Frequently asked
Procurement-grade answers.
The questions the house is asked most often — cost, deployment, sovereignty, exit, the Legates, and how the platform compares to its neighbours.
For anything not answered here, write to house@marsovius.com.
01
Cost & engagement
- — How is Marsovius priced?
- There is no public price list. Community is free under Apache 2.0. For Pro and Sovereign editions, pricing is per institution, not per seat or per legate-hour. The conversation begins after the audience is granted.
- — Do we have to engage a legate to use Marsovius?
- No. The Community edition is fully self-service: clone, deploy, run. A legate is offered for institutions that want setup, training, counsel, and companionship — included in Pro and Sovereign.
- — Is there a minimum commitment?
- For Community, none. For Pro, the engagement is annual with the legate present for the first twelve months. For Sovereign, the relationship is structured under the Pact of Sovereignty and is typically multi-year.
- — What if we are too small for an audience?
- You are not. The same code that runs a hospital network runs a single online shop. Inspect the source, deploy it, write to legates@marsovius.com when you need a hand.
02
Deployment & operations
- — Where does Marsovius run?
- On your hardware — Kubernetes, bare metal, or air-gapped. The house does not host customer data. Cloud-agnostic across OVHcloud, Scaleway, IONOS, Hetzner, STACKIT and on-premise.
- — Is it cloud-agnostic?
- Yes. Marsovius targets standards (Postgres, S3-compatible storage, OIDC, OpenTelemetry) and does not depend on any single cloud's proprietary services.
- — Can it run air-gapped?
- Yes. Sovereign customers deploy in fully disconnected environments. Releases are delivered as signed bundles. No outbound telemetry is required for operation.
- — How are updates delivered?
- Signed release bundles published to the Marsovius release registry, mirrored to customer registries. Major versions are LTS for 24 months. Pro and Sovereign customers receive long-term branches.
03
Sovereignty & exit
- — Who owns the data?
- You do. Marsovius is software the customer hosts. The house never receives a copy of your data. Lineage, ontology and policy are all stored in customer-controlled systems.
- — How do we exit the relationship?
- You stop paying for support and you keep running the open-source platform. Your data, your ontology, and your customisations remain on your hardware. The Pact of Sovereignty makes this contractual, not optional.
- — What if Marsovius is acquired?
- The Pact of Sovereignty refuses controlling investment from any entity not domiciled in EU/EEA. The clause is enforceable by the customer. If the house were to dissolve, the source remains under Apache 2.0 forever.
- — Can our regulator audit the platform?
- Yes. The source is published. For Sovereign customers, audit-grant access to source and infrastructure is provided to the customer's designated supervisory authority on request, without notice and without negotiation.
04
The Legates
- — Who are the legates?
- Senior engineers of the house — platform engineers, clinical data architects, defense systems integrators, econometricians, logistics operations researchers, commerce-platform engineers. The match to the customer is the first decision.
- — How long does a legate stay?
- Twelve months minimum. Longer where the engagement requires it. The legate attends design reviews, sits on architecture councils, and represents the house to your regulators.
- — Is the legate billable by the hour?
- No. Pricing is per institution. There is no per-hour or per-day billing. The conversation about cost begins after the audience is granted.
05
The category
- — How is this different from Palantir Foundry?
- Same category — the operational platform that combines ontology, pipelines, workflows, agents and digital twin. Different posture: open source, EU-domiciled, deployed on your hardware, exit guaranteed in writing.
- — How is this different from Snowflake or Databricks?
- Those are storage-and-compute warehouses. Marsovius is the operational layer above them: the ontology, the workflows, the agents. You can run Marsovius on top of either if you choose.
- — How is this different from dbt, Airflow, Dagster?
- Those are single-function tools (transformations, orchestration). Marsovius is the integrated stack: the same project ships pipelines, ontology, workflows, agents, digital twin, surfaces — bound by one semantic contract.
— VI —
A question well-answered is a relationship begun. The house reads every letter.