Deploy SteelEngine on your own infrastructure with Docker or Kubernetes.
For internal APIs and MCP servers, configure the app and Temporal Worker's deployment policies together. The production Compose file passes EGRESS_ALLOWLIST and ALLOWED_MCP_DOMAINS to both services. See Private Network Configuration for policy setup, separate API hosts, and verification.
Self-hosting SteelEngine requires an Enterprise subscription. The images live in the private ghcr.io/steelengineai registry, and anonymous pulls are rejected. You need registry credentials as well as the license. Contact sales@steelengine.com for pricing, deployment options, and pull access.
Requirements
| Resource | Small | Standard | Production |
|---|---|---|---|
| CPU | 2 cores | 4 cores | 8+ cores |
| RAM | 16 GB | 16 GB | 32+ GB |
| Storage | 20 GB SSD | 50 GB SSD | 100+ GB SSD |
| Docker | 20.10+ | 20.10+ | Latest |
Small: Development, testing, single user (1-5 users) Standard: Teams (5-50 users), moderate workloads Production: Large teams (50+ users), high availability, heavy workflow execution
Every tier starts at 16 GB. The Compose file reserves 13 GB of container memory before PostgreSQL. That is 8 GB for the app, 4 GB for the Temporal Worker, and 1 GB for realtime. The Helm chart adds 3 GB for PostgreSQL and migrations by default. Memory is the constraining factor rather than CPU. Workflow execution (isolated-vm sandboxing), file processing, and vector operations (pgvector) all live in RAM. Larger tiers add CPU and storage headroom. The optional Laya Decision server adds a 6 GB limit (about 1 vCPU and 4 GB in use), so add that much when you run it.
These figures cover the SteelEngine containers only. The Temporal server runs outside the Compose stack and needs its own capacity. See Temporal.
Quick Start
SteelEngine needs a running Temporal server before the stack will start. Set one up first with the Temporal guide. Then write the .env described in Docker → 1. Configure Environment. Compose refuses to start without TEMPORAL_WORKER_BROKER_SECRET and TEMPORAL_WORKER_APP_URL.
git clone https://github.com/steelengineai/steelengine.git && cd steelengine
# Sign in with the registry credentials from your subscription
docker login ghcr.io
# Write .env first (secrets, public URLs, TEMPORAL_* settings)
docker compose -f docker/selfhost/compose.yml up -dOpen http://localhost:3000/signup and create the first account. Only an empty database accepts a sign-up without an invitation, so that account is the first admin, and everyone else joins by invitation.
Deployment Options
Docker
Deploy with Docker Compose on any server
Kubernetes
Deploy with Helm on Kubernetes clusters
Entra Workload Identities
Authenticate Azure DevOps deployment pipelines and grant organization-scoped workspace access
Organization Releases
Follow a Git branch and deploy managed workspaces together, with independent Source Control for teams on their own cadence.
Temporal
Run the Temporal server every deployment depends on
Cloud Platforms
VPS guides for DigitalOcean, AWS, and Azure, plus managed databases
Workflow Checkpoint Upgrades
Releases with checkpoint state V4 support require a manual, once-per-database activation to enable payload deduplication. Normal schema migrations leave the existing write version unchanged. Upgrade every application reader and worker before activation, including older draining workers. See Workflow checkpoint upgrades for the dedicated-installation runbook and rollback limits.
Architecture
| Component | Port | Description |
|---|---|---|
| steelengine | 3000 | Main application |
| steelengine-worker | 3003 (internal) | Temporal Worker that runs workflows, schedules, and background jobs. The port serves health checks and Task Queue backlog stats and is not published |
| realtime | 3002 | WebSocket server |
| db | 5432 | PostgreSQL with pgvector |
| migrations | - | Database migrations (runs once) |
| Temporal server | 7233 | Not part of the Compose file. You run ghcr.io/steelengineai/temporal-server yourself. See Temporal |
The Compose file pulls steelengine, worker, realtime, and migrations from ghcr.io/steelengineai. PostgreSQL comes from pgvector/pgvector:pg17 on Docker Hub. The app and the Temporal Worker share ENCRYPTION_KEY, INTERNAL_API_SECRET, and TEMPORAL_WORKER_BROKER_SECRET. Realtime receives BETTER_AUTH_SECRET and INTERNAL_API_SECRET but never the broker secret.