MARSOVIVS

Sovereign data infrastructure·Apache 2.0·Built in Europe

Foundry was the question. We are the answer in the open.

Marsovius is the open-source operational platform that gives every institution — from a single online shop to a sovereign government — the same ontology, the same digital twin, the same auditable predictions, the same code.

And, when you want one, the same legate of the house sitting beside your team.

I

Palantir proved that an operational platform can change how a ministry, a hospital, a fleet command — or a shop with twenty branches — actually works. What it has not done is open the foundations. Marsovius does.

The architecture

Five layers. One contract.

Marsovius is not a single product. It is a stack of five layers that share one semantic contract — the ontology — and operate together as a single system of truth across the institution.

VSurfacesworkspaces · case files · field apps · operator HUDs · storefrontsReact · TSIVAgentsassisted · autonomous · boundedtyped toolsIIIWorkflowsversioned · signed · replayableDSL · WASMIIOntologyobjects · links · actions · the contract of meaningRust · kernelIPipelinesingest · transform · serve · lineage from source to leafIceberg · CHEHR · ERPCRM · POSIoT · sensorsCSV · APISource systems
  1. V

    Surfaces

    The operator-facing applications. Workspaces, case files, operational HUDs, storefront surfaces. Built on the ontology so that every interaction is bound to a contract.

  2. IV

    Agents

    Assisted and autonomous decision agents. They cannot operate outside the ontology — every action is typed, traced, and revocable.

  3. III

    Workflows

    Long-running, versioned business processes. Each step transition is signed. Each branch is replayable. Each rule is reviewable in court.

  4. II

    Ontology

    The semantic core. Objects, relationships, allowed actions. The shared contract that a thousand workers — or a single shopkeeper — agree to when they say "patient", "order", "asset".

  5. I

    Pipelines

    Source-of-truth ingestion and transformation. Lineage from the raw source to the leaf field. Every transformation auditable, every dataset attributable.

Capabilities

The four capabilities of an operational platform.

Ontology is the contract. The digital twin is the live shadow of the operation. Predictions are bound by the ontology. Agents act only through it.

Capability I

Ontology

The contract of meaning.

VISITSPLACESOWNSSERVESOPERATESYIELDSSubjectVisitOrderAssetOperatorWorkflowOutcome

A versioned, typed semantic model of every object the institution cares about — subject, order, asset, branch, outcome — and the actions allowed on them. Every dashboard, every workflow, every agent acts through this contract.

  • · versioned types
  • · typed actions
  • · lineage-aware
  • · reviewable as code
Capability II

Digital twin

A live shadow of the operation.

PhysicalDigitalWarehouseFleetBranchPatientwh-01.warehousefl-04.fleetbr-22.branchpt-9183.subjectingest · represent · predict · act

Marsovius keeps a continuous digital replica of the physical world: a warehouse, a fleet, a hospital floor, a population. The twin is queried like data, simulated like a model, and synchronised in both directions in real time.

  • · bidirectional sync
  • · scenario simulation
  • · what-if branches
  • · event-time replay
Capability III

Predictions

Forecasts bound by the ontology.

actionobservedforecast · 95%valuenow

Demand, risk, capacity, throughput, mortality, congestion. Forecasts are first-class objects in the ontology — their inputs are traceable, their confidence is published, and the action they trigger is signed.

  • · traceable inputs
  • · published confidence
  • · human-in-the-loop
  • · signed actions
Capability IV

Agents

Bounded by the ontology.

Policy perimeterAgentboundedlookup(Subject)tool · Ischedule(Visit)tool · Jsign(Outcome)tool · K

Assisted and autonomous agents that cannot operate outside the ontology. Every tool call is typed. Every action is signed. Every capability is scoped by policy and revocable by the institution at any moment.

  • · typed tools
  • · capability scopes
  • · signed actions
  • · revocable in one call

The Legates

We do not sell a tool. We send a person.

A legate of Marsovius — Latin legatus, the senatorial governor of a Roman province — is a senior engineer of the house sent to the customer's premises to install the platform, design the ontology, train the operators, and remain as counsel. Setup, training, advisory, companionship. Included in the relationship.

D + 0AudienceD + 10MatchD + 20ProtocolD + 30OntologyW + 12ProductionM + 12Companion→ ongoingSetup · onboardingTraining · counsel · companionship
I

Setup

The legate installs Marsovius in your environment, connects it to your existing systems, designs the first ontology with your subject-matter experts, and stands up the first workflows. From kickoff to first production decision: six to twelve weeks.

II

Training

The legate transfers every skill they use to the customer’s engineers, data teams and operators. Marsovius is not a black box and the training is not a course. Within ninety days the customer’s team runs the platform without house involvement.

