Linked Data and pod servers
Solid and AtomicServer organize data around web identity, typed resources, links, and controlled access. They are better understood as Linked Data and pod servers than as RDF database engines: application-facing data ownership is their primary product boundary.
Where this category excels
Web-native resource identity and links between independently published data.
Application access mediated by the person or organization controlling the server or pod.
A practical sovereignty model that does not require one application to own every record.
Where Legra extends the model
Workspaces add encrypted custody, versioned branches, graph reasoning, and offline operation to controlled data ownership.
The corpus can include files, media, conversations, tasks, agreements, and execution evidence around graph objects.
Individuals and organizations can participate in governed transactions and multidirectional value exchange across operators.
Questions to use in an evaluation
Do applications only need permissioned resource access, or a continuously improving shared corpus?
Must the storage provider remain unable to interpret encrypted workspace content?
Will personal data participate in contracts, execution, provenance, and settlement with third parties?
Beyond database features
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.
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.
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.
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.
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.
Product-level technical deep dive
This matrix includes only products in the same directly comparable family. Adjacent product types belong in their own guide instead of making one oversized, apples-and-oranges scorecard.
Decentralized personal data pods with linked data and user-controlled access
| Feature | Legra | Solid | AtomicServer |
|---|---|---|---|
| Architecture | |||
| Peer-to-peer distribution | |||
| No central server required | |||
| Data Model & Query | |||
| RDF / Linked Data native | |||
| Full-text search | |||
| Query Languages | |||
| RDF 1.2 | |||
| SPARQL 1.1 | |||
| SPARQL 1.2 | |||
| RDF-star (RDF*) | |||
| openCypher | |||
| ISO GQL | |||
| SQL | |||
| Graph Store Protocol | |||
| GraphQL | |||
| Proprietary query language | |||
| Versioning & Branching | |||
| Git-style branching | |||
| Immutable commits | |||
| Delta / diff queries | |||
| Security & Encryption | |||
| Decentralized identity (DIDs) | |||
| planned | |||
| Enterprise & Operations | |||
| High-availability clustering | |||
| OWL / RDFS reasoning engine | |||
| Datalog reasoning | |||
| SWRL / RIF rules | |||
| LPG reasoning | |||
| SHACL / ShEx validation | |||
| Managed cloud offering | |||
| Visual graph explorer / GUI tools | |||
| Production-ready today | |||
| AI & Vector | |||
| Built-in vector search | |||
| Versioned vector indexes | |||
| Encrypted vector search | |||
| Data Model Breadth | |||
| Property graph / LPG support | |||
| ACID transactions | |||
| Immutable transaction history | |||
| Indexing & Performance | |||
| Ad-hoc index creation | |||
Continue exploring