Quiet infrastructure work. Clear lines of responsibility.
CloudVault is pre-launch. These are the principles shaping the operating model — stated plainly now, before they become promises about a running platform.
Infrastructure should not turn your agency into an unpaid help desk.
The intended scope is the work that accumulates after a site launches: deployment, routing, certificates, backups, monitoring, and infrastructure operations. The model is still being built, so its boundaries matter as much as its ambitions.
Four principles that keep the relationship honest.
- Agency-facing by design
- Your agency remains the commercial and day-to-day relationship. CloudVault does not market to or upsell your clients.
- Standard and portable
- The platform is being designed around standard components and an agreed handoff, so leaving is a process to plan for rather than a trap.
- Authorization before action
- Changes, cutovers, and restores need the right agency approval. “Managed” does not mean unilateral.
- Facts over theatre
- We will describe the operating model as it is. Until coverage, monitoring, and restoration work are evidenced, they remain planned rather than performed.
The agency keeps the client. CloudVault stays behind the work.
The split is a provisional operating model, not a contract. It makes the handoffs visible now so a future agreement can make them specific.
Your agency
// Owns the client and the application
- Client relationship Owns the commercial and day-to-day client relationship.
- Application code Owns source, dependencies, build configuration, and application defects.
- Deployment Supplies a deployable build, a production branch, and release approval.
- Data and auth Owns schema, migrations, authorization logic, and data correctness.
- Domains and DNS Confirms domain authority and authorizes cutovers and client-facing timing.
- Backups and restores Identifies critical data and authorizes restore point, target, and timing.
- Incidents Coordinates client communication and application-level remediation.
- End-user support First-line support for the client and its users.
CloudVault
// Owns the infrastructure layer, invisibly
- Client relationship Stays behind your agency. Does not market or upsell to your clients.
- Application code Does not change code without an approved support request and repository authorization.
- Deployment Provisions and maintains the supported pipeline once it is implemented.
- Data and auth Maintains the managed database and auth service within confirmed boundaries.
- Domains and DNS Prepares and validates infrastructure records within approved scope.
- Backups and restores Runs only the backup services included in the approved plan.
- Incidents Diagnoses infrastructure-scope incidents and reports facts to you.
- End-user support Not included by default.
Escalation path: End client → Agency → CloudVault
Exceptions must be explicit, narrow, and documented. A client emergency contact does not become a general support channel, and never becomes a route for us to sell around you.
Bring one real constraint.
A founding-partner conversation starts with what is awkward about a single suitable site — not a promise to move your whole portfolio.
// Pre-launch. Founding partners are onboarded personally, one site at a time.