For B2B SaaS Teams
Deploy into customer AWS
Run your SaaS in each customer's own AWS account. Connect GitHub, and Deployz checks what your app needs, sets up the infrastructure, and deploys the releases you choose.
Free evaluation · No credit card required
Customer-hosted deployments without a DevOps project.
-
Say yes to customer-hosted deals
Offer customer-hosted installs without a custom project for each deal.
-
Skip the infrastructure work
Deployz sets up the network, containers, database, cache, storage, and HTTPS.
-
Ship updates to every customer
Build a release once. Choose when each customer gets it.
How it works
- 1
Connect GitHub
Deployz reads your repository and reports what your app needs.
- 2
Configure and build a release
Fill in settings, fix any blockers, and build a versioned release.
- 3
Your customer connects AWS
They open your installation link and approve access in their AWS console.
- 4
Deploy and manage updates
Deployz deploys the release. You choose when each customer updates.
Configure, deploy, and manage in one place.
See what passed, what needs input, and what blocks deployment.
Follow deployment progress in your customer's AWS account.
Check status, release updates, and roll back.
Your customer owns the account. You own the app. Deployz runs the deployments.
-
Your customer
Owns the AWS account
Approves the connector, pays AWS directly, and administers the account. The database, cache, and files stay there.
-
You
Own the application
Your code, configuration, and integrations. You decide when each customer gets a new release.
-
Deployz
Runs the deployments
Sets up the supported infrastructure, deploys releases, and handles updates, rollbacks, and status.
Deployz works through a connector that the customer launches in their AWS console. It does not receive database data, cache contents, S3 data, or application logs.
Security and architectureQuestions
Who owns the code, infrastructure, and data?
You own your code and data. Your customer owns the infrastructure deployed in their AWS account. Deployz handles deployment and management without taking ownership of your application or customer resources.
Is there any lock-in?
No proprietary runtime or Kubernetes setup required. Deployz uses standard AWS services, so your application and infrastructure can keep running on them. You can stop using Deployz without rebuilding your application, although managing future deployments becomes your responsibility. The default deployz.dev URL and the Deployz image registry are the parts that still depend on Deployz.
Who pays for the underlying infrastructure?
AWS infrastructure costs are billed directly to the owner of the customer AWS account. Deployz charges separately for its deployment and management services. No infrastructure markup.
Does my customer need an AWS account?
Yes. Your customer approves the connection in their own AWS account, and AWS bills them for the resources. They do not need a Deployz account.
Do I need DevOps or AWS expertise?
No dedicated DevOps team is needed. Deployz finds what your app needs and sets up the supported AWS infrastructure. You still review the configuration and fix issues in your own code.
Is DevOps support available?
Deployz is designed to eliminate routine DevOps work. It automates infrastructure provisioning, deployments, configuration, and lifecycle management. For issues that need human assistance, our team is available to help with Deployz-related problems.
Is Deployz SOC 2 or ISO 27001 compliant?
Deployz runs on infrastructure provided by AWS, which holds SOC 2 reports and ISO 27001 certification. Deployz is preparing for its own independent SOC 2 audit. Deployz itself is not currently SOC 2 or ISO 27001 certified.
Which clouds and Kubernetes distributions do you support?
Deployz currently supports AWS, using managed services such as ECS, RDS, S3, and other AWS resources. No Kubernetes cluster is required. Support for additional cloud providers may be introduced in the future.
How long does it take to go live?
From a few minutes to a few hours. Deployz analyzes your repository, identifies infrastructure requirements, and automates deployment into your customer's AWS account. The time depends on the application, the changes it needs, and the AWS resources being provisioned.
What happens if Deployz is unavailable?
The application keeps running in the customer's account, because its requests do not pass through the Deployz management service. New installations and updates pause. Traffic to the default deployz.dev URL depends on the Deployz proxy; with a custom domain, traffic goes directly to the customer's load balancer.