The Problem:
Deals now require self-hosting because enterprises want data to stay inside their account. Regulated customers need control over cloud, region, access, and update timing. SaaS-only loses them, and every workaround costs more than the deal.
For SaaS-only products, that creates four bad options:
- Build a separate self-hosted product. Now you have two products, two release paths, and a second team to maintain it.
- Manually deploy every customer. Each deal becomes a custom deployment project.
- Wait on customer DevOps. Implementation gets stuck in security reviews, tickets, approvals, and infrastructure queues.
- Lose the deal. A competitor that can run inside the customer's environment becomes the safer choice.
The solution: one product, delivered two ways
Keep your SaaS running exactly as it does today. With Akua, the same product can also install into the customer's own cloud, account, or server from a guided link.
- Isolated installation for every customer. Data stays in their environment, and they choose the provider, region and server.
- Preconfigure each customer setup. Set defaults, lock fields, and tailor offers without custom engineering.
- Publish updates once. Customers approve when they land.
- Avoid a second product and ops team. No custom deployment work for every deal.
Customer install view
What you get
- Win larger deals. Support enterprise and regulated customers without changing your product.
- Cut deployment costs. Guided installs replace weeks of custom deployment work.
- Avoid product fragmentation. SaaS and self-hosted customers stay on the same release.
- Get through security reviews faster. Customers keep their data and infrastructure under their control.
- Custom deals without custom builds. Tailor access, settings, and offers without branching your product.
- Be ready for every audit. Full deployment history, traceability, and rollback built in.
- Manage deployments without accessing customer data. Manage installs and updates while data remains with the customer.
How it works
Package once
Choose what the customer can configure. Akua builds the setup.
akua package publish brightline-erpSend one link
They sign up, pick where to host and install it.
akua.dev/i/x7kQ9mOperate the fleet
Manage from one place. Ship updates and monitor health.
264 deployments · 3 updates pendingSecurity & Compliance
- Your product runs in the customer's own cloud, account, or server.
- Customer data never leaves their environment.
- You publish updates. The customer decides when to apply them.
- Installs connect to Akua. Akua never connects into customer systems.
- Customers choose their cloud provider, deployment region, and infrastructure policies.
FAQ
Does the software run in the customer's own cloud, or on shared infrastructure?
It runs entirely in your customer's own cloud account, on infrastructure they control. Each customer's install is separate from every other customer's, and their data stays in their account. It never passes through us.
Can you or the vendor reach into the customer's environment?
No. The install reaches out to us. We never reach in. The customer can cut that connection at any time, and the software keeps running.
Which clouds can the customer use?
Their own. They choose the provider and the country:
- AWS
- Azure
- GCP
- Hetzner
- IONOS
- OVH
- Scaleway
- On-prem
- A server they already run
Do I have to maintain two codebases?
No. It is the same product, delivered two ways. Your SaaS customers and your self-hosted customers run the same release.
How do updates reach each customer?
You ship an update once. Each customer receives it as a change they can review and accept in their own environment, on their own schedule.
Who handles billing and payments?
We do. You never have to build billing or chase invoices. Your customer pays for the platform, and they pay their cloud provider directly. We add no markup on their compute.
How is this different from the tools I have already evaluated?
Most other tools make your own team operate each deployment. Here the customer installs the software themselves and keeps control, while you manage every install from one place.