A new infrastructure category
Marketplaces are applications. Data logistics is infrastructure.
Legra turns the foundations every data system rebuilds into shared capabilities across sovereign workspaces.
Every silo rebuilds them. Legra provides them once.
Applications and Use Cases
Business value lives above the infrastructure.
Marketplaces use the same foundations as every other application.
Marketplaces & Data Products
Catalogues connect governed supply to executable demand.
Apps, agents & workflows
Use Cases bind outcomes to personas and tested stories.
Digital twins & simulations
The default branch mirrors today. Scenario branches model possible futures.
Core data-management foundations
Twelve disciplines · one operating model
Define
Operate
Trust
Legra data logistics infrastructure
Sovereign graph workspaces
Knowledge, content, and files share one governed corpus.
Branched timelines
Query the past. Govern the present. Fork possible futures.
Journal + settlement
Every task journals its authority, work, and outcome. Tokens flow to contributors.
Follow the complete logistics loop.
Shared meaning
Can people, systems, and agents interpret the same concepts and relationships?
Sovereignty
Can each party retain authority over private, shared, restricted, and public data?
Agreements
Are rights, responsibilities, authority, policy, and commercial terms explicit?
Execution
Can governed Use Cases connect models to human, agent, service, and code execution?
Evidence
Does work leave durable, attributable, reviewable history around the objects involved?
Economic exchange
Can data, rights, resources, services, and settlement participate in one value flow?
Ten established categories. One connected infrastructure problem.
Start with the platform family you know. Product matrices are deliberately separated by type: RDF stores are compared with RDF stores, LPG stores with LPG stores, and unlike categories are not folded into one master scorecard.
Knowledge graphs and graph databases
Represent, connect, query, infer over, and explore graph-shaped knowledge.
Lakehouses, fabrics, integration, and ETL
Collect, transform, govern, and serve data across analytical and operational estates.
Catalogs, data meshes, and Data Product platforms
Describe ownership, quality, discoverability, interfaces, and governed consumption.
Workflow, BPM, low-code, and orchestration
Coordinate process steps, decisions, tasks, approvals, applications, and people.
APIs, iPaaS, service meshes, and event platforms
Connect applications and transport requests, messages, and events between services.
RAG, vector databases, agent memory, and AI platforms
Retrieve context, generate outputs, coordinate agents, and provide model-facing tools.
Blockchain and smart-contract platforms
Execute deterministic on-chain code and establish shared transaction state through consensus.
Personal data stores and pods
Give individuals a controlled place for personal data and permissioned application access.
Federated data spaces and marketplaces
Establish trust frameworks, catalogs, policies, and exchange between organizations.
Content, document, and collaboration platforms
Help people create, discuss, share, approve, and retain documents and media.
Go deeper from your current technology stack.
Choose your perspectiveRDF and semantic graph platforms
RDF is part of the foundation, not the boundary of the product.
Compare Legra with RDF databases and semantic graph platforms across graph semantics, reasoning, query, versioned workspaces, sovereignty, and data logistics.
Read comparisonRDF and SPARQL engines
A focused SPARQL engine and a data logistics infrastructure solve different layers.
Compare Legra with focused RDF and SPARQL engines across standards support, execution architecture, indexing, versioned change, sovereignty, and operational scope.
Read comparisonLabelled property graph platforms
Property-graph ergonomics should not require a separate knowledge world.
Compare Legra with property-graph and multi-model platforms across developer ergonomics, graph querying, semantics, reasoning, history, sovereignty, and execution.
Read comparisonVersioned graph databases
Versioning preserves change; a living corpus must also organize the work.
Compare Legra with graph databases built around immutable history, branching, time travel, and ledger-style change.
Read comparisonLinked Data and pod servers
A controlled place for Linked Data is the beginning of sovereignty, not the end.
Compare Legra with Linked Data servers and personal data pods across identity, standards, authority, history, encryption, execution, and exchange.
Read comparisonLocal-first and P2P databases
Peer-to-peer movement is a transport property; data logistics is the operating model around it.
Compare Legra with peer-to-peer and local-first databases across offline work, convergence, content addressing, graph meaning, authority, and managed logistics.
Read comparisonDecentralized knowledge networks
A knowledge economy needs verification and value flows without forcing all knowledge on-chain.
Compare Legra with tokenized and blockchain-anchored knowledge networks across semantics, verification, privacy, execution, governance, and economic exchange.
Read comparisonData platforms
Moving and storing data does not by itself create shared meaning.
Understand how Legra relates to lakehouses, warehouses, fabrics, operational stores, and analytical data platforms.
Read comparisonData Product platforms
A Data Product becomes valuable when a Use Case can safely put it to work.
Compare catalogs, data meshes, contracts, and Data Product platforms with Legra's supply-and-demand model.
Read comparisonWorkflow and BPM platforms
A process is only one view of the knowledge required to perform the work.
Compare process orchestration with graph-modelled Use Cases, executable Stories, governed knowledge, and durable activity evidence.
Read comparisonIntegration platforms
Connectivity transports data; logistics preserves its purpose and obligations.
Compare ETL, iPaaS, API management, service meshes, and event platforms with graph-based data logistics.
Read comparisonAI context and agent platforms
AI needs a repository of work, not another temporary context window.
Compare RAG, vector databases, agent memory, orchestration, and model platforms with Legra's living graph of work.
Read comparisonBlockchain and smart contracts
Serious agreements contain more than deterministic code on a shared ledger.
Compare deterministic blockchain execution with private graph-based agreements, governed work, evidence, and conventional settlement.
Read comparisonSovereign and personal data systems
Data sovereignty becomes operational when the workspace can participate in real work.
Compare pods, personal data stores, and sovereign data services with graph workspaces designed for individuals, teams, and organizations.
Read comparisonData spaces and marketplaces
The data economy needs logistics between discovery and settlement.
Compare federated trust frameworks and centralized marketplaces with Legra's global data-logistics infrastructure.
Read comparisonGaia-X
Two software models for federated data economies.
Compare Legra and Gaia-X as federated data-economy software across architecture, interoperability, governance, trust, source assurance, and commercial accountability.
Read comparisonContent and collaboration platforms
Knowledge should stay connected to the objects and Use Cases it is about.
Compare document, content, messaging, and collaboration systems with a graph-organized corpus of work.
Read comparison