Marsovius is deployed on the customer's hardware, in the customer's jurisdiction, under the customer's law. The house does not host customer data. This page describes what the platform supports today, what is on the roadmap, and the postures it does not yet support.

Today

The canonical deployment target is Docker Compose. The docker-compose.yml that ships in marsovius-platform is the file used by the house in development and by the first production customers.

Four containers, host networking for the API and sync services, persistent volumes for ClickHouse. The full topology is described in Installation.

Kubernetes

Every container is a standard image. Anyone with a working Kubernetes cluster can roll a deployment from the same images — Postgres, ClickHouse, FastAPI, nginx — using the manifests they already maintain. No official Helm charts ship in the repository today. When they do, this page will say so.

Bring your own cloud

Marsovius targets open standards — Postgres, ClickHouse over HTTP, OIDC, OpenTelemetry — and does not depend on any single cloud's proprietary services. Container-based deployment is therefore portable across:

OVHcloud (FR)
Scaleway (FR)
IONOS (DE)
Hetzner (DE / FI)
STACKIT (DE)
Aruba Cloud (IT)
T-Systems Open Telekom Cloud (DE)
on-premise hardware

The house does not publish tested matrices for each cloud beyond the ones it has deployed onto.

Sovereign-cloud direction

The deployment story the house is building toward — air-gap, sovereign-cloud, EU mirror registries, signed release bundles, cleared legates on premises — is the work of the next several releases. The single source of truth for what is planned and in what order is the platform's roadmap:

docs/ROADMAP.md

Read it before assuming anything about a feature not described above. The roadmap is held in git for a reason: every claim is reviewable.

Production checklist (current scope)

For a Docker-Compose deployment to a single hardened node:

Postgres with point-in-time recovery enabled for marsovius_meta.
ClickHouse provisioned with storage proportional to the lake target.
OIDC provider configured with the customer's identity authority (the platform's auth surface is JWT today; OIDC plumbing is in progress).
ANTHROPIC_API_KEY set if Pythia is in scope; otherwise the AIP endpoints return 503 and every other module continues to work.
A backup and restore drill rehearsed against marsovius_meta and the ClickHouse data directory before first production use.
A legate or the customer's lead engineer present for the first cut-over.

Upgrades

Versions are tagged in git and published as Docker images. Major versions are intended for long-term support; the contract on upgrade ergonomics firms up at v1.0 — see the roadmap for the policy.

Where to read next

Operations — the day-to-day commands.
The Pact of Sovereignty — for the contractual posture the house offers sovereignty-bound customers.

Deployment