Data and content
Graph data, models, ontologies, documents, images, audio, video, messages, and arbitrary files.
A new infrastructure category
Legra is the infrastructure.
Data becomes economically useful only when an authorized party can find it, understand it, agree on its use, receive it, integrate it, verify what happened, and compensate the parties that contributed value. Legra connects that complete route around sovereign, independently operated graph workspaces.
A governed Data Product should become as easy to find, acquire, and integrate into a business process as a software package is to add to a project—without collapsing ownership, security, contractual, or economic boundaries.
What moves
Every block may travel like a parcel, but its value and permitted use come from the surrounding graph: what it means, who controls it, which work produced it, what may happen next, and who should receive value in return.
Graph data, models, ontologies, documents, images, audio, video, messages, and arbitrary files.
Concepts, relationships, taxonomies, provenance, Use Cases, and the objects around which work is organized.
Membership, encryption keys, permissions, policies, contracts, spending authority, and review boundaries.
Human and agent tasks, changes, derivations, decisions, failures, approvals, and reproducible results.
Data value, resource costs, operator services, charges, credits, commissions, and settlement—not a price derived from byte size.
The complete logistics loop
The architecture is designed around this loop. Catalog discovery, semantic supply-demand matching, first-class contract formation, and automated settlement remain planned surfaces; the workspace, graph, identity, execution, task, journal, and accounting foundations provide the substrate beneath them.
A Data Product combines data with meaning, ownership, interfaces, provenance, quality, policies, dependencies, service levels, and commercial terms.
Planned surface
Catalogs can make products and reusable Use Cases findable, while graph semantics let demand be matched to more than a keyword or file format.
Planned surface
Identity, rights, constraints, budgets, contracts, and permitted actions become explicit before data or services cross an authority boundary.
Storage, custody, transport, replication, transformation, and external services form one traceable route from a sovereign source to an authorized use.
Stories connect graph-defined intent to queries, workflows, pipelines, agents, UI actions, and existing APIs without hiding the business contract in code.
Economic direction
Task and activity evidence connects the result to actors, authority, inputs, costs, credits, data value, operator services, and token flows among the parties involved.
Global describes reach and participation—not an open-data policy. Workspaces may be private, shared, restricted, or public. Owners keep the cryptographic and governance boundary while selectively authorizing transactions with people, organizations, services, and agents elsewhere in the network.
Compare sovereign data systemsData value is independent of byte size. Legra's economic model composes data value with compute, storage, custody, transport, transformation, external I/O, rights, and operator services. Zero is an explicit price for self-operated work, while positive prices can compensate data owners and infrastructure providers.
Compare data spaces and marketplacesWhy this is a new category
Legra is not defined as another member of any one of them. Data logistics infrastructure connects their concerns into one graph-based operating and economic model.
Explore the technology landscapeChoose the next view
Business leaders, operations teams, data professionals, and technologists each enter the same system with different questions.