The data economy needs logistics between discovery and settlement.
Data spaces and marketplaces help organizations discover and exchange data under common policies. Legra's destination is the operational substrate beneath that exchange: sovereign supply, Use Case demand, contracts, delivery, value-added services, execution evidence, and multidirectional settlement across Operators.
Where this category excels
Shared participation rules, catalogs, trust frameworks, and policy vocabularies.
Organizational ecosystems for controlled data sharing.
Commercial packaging and discovery of data offerings.
Where Legra extends the model
Workspaces and Data Products participate without requiring one proprietary central marketplace.
The logistics path includes custody, transport, transformation, execution, evidence, and settlement.
Individuals and small providers can use the same network model as large organizations and Operators.
Questions to use in an evaluation
What happens after a product is discovered and an agreement is accepted?
Can value-added intermediaries contribute and receive attributable payment?
Can participants retain their own infrastructure, identity, policy, and data authority?
Beyond database features
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.
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.
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.
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.