pre-mvp
All comparison categories

Sovereign and personal data systems

Data sovereignty becomes operational when the workspace can participate in real work.

Personal data stores and pods separate a person's information from individual applications. Legra shares that sovereignty goal and extends the workspace to graph knowledge, files, versions, executable Use Cases, organizational collaboration, contracts, and economic transactions.

Where this category excels

User-controlled storage and permissioned application access.

Separation of personal data from application-specific silos.

Standards-oriented interoperability and portability goals.

Where Legra extends the model

The same workspace model serves private individuals, teams, organizations, and published Data Products.

Graph history, branches, tasks, evidence, media, and conversations form one durable corpus.

A sovereign workspace can enter governed third-party Use Cases and transactions without surrendering ownership.

Questions to use in an evaluation

Can the workspace support collaborative and organizational knowledge as well as personal records?

How are changes, tasks, provenance, agreements, and disputes represented?

Can the owner safely acquire services or sell access and rights?

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.
Explore activity history

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.
Reasoning and derivations

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.
Data logistics infrastructure

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.
Data Products and contracts

Continue exploring

Follow the connected topics.

Choose your perspective