After you sign up
Once your account is active, a member of our team will reach out within one business day to begin the onboarding process. We don't automate this step — your initial cluster is designed by engineers, not a wizard.
What we need from you
The handoff is minimal by design. We'll ask for:
- Repository access — read access to your codebase (GitHub, GitLab, or Bitbucket). We create a deploy key and never store your credentials.
- Environment variables — a list of the secrets and config your application needs at runtime. We store these encrypted and inject them at deploy time.
- A brief on your stack — language, framework, database, any external services you depend on. This informs the cluster architecture.
- Expected traffic profile — rough numbers: daily active users, peak concurrent requests, any known traffic spikes (launches, seasonal, etc.).
The architecture review
We review your codebase before provisioning anything. We're looking for:
- Stateful vs. stateless services and how they should be orchestrated
- Database connection patterns and pool sizing
- Any services that warrant isolation in separate deployments
- Potential bottlenecks at scale
We'll share our findings and proposed architecture before we build anything. You have full visibility and sign-off.
Timeline
Standard onboarding — from repository submission to production deployment — takes 3 to 5 business days. Complex architectures or multi-service migrations may take longer. We'll give you an honest estimate upfront.