III

Counsel

The legate remains as a standing advisor for architectural decisions, ontology evolution, model selection and incident response. The counsel is not billed by the hour. It is included in the relationship.

IV

Companionship

The legate stays attached to the customer for twelve months at minimum. They attend design reviews, sit on architecture councils, and represent the house when the customer’s regulator asks how a decision was made.

The four pillars

.01

Sovereign

Deployed on your hardware, in your jurisdiction, under your law. The data and the code remain where your sovereignty does.

.02

Open

Apache 2.0, from foundation to surface. Every algorithm that governs a decision is inspectable, auditable, forkable by your engineers.

.03

Operational

Not a dashboard. Ontology, pipelines, workflows, agents, twin. The architecture that makes everyone act on the same truth.

.04

European

Designed in Europe, hardened against the standards that govern hospitals, ministries, and defense procurement on this continent.

For whom

From a single online shop to a sovereign government.

The same architecture serves a shop with one branch and a state with sixty ministries. The licence does not change. The ontology grows. The code is the same.

  1. 01

    Online commerce

    A single shop.

    1 – 50 operators

    A storefront unifies its catalogue, its orders, its inventory and its customer support into one ontology. Predictions of demand drive replenishment. A digital twin of the warehouse keeps stock honest. Self-hosted on a single node — or run with a legate beside the team.

  2. 02

    Small & mid-market

    A growing company.

    50 – 2 000 operators

    A manufacturer, a logistics operator, a regional retailer with twenty branches. Marsovius replaces the patchwork of spreadsheets, ERPs and BI tools with one operational layer. A legate installs the platform and stays as counsel for the first year.

  3. 03

    Public health

    A hospital network.

    2 000 – 30 000 operators

    A regional health authority unifies six EHRs, two registries, and a clinical-trial pipeline. Outcomes are read by every clinician from the same definition of "patient". A clinical-data-architect legate designs the ontology with the chief medical officer.

  4. 04

    Ministry & administration

    A national institution.

    10 000 – 250 000 operators

    A tax authority replaces three legacy intake systems with one workflow layer. Each decision is bound to a versioned rule and reviewable in court. The digital twin of the population is held inside the national perimeter. A legate sits on the architecture council.

  5. 05

    Defense & sovereign

    A force command.

    air-gap · classified

    A defense organisation runs Marsovius on a sovereign cloud, air-gapped where required. Source is held in an EU repository. The audit chair holds the keys. Cleared legates remain on premises for the duration of the engagement.

What we replace

The category is right. The form of delivery is not.

VendorSource modelDeploymentOntology layerSovereignty
Palantir FoundryClosedSaaS / on-premYesUS-controlled
Snowflake / DatabricksClosedSaaSNoUS-controlled
dbt · Airflow · DagsterOpenSelf-hostedNoVariable
MarsoviusApache 2.0Self-hostedYesEU / customer

Marsovius is the only entrant that combines the operational-platform category with an open-source licence and a European sovereignty commitment.

Editions

One codebase. Three postures.

The same source under Apache 2.0 — community, professional, or sovereign. The code is identical. What changes is the relationship the house enters into, and the legate it sends.

01 · free

Community

Apache 2.0 · self-hosted

The full platform. No licence cost. No registration. Used by a single online shop or a research lab the same way it is used by a hospital network in production.

  • ·full source
  • ·all capabilities
  • ·community support
  • ·no telemetry
Inspect the source
02 · commercial

Pro

Per institution · no list price

Production hardening, professional support, named SLAs, security review, and a legate of the house for setup, training, and counsel throughout the first year of deployment.

  • ·a legate, included
  • ·production SLAs
  • ·security review
  • ·long-term branches
Request an audience
03 · pact— sealed —

Sovereign

Subject to the Pact of Sovereignty

The most binding posture the house offers. Cleared legates on premises, air-gap-capable deployment, source in EU registries, and audit-grant access to the customer’s supervisory authority.

  • ·Pact of Sovereignty
  • ·cleared legates on premises
  • ·air-gap capable
  • ·audit-grant access
Read the Pact

— II —

The same operational truth for the smallest shop and the largest state. The same code. The same audit. The same right to leave with everything.

We do not publish prices. We accept audiences.

— Marsovius · MMXXVI —

III

Inspect the source. Engage a legate. Or request an audience.

Marsovius is free to inspect, fork, and self-host under Apache 2.0 — by any organisation, of any size, in any jurisdiction. For installation, training, counsel and the Pact of Sovereignty, the four desks below answer within three working days.

Legates of the house

legates@marsovius.com

Defense & sovereign

sovereign@marsovius.com

Patronage & alliances

house@marsovius.com