Matruno

Deployment

Last updated April 25, 2026

Deploy Matruno by running the FastAPI backend, Temporal worker, Next.js apps, PostgreSQL, Redis, Temporal, artifact storage, and observability components with explicit production hardening.

Supported path in this repo#

The repository supports local and production-like deployment through Docker Compose and explicit service processes. It does not include a one-click cloud deployment or hosted Matruno service.

The root docker-compose.yml starts:

  • postgres with pgvector
  • pgbouncer
  • redis
  • otel-collector
  • temporal
  • temporal-ui
  • backend
  • worker
  • pgbouncer-exporter
  • frontend

The admin control plane is started separately with admin-panel/docker-compose.admin.yml. It expects the root stack's shared network and infrastructure services to exist.

Production requirements#

Before routing production traffic:

  1. Build and publish versioned backend, worker, frontend, admin API, admin panel, and docs images as needed.
  2. Run Alembic migrations with alembic upgrade head.
  3. Use persistent PostgreSQL, Redis, Temporal, and artifact storage.
  4. Set high-entropy SECRET_KEY and TOKEN_HASH_SECRET.
  5. Set COOKIE_SECURE=true and restrict CORS_ORIGINS.
  6. Configure provider credentials only for integrations you actually use.
  7. Expose /health and /health/aggregate to health monitors.
  8. Monitor Temporal task queues and worker capacity.

Runtime ownership#

Know which team owns environment variables, migrations, Temporal worker scaling, PostgreSQL backups, artifact backups, connector credentials, legal workflow definition changes, document template changes, and observability alerts.

No production guarantee

The repo has production-oriented hardening hooks, health checks, and observability, but these docs should not claim universal production readiness for every regulated environment.

Previous

Data Protection

Next

Docker Compose Topology

Was this helpful?