Skip to main content
This section is a work in progress. Typical deployment pattern is:
  1. Have a Dockerfile that installs the soma binary using our install script or base image.
  2. Install your SDK system specific dependencies (e.g. Node.js, Python, etc.)
  3. Install your SDK project dependencies (e.g. pnpm install)
  4. Build your SDK project (e.g. pnpm build)
  5. Set the entrypoint command to soma start
  6. Using your container host platform, set any environment variables required
  7. Let soma.yaml manage your production secrets and MCP provider credentials
  8. Ensure your container has access to the AWS KMS key used to encrypt your secrets and MCP provider credentials

Production dependencies

Soma embeds these dependencies into the binary for ease of use. It’s advised that you follow best practice for self-hosting these tools in a production setting or opt for their cloud managed services.
You can configure credentials for Turso and Restate as parameter options to the soma start command. soma start --db-conn-string xxx --db-auth-token xxx --restate-admin-url xxx --restate-ingress-url xxx --restate-admin-token xxx

Turso / Sqlite

Restate