Subscription management¶

Omnistrate provides you with a powerful subscription management feature designed to simplify and automate the subscriptions for your SaaS Product. It allows you to configure subscription behaviors, such as enabling auto-approvals, or fine grained control such as manual approval, suspending/removing, or re-enabling subscriptions. You can gain a comprehensive view of all subscriptions, including detailed information on instances and user roles, ensuring complete visibility into your SaaS Products.

What is a subscription?¶

A subscription is a formal agreement between your customers and your SaaS platform that grants them access to your services based on a specific Plan. When customers subscribe to a Plan, they gain the ability to create and manage instances of your SaaS offering according to the resources, features, and limitations defined in that Plan.

Each subscription represents:

• Access Rights: Permissions to use your SaaS platform and its features
• Resource Allocation: Compute, storage, and other resources as defined by the Plan
• Service Level: The tier of service and support the customer receives
• Billing Agreement: The pricing model and payment terms for using your platform

How customers subscribe to a plan¶

The subscription process is designed to be straightforward and secure for your customers:

1. Plan selection¶

Customers browse the available Plans you've configured for your SaaS offering. Each Plan defines:

• Resource limits (CPU, memory, storage)
• Feature availability
• Pricing structure
• Support level

2. Subscription request¶

When a customer selects a Plan, they initiate a subscription request through your customer portal or API. This request includes:

• Selected Plan details
• Customer account information
• Billing preferences
• Any custom configurations

3. Terms and conditions acceptance¶

Before the subscription can be processed, customers must:

• Review your platform's Terms of Service
• Accept the Privacy Policy
• Acknowledge the Service Level Agreement (SLA)
• Agree to the billing terms and payment schedule

This step ensures legal compliance and sets clear expectations for both parties.

4. Subscription approval¶

Depending on your configuration, subscriptions can be:

• Auto-approved: Instantly activated for immediate use
• Manually reviewed: Queued for your team's approval before activation

5. Platform access¶

Once approved and terms are accepted, customers can:

• Access your SaaS platform
• Create instances within their Plan limits
• Manage their resources through the customer portal
• Begin using your services immediately

6. Deployment instance management¶

After subscription activation, customers can:

• Create Instances: Launch new instances of your SaaS offering within their Plan limits
• Start/Stop Instances: Temporarily halt running instances to save resources while preserving data
• Delete Instances: Permanently remove instances they no longer need
• Monitor Performance: Track instance performance, resource utilization, and health metrics
• Modify Configurations: Adjust instance settings and parameters as allowed by their Plan
• Scale Resources: Increase or decrease instance resources within Plan boundaries
• Access Management: Control user access and permissions for their instances

All these steps are automated and can be performed by customer in a self-served manner when enabling the Customer Portal

Subscription management operations¶

Once customers subscribe to your SaaS Product, you will need to manage those subscriptions and perform operations as required on those subscriptions.

Omnistrate enables the following operations:

Subscription approval - auto/manual¶

Whether you want tight control during the initial or beta launch of your SaaS, reviewing each subscription request before approving, or you want to streamline and automate the subscription approval process after launch, Omnistrate supports both approaches. You can configure it to meet your specific needs, providing you with the flexibility to manage subscriptions effectively at any stage.

Review all subscriptions¶

Review all of your subscriptions in detail with Omnistrate. You can see detailed list of all of your subscriptions with information such as status, users, roles and instances etc. This enables you to easily manage the subscriptions as well troubleshoot any issues that arise. Whether you need to check the status of a subscription, identify which users have access to specific subscriptions, or review the details of each instance, Omnistrate ensures you have all the information you need at your fingertips.

Cloud Provider and Region Lock¶

Use cloud provider and region locks to control where your customers can deploy instances. You can limit a subscription to specific deployment locations for data residency, compliance, or contractual requirements. The restriction applies to all users sharing the subscription.

A subscription inherits its Plan's deployment locations by default. Subscription restrictions can narrow those locations; they cannot enable a cloud provider or region that the Plan does not support.

To configure these restrictions, sign in as a member of the SaaS Provider organization with Service Operator, Admin, or Root access to the SaaS Product. See Omnistrate RBAC.

Configure locations in the Operations Console¶

The Deployment Locations form offers these choices:

For Restrict locations, select at least one cloud provider. For Selected regions, select at least one region per provider. The form offers only locations available in the Plan.

Update an existing subscription¶

1. Open Subscriptions in the Operations Console and select your SaaS Product and Environment.
2. Click the subscription's Subscription ID to open its details, then select the Deployment Locations tab.
3. Choose the location policy and, if restricting locations, select the allowed cloud providers and regions.
4. Select Save Changes.

If saving fails, review the error and the validation requirements, then adjust your selections.

Set locations when subscribing a user¶

1. Open Subscriptions and select your SaaS Product's production (PROD) Environment.
2. Select Subscribe User, then choose the Customer.
3. On the desired Plan's card, select Configure locations.
4. Choose the location policy, select any required cloud providers and regions, then select Subscribe.

To create the subscription with all Plan locations, you can select Subscribe directly on the Plan card without configuring locations.

You can also configure subscription deployment locations through the Fleet API using allowedDeploymentLocations. See the API reference for request details.

Validation and deployment behavior¶

When you tighten a restriction, all existing cloud deployment instances in the subscription must remain within the proposed locations, including stopped instances. If an existing instance is outside the new restriction, the update fails and identifies the instance, provider, and region. Changing the restriction does not migrate existing instances.

If a previously selected provider or region is no longer available in the Plan, remove it or choose All plan locations or All plan regions, as appropriate, in the Operations Console.

Customers can create instances or restore snapshots to new instances only in locations allowed by both the Plan and the subscription. When building your own portal, use the subscription restriction to limit the deployment locations you offer customers. Omnistrate also enforces these restrictions on API requests.

Subscription Lifecycle¶

Subscription suspension¶

Subscriptions can be temporarily suspended when billing issues, payment risk, policy violations, or other concerns require access to be restricted. Suspension preserves the subscription, its data, and its existing deployment instances. It does not automatically stop or delete running deployments.

Customers retain read-only visibility into the suspended subscription and its deployments, but cannot:

• Create new deployment instances
• Update, upgrade, scale, start, stop, restart, fail over, or delete existing instances
• Run other mutating deployment-management operations

Authorized provider-side operators can continue to perform RBAC-allowed operations on existing deployments for remediation, upgrades, and cleanup. Provider-side creation of new instances remains blocked while the subscription is suspended.

Subscription suspension affects access to the Plan for all customers on that subscription. User suspension is separate: it applies to an individual user account. A suspended user can still sign in and perform billing or payment-related activities, but cannot create, update, or manage deployment instances even if the subscription itself is active. For details, see User Suspension.

Reactivating a subscription¶

Suspended subscriptions can be reactivated seamlessly, restoring full access to the SaaS Product and allowing customers to pick up right where they left off. This ensures a smooth and uninterrupted experience for customers who are ready to resume their subscription, eliminating any inconvenience.

Terminating a subscription¶

You can terminate subscriptions when needed. Whether ending a SaaS Product contract, responding to a customer cancellation request, enforcing policy compliance, or optimizing resource use, terminating subscriptions helps manage resources effectively.