Bring your own cloud
Plan your first customer-cloud deployment
Define the account, access model and operating responsibilities before bringing your SaaS into a customer’s infrastructure.
Start with the customer’s requirement
Ask what the customer needs from running your software in their account. The answer might be control over infrastructure, a chosen deployment region, a procurement requirement or integration with an existing environment.
Write down the specific requirement. It will guide the topology and access model more effectively than a broad request for “private cloud”.
Agree the deployment boundary
Identify the account, region and environments involved. List the application services, persistent data stores and external services your software needs.
Make the boundary visible to both teams: what runs in the customer’s account, what remains with you, and which connections cross between them. Include operational data such as logs and support diagnostics in that discussion.
Assign operating responsibilities
Agree who performs each recurring task before the first deployment:
- Approving and granting infrastructure access.
- Releasing application updates and database migrations.
- Maintaining the cluster and its supporting services.
- Monitoring the application and responding to incidents.
- Creating backups and testing restoration.
- Reviewing and paying for cloud usage.
BYOC gives the customer ownership of the infrastructure. It still needs an explicit operating agreement.
Choose a repeatable application pattern
Document the common services and dependencies that every customer needs. Keep customer-specific values separate: domains, credentials, sizing and external integrations.
Start with one pilot customer. Exercise installation, an application update and a recovery scenario before treating the pattern as ready for repeated deployments. See Kapten for SaaS vendors for the intended workflow.
Prepare an exit path
Define what happens when access is revoked or the commercial relationship ends. Agree which resources remain, how the customer obtains an inventory, and who takes over maintenance and application delivery.
Infrastructure ownership is most useful when the team inheriting it knows how to operate it. Include the handover in the original plan.
Scope the pilot
Bring your architecture, the customer’s constraints and your operating model to the early-access conversation. Confirm available capabilities before promising automated fleet management, reseller workflows or a particular deployment schedule.
Build with Kapten
Start with one service.
Build from there.
Tell us what you want to deploy. We review each request and follow up about fit and onboarding on your preferred cloud.
Free during early access. No card required. Cloud usage billed separately.