Hosting problems should not become agency emergencies.
Your clients call you first when something breaks. CloudVault is being designed to handle the hosting work behind the scenes, while your agency stays in control.
When a site goes down, you should not have to become the server expert.
The client contacts your agency, and everything else stops while you try to find the problem.
CloudVault is being designed to handle the agreed hosting response and update your agency with what happened and what was done. You decide what the client hears.
Your agency remains the client contact. Coverage hours and escalation limits will be agreed before onboarding.
A messy inherited site needs a plan before it needs a move.
You receive a site with missing logins, old software, and no useful notes. It is hard to price the work or promise a smooth move.
We would first document what exists, what is missing, and whether we can support it. You get the written assessment before deciding whether to move.
You provide the available files and access. We do not promise to accept every old or custom setup.
A growing site should lead to a planned upgrade, not a crisis.
A site that once fit shared hosting starts slowing down as traffic grows. The problem usually reaches your agency only after the client notices.
Once monitoring is available, we would show your agency the trend and explain the next step early. Nothing is resized or billed without your approval.
Keep the client. Add hosting to the relationship.
Many agencies either give hosting away or pass through the bill while still doing the support work.
The intended model lets your agency package managed hosting under your own brand and set the client price.
- CloudVault
- Provides the agreed hosting capacity and support.
- Your agency
- Packages the service and sets the client price.
- Your client
- Continues to see and work with your agency.
Rates, capacity limits, and commercial terms are not published yet. They will be discussed with founding partners once the real cost base is known.
Give clients clear answers without pretending everything is finished.
Larger clients may ask about uptime, access, support, and exit plans. Here is the simple answer today.
Do you offer an uptime guarantee?
Not yet. We will only publish one after the platform has real measurements, written exclusions, and reviewed terms.
No figure is published yetWho can access the site?
Only the people who need access to run the agreed hosting work. Your agency keeps ownership of the website and client relationship.
Confirmed boundaryWill CloudVault contact my client?
No. We work through your agency unless a narrow emergency contact path is agreed in writing.
Confirmed policyCan a client leave?
Yes. The platform is being designed around standard tools so code and data can be moved.
Confirmed design principle
When a client leaves, the handoff should be orderly.
Credentials, files, and setup notes can end up scattered across several accounts. That makes a normal exit harder than it should be.
We are designing a documented export process using standard components. Your agency coordinates the client and destination; we provide the approved data and hosting details.
Exports require proper authorization and account settlement. Leaving should be a clear process, not a retention tactic.
Three boundaries that do not change.
We do not market to your clients.
// Confirmed policy — C-03We do not upsell around your agency.
// Confirmed policy — C-02We design for standard, portable components.
// Confirmed principle — C-08Want fewer hosting emergencies?
Start with one lower-risk site. We will review it with you, explain the scope, and let you decide whether to move forward.
// Pre-launch. Founding partners are onboarded personally, one site at a time.