Single-tenant deployment
Dedicated, VPC, bring-your-own-cloud and on-prem
What it is
Some customers won't use a shared, multi-tenant service. Single-tenant options range from a dedicated instance you run for one customer, to deploying into the customer's own cloud account, to on-premises or fully air-gapped installs you never see. Each step moves more operational work into environments you don't control.
Regulated industries, governments and large enterprises often require data to stay inside their environment. For them, shared SaaS is a non-starter.
What it takes
About 8–16 engineer-weeks to build in-house, or 4–8 using Replicated, Distr or Omnistrate.
Answer these first
- Product: Is this one deal, or a product line we'll sell again?
- Finance: What do we charge for it?
- Engineering: Can every deployment ship from one artifact and one release train?
- Engineering: How do upgrades happen without one of our engineers on a call?
- Support: How do we debug an environment we can't access?
- Security: What does the customer's security team require of the install?
This page works best with JavaScript on. Every answer also has its own address, like /what/scim.