SAND Architecture
How Solid, ActivityPub, Nostr, and DID work together. A visual guide to the stack.
The Full Picture
Protocol Roles
Each protocol has a distinct role in the stack:
| Protocol | Role | Strength |
|---|---|---|
| Solid | Data storage & access control | Structured data, permissions |
| ActivityPub | Federation & social | Server-to-server communication |
| Nostr | Real-time & censorship-resistance | Simplicity, resilience |
| DID | Identity | Portable, self-sovereign |
Data Flow: Reading a Profile
Data Flow: Social Posting
A single post can:
- Store in your Solid pod (your archive)
- Broadcast to Nostr relays (public, censorship-resistant)
- Federate via ActivityPub (reach Mastodon users)
Authentication Flow
Solid-OIDC
Nostr (NIP-98)
Server Architecture: Sandymount
Client Architecture: Typical Solid App
Multi-Protocol Agent Architecture
See Also
- Protocols Overview — Individual protocol details
- Concepts Overview — Foundational ideas
- Sandymount — Run the full stack