Getting Started with Omnistrate¶
Turn your existing deployment assets into a production-ready customer deployment with the Omnistrate Starter Kit. Start with the agent skills, choose where customers will run your software, build one working development plan, and test the customer journey before adding billing or production automation.
Omnistrate generates the private control plane around your product: APIs, workflows, a customer portal, deployment automation, observability, and operational controls. You bring your application and deployment assets; the starter kit takes you from first setup to a repeatable release and launch process.
Follow the Starter Kit¶
| Step | What you do | What you establish |
|---|---|---|
| 1. Start with the agent skills | Install and authenticate the CLI, then install the agent skills. Configure MCP only if you need it. | An authenticated workspace and an agent ready to reuse your assets safely. |
| 2. Deployment model and account onboarding | 2.1 Select the deployment model: choose Hosted SaaS, BYOC account or VPC, existing Kubernetes, or an air-gapped installer. 2.2 Onboard cloud accounts: follow the relevant account or cluster onboarding flow after confirming ownership and network boundaries. | A distinct plan per deployment model, agreed infrastructure ownership, and the required account onboarding completed or prepared for the development plan. |
| 3. Reuse your assets and build in development | Pick the appropriate deployment strategy, pin your artifacts, validate the specification, and create a minimal development deployment. | One known working baseline with a passing application smoke test. |
| 4. Test the customer journey and release process | Exercise customer onboarding, endpoints, lifecycle operations, and repeatable version promotion. | Evidence that customers can deploy and operate the product you promise. |
| 5. Prepare for production and launch | Add customer experience, security, operations, pricing, billing, and marketplace fulfillment as needed. | A tested offering ready for your intended production audience. |
Keep the first iteration small: one deployment model, one target, and fixed non-secret values. Introduce customer-facing parameters and commercial integrations after the baseline works. Ask for approval before creating billable resources, changing permissions, or deleting anything.
Reuse Your Existing Deployment Assets¶
Detailed tutorials are organized under Build by Deployment Strategy, so you can stay with the approach your application already uses:
- Compose, including container images and Compose files and source repositories with Dockerfiles.
- Helm charts, including Helm and Terraform compositions.
- Kubernetes operators, preserving CRDs and operator-owned application lifecycles.
- Terraform/OpenTofu, reusing infrastructure modules.
- Kustomize, reusing overlays or raw Kubernetes manifests.
For disconnected deployments, follow the dedicated air-gapped Helm installer guide. Deployment strategy describes how your assets are packaged; deployment model describes where they run; tenancy describes customer isolation.
Get Help¶
Use your shared Omnistrate Slack channel for onboarding questions, with your repository or chart reference, chosen deployment model, environment, and sanitized diagnostics. Book an onboarding session when architecture, permissions, or packaging needs a joint review.
Start here: Step 1: Start with the agent skills.