Use Cases¶

This section explores various deployment models and use cases for building SaaS Products with Omnistrate. Each use case addresses specific business requirements and deployment scenarios that organizations commonly face when building and scaling their Plans.

For more detailed technical information about building SaaS Products, see our Build Guide section.

Deploy in Customer Accounts¶

BYOC (Bring Your Own Cloud)¶

Deploy your SaaS Products directly in your customers' cloud accounts for enhanced security, compliance, and cost control. This model is ideal for enterprise customers who prefer to maintain data sovereignty and control over their infrastructure while benefiting from your Plans. Examples: Databricks Cloud, StarTree BYOC, Redpanda BYOC.

OnPrem¶

Enable on-premises deployments with minimal external dependencies while maintaining centralized management capabilities. Perfect for customers with strict security requirements or air-gapped environments who need enterprise-grade functionality within their own infrastructure.

PaaS¶

In this model, you host the infrastructure in your account and your customers can simply self-serve themselves to deploy the product i.e. they can request a deployment on demand, configure it to their needs, and start using it immediately. In other words, this model enables Product-Led Growth (PLG) by removing manual bottlenecks from provisioning. Examples: AWS RDS, Confluent Cloud (Dedicated)

SaaS¶

In this model, your customers don’t even create or configure deployments. The infrastructure is hosted within your account. They simply go to an URL, authenticate themselves and start using your application — no need to create/customize/govern/manage deployments. The endpoint is smart enough to handle a broad range of use cases and automatically adjust based on usage to optimize for the cost, scale, performance without compromising on the security or reliability. Examples: Confluent Cloud (Standard/Enterprise), HubSpot, Rippling.

Agent-aaS¶

Traditional apps are static — users must manually navigate interfaces, trigger workflows, and interpret dashboards. Instead, agents can execute tasks on behalf of users — interacting with APIs, orchestrating services, and adapting based on environment or intent.

To build dynamic workflows, agents are not optional — they are essential. But here's the challenge: Agents aren’t monolithic binaries or static microservices. They are iterative, context-driven, often multi-step systems. Hence, we need a separate distribution model for you to distribute them nati vely.

Other use cases¶

Internal SaaS/PaaS¶

Build internal platforms to streamline application hosting and management within your organization. Enable platform and IT teams to offer standardized services to internal teams, improving efficiency, reducing operational overhead, and maintaining consistency across deployments.

Open Source SaaS/PaaS¶

Transform open-source projects into monetizable Plans with enterprise-grade capabilities. Accelerate the journey from open-source community adoption to commercial success by leveraging Omnistrate's platform to handle the undifferentiated heavy lifting of operations.

Extend your Platform Stack¶

Integrate Existing Stack¶

Extend your current platform with new distribution channels without rebuilding from scratch. Learn about vertical integration patterns (adding new deployment models, regions, or services) and horizontal integration patterns (offloading specific layers of your SaaS Product to Omnistrate).