Skip to content

Compose Deployment Strategy

Omnistrate lets you turn an existing Docker Compose application into a SaaS Product without rewriting the application topology. Compose remains the source for services, networks, volumes, and configuration while Omnistrate adds the product and operations layer around it.

When to Use Compose

Compose is a good fit when:

  • Your application is already defined by a Docker Compose file.
  • You want to package several containers and their relationships as one deployable product.
  • You want to expose customer inputs, endpoints, tenancy, observability, billing, and lifecycle operations around the Compose application.
  • You prefer a concise YAML definition over a Kubernetes-native or infrastructure-as-code model.

If your application lifecycle is managed by custom resources, use the Kubernetes Operators strategy. If your product requires cloud infrastructure managed as code, use the Terraform strategy.

How Compose Fits into Omnistrate

The Compose file describes the application topology. Omnistrate extensions add the service plan, resource visibility, compute, storage, API parameters, integrations, action hooks, and deployment capabilities needed to deliver that topology as a managed service.

The resulting control plane can manage customer subscriptions and deployments across supported clouds and deployment models while the application continues to run from the Compose definition.

Strategy Guide

For the high-level Docker Compose concepts and schema entry point, see the Compose specification overview.