What makes up your service?

Each service built with Omnistrate platform is a collection of service components, parameters, features, and infrastructure configurations. Omnistrate will use all those to determine which parameters it needs to request from your customers, which resources need to be deployed, and how they need to be deployed each time a new deployment is created.

Defining a Service Based on Your Existing Artifacts

Omnistrate makes it easy to define a service using the artifacts you already use to run your application:

If you have a Docker image: Use the Compose spec, which extends the familiar Docker Compose format with Omnistrate-specific features. It’s ideal for containerized applications and gets you started quickly. → Learn more about the Compose spec here.

If you use Helm charts, Kubernetes Operators, Kustomize, or Terraform: Use the Service Plan spec to define your service’s structure. This format is designed to onboard and manage these artifacts in a consistent, declarative way. → See the Helm onboarding guide helm-charts

Once your service is defined using either method, you can store it in your preferred code repository and automate updates via your CI/CD workflows. For more advanced control, you can also define services programmatically using the Omnistrate API. For API reference, see here.