One suitable site. A clearer way to find the edges.
Founding partners will be onboarded personally. The first conversation is for fit, constraints, and an agreed scope — not a promise that every project belongs on the platform.
Small enough to inspect. Real enough to learn from.
The founding-partner path begins with a single lower-risk site, the constraints you already know, and an honest decision about whether the intended scope fits. It is not an automatic migration pipeline or a commitment to move the rest of your book.
Come with the edges, not a polished pitch.
A site with a known history, its repository or production files, and the constraints that already make its hosting work awkward.
What the agency needs to retain, what CloudVault would need to understand, and where the current model is not ready.
Whether a small, agreed scope makes sense. A no is useful when it keeps a client site out of an unready fit.
We will reach out when the founding-partner conversation opens.
Leave an agency email. We will use it for one note when onboarding is ready; you can read exactly what is stored in the privacy notice.
// Pre-launch · founding-partner waitlist