Personal data pods, data-monetization platforms, and where Solidus Pod sits
The four categories, kept apart
1 · Custody, personal data stores. Your data sits in storage you control; applications read what you permit. The value proposition is that nothing is pooled. Solid-based offerings live here, and so do independent open-source personal data stores, including one built by a Japanese consortium with pilots in healthcare, finance and tourism.
2 · Monetization, data marketplaces. Data is licensed, sold or attributed, usually with tokens, escrow or an on-chain attribution mechanism. The value proposition is that data gets used and someone gets paid. Why that pulls against custody.
3 · Durable storage substrates. Pay once, store for a long time. This is about persistence and economics, not about personal data models at all: a pod could sit on one, and the two answer different questions.
4 · Edge and AI data infrastructure. Orchestration and processing near where data is produced. Adjacent, and not the same problem.
Most confusion in this field comes from treating these as one market. They are not, and a product strong in one is usually absent from the others.
Where pod sits, and where it does not
Category 1. Only category 1.
Checked against our own repository rather than asserted: there is no marketplace, no escrow, no attribution mechanism and no payment path in what we have built, searched, with a control matching hundreds of files for something that genuinely exists.
So we do not compete in category 2, we are not a category 3 substrate, and we do nothing in category 4. Anyone comparing us on those axes is comparing us to something we are not offering.
Inside category 1, the ranking does not favour us
An established commercial offering has a production server, versioned releases and enterprise deployments, the comparison in detail.
An independent open-source personal data store has sector pilots and a consortium behind it.
What is genuinely ours is a bet about the identifier layer: that a pod addressed by an identifier its holder controls, with a record whose changes are visible, beats one addressed by a rented domain. We argue it and concede it is currently the weaker position. A bet is not a placement in a ranking.
What the source material wanted us to say, and why we refused
Three of the five briefs position us on a consent-receipt capability, as the anchor a marketplace's pricing layer composes with, or as an overlap with an attribution standard.
That capability is not on this surface. A grant is not a consent record: a pod grant carries a resource, an agent and permission modes, with no purpose, no scope and no expiry. The consent ledger that does have those fields belongs to another Solidus product and pod does not call it.
A composition story built on a capability the surface does not have is not a strategy; it is an error, and it would have been repeated across five comparisons.
We also print no third-party funding or traction figures. We did not verify them, they are more than two months old, and one figure in our own material did not survive checking.
Choosing, if you are actually choosing
- Want your data not pooled, in production, today? An established custody offering, or run the server yourself, which needs nothing from us.
- Want to be paid for your data? Category 2. We do not compete for that.
- Want cheap durable storage? Category 3. Different question entirely.
- Interested in whether the identifier under a pod should be chain-anchored? That is our argument, it is unfinished, and it is the only reason to read us on this subject.