Solidus Pod vs Inrupt PodSpaces: two bets on what a Solid pod becomes

Both are development-stage offerings, and only one of them has a production product behind it. It is not ours.

The comparison a buyer actually needs, first

Neither of these is a production answer today.

Theirs says so in its own documentation, a Developer Preview, explicitly not for production or sensitive personal data, offered free in two regions as somewhere to test applications against the current server.

Ours says so on every page of this estate.

That symmetry is real and it is also misleading, which is why the next section exists.

Where the symmetry breaks, and it breaks against us

Their developer preview is a shop window for a commercial product, an enterprise Solid server with versioned releases, sold and deployed. Solid deployments in production exist, and they belong to that side of this comparison.

So "two free previews" is the wrong frame. Behind theirs is a business with customers. Behind ours is us. A buyer choosing on maturity should not be reading this page for permission to choose us.

What each is actually betting on

Their bet is that pods become enterprise infrastructure: an organisation runs pods for its users, and the value is in operating that reliably at scale, with support contracts and a hardened server.

Our bet is that the identifier layer underneath the pod matters: that a pod addressed by an identifier the user controls, with a record whose changes are visible, is worth more than one addressed by a domain someone else rents. We argue that bet rather than assert it, and the trust-anchor page concedes it is currently the weaker position.

Both bets can be right. They are not the same product, and one is much further along.

Five things this page refuses to say

Named, because the brief that fed this page contained all five and a later editor should know they were removed on purpose.

1. A per-verification price. No price is settled here, and printing one as though it were would be an invention.
2. Vocabulary belonging to a different product tier. That language describes another Solidus surface, not this one, and importing it here has already gone wrong once.
3. "Their stack lacks X." We have not measured their stack. An absence claim about somebody else needs a measurement, and we do not have one.
4. A differentiation claim resting on our selective-disclosure work. That work is unaudited. An unaudited mechanism is not a competitive advantage; it is a plan.
5. An internal scoring table and a how-hard-would-it-be-to-compete line. That is commercial strategy. It does not belong on a page a customer reads.

What is left after removing all five is a shorter page and a true one.

What is genuinely different, stated small

• They host; we host. Both are hosted offerings, and neither obliges you to use them: run the server yourself and neither of us is in your path.
• Their identity layer is Solid's own login model. Ours bridges to an identifier we anchor, with the portability gap that entails, generic tooling does not resolve ours.