Gaia-X
Two software models for federated data economies.
Gaia-X combines open specifications, rules, labels, and open-source software for trusted data and infrastructure ecosystems. Legra combines proprietary software with a graph-native P2P network for the same domain. Both enable federated data economies through cross-organization interoperability, ecosystem governance, trust, sovereign exchange, and economic participation.
Axis coverage
The six axes of the complete logistics loop. What each axis asks.
Same domain. Different operating models.
| Dimension | Gaia-X | Legra |
|---|---|---|
| Stewardship | Open specifications and open-source components evolve through the Gaia-X Association, contributors, operators, and implementation projects. | One vendor governs the proprietary codebase, integrated architecture, release train, and roadmap. |
| Federation architecture | Heterogeneous participants assemble standards-conformant credentials, clearing houses, catalogues, contracts, and data-exchange services. | Autonomous P2P nodes and sovereign graph workspaces share one protocol, runtime, and operational model. |
| Interoperability, governance, and trust | Common rules, ontologies, verifiable credentials, labels, and conformity services coordinate participating ecosystems. | Shared semantics, cryptographic identities, authorities, policies, agreements, licences, signed records, and execution evidence govern cross-organization work. |
| Source assurance | Public repositories permit continuous inspection, reuse, modification, and contribution under open-source licences. | Controlled third-party inspection and independent audits provide scrutiny without granting public modification or redistribution rights. |
| Commercial accountability | Accountability is contracted separately with selected operators, integrators, and software providers. | One supplier provides an end-to-end contractual counterparty for the integrated stack, subject to the purchased warranties, service levels, and indemnities. |
Compare the mechanisms.
Gaia-X
Open specifications and software support implementation by multiple vendors, operators, and data spaces.
Credentials, clearing houses, catalogues, ontologies, usage agreements, and data-exchange components establish shared federation machinery.
Association governance and conformity services coordinate trust across heterogeneous technology stacks.
Legra
One commercially governed stack carries identity, authority, policy, semantics, storage, custody, query, execution, evidence, and settlement.
P2P peers operated by different organizations form the federation while retaining workspace and data authority.
One vendor owns the integrated roadmap and provides an end-to-end contractual counterparty; controlled third-party source inspection supports independent assurance.
Questions to use in an evaluation
Ask these in the room.
- 01
Which federation model fits the ecosystem: multi-party component assembly or one integrated P2P infrastructure?
- 02
Which Gaia-X credentials, services, and protocols must the Legra network interoperate with?
- 03
Which guarantees, audit rights, source-inspection rights, and operational responsibilities belong in the supplier contract?
Graph features are only the substrate.
Legra also organizes the work that uses and changes the graph, the evidence needed to review that work, and the economic relationships that move data and value between parties. That operational layer is what turns graph infrastructure into data logistics infrastructure.
A complete history of the work
Legra keeps each piece of work together with the changes it made, the evidence behind it, and any costs incurred. That history stays private to the workspace and cannot be quietly rewritten.
- Work by people, AI agents, and automated services appears in one traceable record.
- See what is happening now, then return to the same history later for review.
Layered provenance
Full provenance connects signed commits and exact deltas to task and transaction lineage, actors, delegated authority, imports, and every retained rule and premise behind derived facts.
- Evidence answers who or what acted, on whose authority, from which inputs, and with which result.
- Commit, activity, fact-origin, and derivation evidence remains attached to the workspace and its history.
Composable transaction pricing
The admitted total composes independently priced data value, compute, storage, custody, transport, external I/O, rights, and operator services instead of treating bytes as the value of data.
- Charges, credits, refunds, penalties, and commissions contribute to the final amount.
- Zero is an explicit price through the same accounting path, including self-operated work.
Multidirectional token settlement
Every resource-consuming operation follows one path: measure, price, authorize, execute, record, and settle. Detailed evidence stays with the workspace instead of one central billing ledger.
- Tokens can flow to data owners, infrastructure and service Operators, and the NetworkOperator treasury.
- The same evidence supports internal chargeback and external settlement; subscriptions supply token packages rather than feature gates.