Self-hosting
On your own infrastructure
Marlow ships as container images, a Helm chart and a compose file. The services keep nothing durable on local disk, so each one can run as several replicas.
A Helm chart for a Kubernetes cluster, or a compose file that runs the whole stack on one host.
Every run works in its own disposable sandbox: a container on one host, or a Kubernetes pod anywhere in the cluster, running as non-root.
A switch that pauses every run in an organisation, manual ones included.
Sign-in, which goes through a hosted Auth0 tenant. The chart will not install without one.
Model calls, to the provider you configure — unless you point Marlow at a model you host yourself.
Calls to GitHub or GitLab, which is where the tickets and pull requests are.
Postgres, Temporal and S3-compatible storage of your own. The chart connects to them; it does not deploy them.
An encryption key for stored secrets. The chart refuses to install without one.
A conversation with us first. Self-hosting is set up together, not downloaded.