All guides
#ecosystem#sovereignty#nostr#architecture#self-host

Swap anything, trust nothing: the Obelisk four-piece stack

Obelisk is four small projects on one open protocol: chat, voice SFU, bot runtime, and relay. Any piece is replaceable, none is central.

5 min read
Swap anything, trust nothingThe Obelisk ecosystem: one self-hostable relay at the top connected to a chat client, a voice SFU, and a bot runtime, every piece independently replaceable.obelisk-relaySelf-hostable Nostr relay · whitelist · admin UIobelisk-dexWeb chat clientbrowser · NIP-07obelisk-sfuVoice mixing serverWebRTC · large callsobelisk-botsBot runtimemod · games · opsfour projects · one protocol · no central server

The short version

Most chat apps are one company. One server, one database, one team that can change the rules tomorrow. If you don't like Discord, you can leave Discord, but you can't take your community with you. The data, the identity, the history all stay behind.

Obelisk is built to look nothing like that. It's a Discord-style group chat, but instead of a single backend, it's four independent projects that talk to each other through Nostr relays. Pick the pieces you trust and ignore the rest.

The four pieces

The Obelisk ecosystem: one self-hostable Nostr relay connected to a chat client, a voice SFU, and a bot runtime: every component independently replaceable, nothing locked together.
  • obelisk-dex logo mark: a chat bubble containing the Obelisk monument, representing the browser chat client that signs Nostr events and posts them to a relay. obelisk-dex: the chat client. It's what you see in the browser when you open obelisk.ar. It signs messages with your key and sends them to a relay. That's almost all it does.
  • obelisk-sfu logo mark: a central voice mixer hub connected by spokes to five peers, representing the Selective Forwarding Unit that mixes streams for large group calls. obelisk-sfu: the voice server for large calls. When a group call gets too big for everyone to talk to everyone directly, the SFU mixes the streams. It signals through Nostr like any other participant.
  • obelisk-bots logo mark: a small robot head with an antenna, representing the bot runtime where each bot has its own Nostr keypair and posts messages like any user. obelisk-bots: the engine that runs bots. Moderation bots, game bots, integration bots. Each bot has its own keypair and posts messages the same way a human user does. There is no special bot API.
  • obelisk-relay logo mark: a relay tower broadcasting concentric signal arcs, representing the self-hostable Nostr relay with built-in whitelisting and admin UI. obelisk-relay: a Nostr relay you can run yourself. It comes with whitelisting built in and a CLI that gets you online in a few minutes. There's a web UI for managing it without touching the terminal.

None of these four projects import each other's code. They've never had to. They all speak the same protocol and meet on the relay.

The protocol is the bus

In a normal app, the frontend calls the backend through an API. The bot framework hooks into the chat server. The voice service authenticates against the user database. Every component depends on every other component. Replace one piece and three things break.

Nostr changes this. A relay is a public bus for signed messages. Anything that can sign and publish can join the conversation. Identity is just a public key. Authorization is just a signature. There is no shared database to coordinate.

So when a bot wants to send a message, it doesn't call an API on the client. There is no API on the client. It publishes a signed event to a relay, and any client subscribed to that group sees it. Same path, same rules, same guarantees as a human typing in their browser.

When the SFU wants to start a voice session, it doesn't ping a central server. It exchanges WebRTC signaling as Nostr events. The SFU is just another participant.

When the relay wants to enforce a whitelist, it doesn't need to know what bots exist or which client you're using. It checks your signature, checks your pubkey against its allowlist, accepts or rejects. Done.

Why this makes the ecosystem resilient

This is the part that matters. Because every piece is replaceable, no single piece can hold you hostage.

Obelisk swap matrix: every layer of the stack - client, voice, bots, relay - has independent alternatives, so any one component can be replaced without changing the others.
Every layer of the stack has alternatives. Nothing imports anything else, so nothing can secretly require anything else.
  • Don't trust our client? Use a different one. Any Nostr client that supports group chat will work against the same relays and see the same messages.
  • Don't trust our SFU? Run a different one, or use a different voice implementation entirely. The signaling is on the wire and you can audit it.
  • Don't want our bots? Write your own, or use someone else's. Bots are just keypairs that publish events. There's no framework you have to adopt.
  • Don't want to run our relay? Run any NIP-29 relay. There are several implementations. Your community moves over by changing the relay URL.

Want to mix and match? Go ahead. Use our client with someone else's relay. Use our relay with someone else's client. Use our bots with their voice server. The pieces don't care.

The relay is the sovereign part

Of the four pieces, the relay is the one that matters most for sovereignty. The client is a browser tab. The SFU is a temporary peer. The bots are stateless processes. The relay is where group history lives, where membership is enforced, where moderation happens.

If you want a community you actually control, run your own relay. That's why obelisk-relay was built with whitelisting first. A community that owns its relay owns its data. A community that rents a relay owns nothing.

The CLI is for technical operators who don't want to click. The web UI is for everyone else. They both manage the same allowlist, see the same connected users, point at the same database.

Why one developer can ship this

Building four projects sounds like more work than building one. In practice it's less, because the protocol does the integration work.

  • We don't write authentication. The signature is the auth.
  • We don't write a user database. Public keys are the identity.
  • We don't write a message bus. The relay is the bus.
  • We don't write client/server contracts. The Nostr event format is the contract, and it's already specified in NIPs that other people maintain.

What's left is the chat experience, the voice mixing, the bot runtime, and the relay implementation. Each one is a focused project with a clear job. None of them have to know about the others. That's why a solo dev can carry it.

Try any piece you want

Everything is open source. Fork it, swap it, replace it.

If you build something that talks to any of these, it works. That's the whole point.

How Obelisk worksOn a usual chat platform, your account, your data and the rules live on the company's server, between you and your community. In Obelisk you sign each message with your own key and it goes straight to your community's relay, a NIP-29 relay: Obelisk runs a public one, and anyone can run their own. The Obelisk app only signs and shows.A USUAL CHAT PLATFORMYoumessageThe company's serveryour account · your data · its rulesYour communityOBELISKYou, with your keysigned messageYour community's relayObelisk's relayor your ownYour communityUse Obelisk's relay or run your own: your community depends on no one.

How Obelisk works

the no-backend architecture

Web of Trust graphA trust graph with your node at the center, connected nodes in lime green for high trust, and red-outlined spam nodes at the periphery.YOU!!!direct followfriend-of-friendfiltered (spam)

Bring your own relay

relays as sovereign communities

Future: Nostr relay-based groupsA mesh of Nostr relays exchanging encrypted group messages, with no central server.relay.arelay.brelay.crelay.drelay.erelay.fNIP-29 group

What shipped, and what's next

what's still being built

Admission is a ladder, not a switchA self-hosted Nostr relay with three widening tiers of admitted keys around it, added by hand, two hops away, three hops away, each publishing on a smaller share of the rate budget, with a block list cutting across all three.relayyoursTIER 1added by hand6,000/minTIER 2two hops3,000/minTIER 3three hops1,500/minBLOCKEDchecked first, overrides every tiernothingDistance from your reference accountsis how much evidence you have.

Run your own relay: admission is a ladder, not a switch

running the sovereign part yourself