Solidus Pod

A vault for the credentials that prove who you are

Most storage treats a diploma, a KYC result or a licence as a file with a name. A pod treats it as a credential: something signed by whoever issued it, checkable by whoever you show it to, and disclosed a field at a time rather than whole. Files live here too. Credentials are the reason it exists.

Create a pod Sign in What it does today

Per-file, per-person access
Readable by any Solid client
Your DID is the address

pod.solidus.network/<slug>/credentials

Issuer: Solidus Verify
Subject: did:solidus:testnet:7xKp…

over_18trueReleased
countryTRReleased
date_of_birthWithheld

A credential mid-disclosure: two fields released, one withheld.

What it does today

Credentials as first-class objects

SD-JWT VC and JSON-LD credentials are parsed, displayed and stored as credentials, not as opaque files. This is the capability ordinary storage does not have.

SD-JWT VCJSON-LD

Access control per resource, per person

Web Access Control rules attach to individual resources and name individual agents. Not a folder-level toggle, and not a setting you ask support to change.

acl:accessTo <tax-2024.pdf> ;
acl:agent <https://accountant.example/#me> ;
acl:mode acl:Read .

Readable by other Solid clients

Every resource is LDP over HTTP, so a different Solid application can read your pod without asking us. Portability you can test rather than a promise.

curl -H "Accept: text/turtle" \
  https://pod.solidus.network/<slug>/

Ordinary file storage

Upload, download, folders, drag-and-drop with multiple files. A working file store, underneath the credential layer.

Encryption is per-file and opt-in, access is revoked by you rather than by an expiry timer, and pod runs in the browser.

What we do and don't do

On Solid, and where we actually stand

Solid is the W3C-community specification Tim Berners-Lee started, and it is the reason another application can read your pod without asking us. Pod runs an unmodified Community Solid Server with a did:solidus bridge, so what you build on is the reference implementation rather than our interpretation of it. We say Solid-compatible, and we publish exactly where we stand against the conformance suite.

Pod runs on Solidus's public testnet and has not completed a security audit.

Hold your own credentials

A pod takes a minute to create, costs nothing, and you can export everything from it at any time.

Create a pod