BYOC deployments
Offer BYOC on AWS without building the platform.
Bring your own cloud (BYOC) means your SaaS runs in the customer's AWS account while you still deliver
and update it. Deployz gives small teams that model.
BYOC sits between hosted SaaS and self-hosting.
Your customer keeps the infrastructure. You keep control of releases.
Hosted SaaS
- App runs in
- Your cloud
- Data infrastructure
- You own it
- Installs
- Not needed
- Updates
- You ship them
- AWS bill
- You pay
BYOC with Deployz
- App runs in
- The customer's AWS account
- Data infrastructure
- The customer owns it
- Installs
- Customer approves; Deployz deploys
- Updates
- You choose; Deployz deploys
- AWS bill
- The customer pays AWS
Self-hosted handoff
- App runs in
- The customer's infrastructure
- Data infrastructure
- The customer owns it
- Installs
- The customer's team runs them
- Updates
- The customer's team, when they choose
- AWS bill
- The customer pays
What a BYOC platform needs
Teams that build BYOC themselves maintain each of these for every customer. Deployz includes them.
See how it works- An installer customers trust
- Installation links with a preview of resources, AWS cost estimate, and IAM actions
- Cross-account access
- A connector the customer launches; it connects out, and its role has a permissions boundary
- Infrastructure templates
- Rule-based CloudFormation for supported AWS resources
- A release pipeline
- Versioned release images built from your repository
- Updates and rollbacks
- Per-customer releases, started by you
- Status across accounts
- Progress and health for every customer environment
BYOC on AWS, for one supported architecture.
Deployz deploys one container image, with optional workers, PostgreSQL or MySQL, a Redis-compatible cache, and S3, into a new network in the customer's AWS account. It does not support other clouds, Kubernetes, or existing customer VPCs.