Use Cases¶

Choose a use case based on two questions: where the product runs and how customers consume it. Omnistrate uses the same service definition and lifecycle framework across these models, so you can add a new distribution channel without rebuilding the product's operational layer.

Hosted SaaS¶

With Hosted SaaS, customers can sign in and use your application, provision a managed service configured to their needs, or launch an AI agent with their own data and tools. In every case, the service runs in your cloud accounts, and you—not the customer—manage its infrastructure, scaling, upgrades, and recovery.

Choose the isolation boundary that fits each customer segment: cellular multi-tenancy groups customers into bounded shared environments, while dedicated tenancy gives each customer an isolated infrastructure stack. Both preserve SaaS convenience without requiring customers to bring their own cloud accounts.

Bring Your Own Cloud¶

BYOC runs the product in a customer-owned cloud account while the service remains managed through your control plane.

BYOC¶

Use standard BYOC when customers require cloud-account ownership, data residency, direct cloud-cost attribution, or tighter control over IAM and networking. Omnistrate automates account onboarding and operates deployments across the customer fleet without requiring shared static credentials.

BYOC PrivateLink¶

Use BYOC PrivateLink for AWS customers that require private control-plane connectivity. Management traffic stays on AWS PrivateLink instead of traversing the public internet, while the product retains the same managed lifecycle as standard BYOC.

BYOC On-Premise¶

Use BYOC On-Premise when the customer supplies an existing Kubernetes cluster rather than a cloud account. The cluster remains connected to your control plane for deployment, upgrades, observability, and other lifecycle operations.

Air-Gapped¶

Package the product as a self-contained installer for environments with no live control-plane connection. This model is intended for customers whose security or regulatory requirements prohibit external connectivity.

Other Use Cases¶

Internal Developer Platform¶

Give application teams approved, self-service templates for infrastructure and application stacks. Platform teams centralize policy, upgrades, cost controls, and operational standards without becoming a ticket-driven provisioning team.

Managed Open Source¶

Turn an open-source project into a commercial managed service by adding tenant onboarding, deployment automation, upgrades, observability, support workflows, and monetization around the core project.

Integrate existing stack¶

Keep the parts of your existing platform that differentiate your product and use Omnistrate for selected control-plane layers or new distribution channels, regions, and services.