Your communities, under your control

Discord-style group chat built directly on Nostr relays.

No accounts. No backend. Your keys, your relays.

Obelisk mobile relay switcher: rotating cards with real relay banners, descriptions, and controls to browse or add a relay.

Watch the walkthrough.

Explore Obelisk and its ecosystem: communities, voice, zaps, and a shared island.

Obelisk walkthrough video · 1/5

Follow Obelisk.

News, videos and what's next, wherever you scroll.

Why Obelisk.

All the chat. None of the servers. Your keys, your relays, signed events.

Groups on any relay

Channels and members are open NIP-29 events. No lock-in.

Private DMs

End-to-end encrypted. Only you and the recipient can read them.

Voice, peer to peer

Calls go straight from browser to browser.

No backend

No database, no servers. Your browser talks straight to the relay.

Bitcoin zaps

Send sats from any message. No custodian, no platform fee.

Games in chat

Chain Reaction, Vesta and Stacker, with no game server.

Three steps.

No signup forms. No email verification. Just keys and relays.

01

Sign in with Nostr

Use a NIP-07 extension, a signer app over NIP-46, or paste an nsec. No signup forms, no email, no password.

02

Pick a relay

The default groups relay is preloaded. Add any NIP-29 relay you like: each one becomes its own 'server' in the rail.

03

Chat

Join NIP-29 groups, post messages, react, reply, DM. Every action is a signed Nostr event going straight to the relay.

Learn.

How a pure Nostr client works, what NIP-29 groups are, and how to bring your own relay.

What is ObeliskAn obelisk monument surrounded by orbiting Nostr keys and floating chat bubbles.Kn

What is Obelisk?

Obelisk is a Discord-style group chat client with no backend. There's no database, no Obelisk server. Your account is a Nostr keypair, your groups live on Nostr relays, and the app is just a frontend that signs and reads events.

#intro#nostr#identity
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

Obelisk is a web app with no backend of its own. It signs Nostr events with your key and sends them straight to your server, which is a NIP-29 relay, and to the other relays it needs. Here's what happens when you log in, send a message or join a group.

#architecture#how-it-works#nostr
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

Obelisk has no central server; instead, you connect to any NIP-29 Nostr relay you trust. Each relay shows up as its own server in the rail. Here's how the multi-relay UX works and why it matters.

#relays#nip-29#sovereignty
Bitcoin zaps in chatA chat message with a glowing lightning bolt flowing into it, orbited by sat particles representing a Lightning zap paid from your wallet, through Nostr Wallet Connect or a WebLN extension.Your wallet+21+42+63+84+105+126+147+168Lightning (NIP-57) chat message

Bitcoin zaps in chat

Obelisk lets you send Bitcoin over Lightning directly from a chat message using NIP-57 zaps, paid by a wallet you connect with Nostr Wallet Connect (NIP-47) or by a WebLN browser extension. No custodian, no platform fee, no middleman. Just your wallet, the recipient's wallet, and a signed Nostr event.

#bitcoin#lightning#nwc
Admin tools in the appThe relay operator's server settings and a channel admin's channel settings, side by side. Both publish signed events to a NIP-29 relay, which checks and enforces them.NIP-78NIP-29Server settingsrelay operator onlyServer profileEmoji & stickersChannels & categoriesRoles & ranksMembers & moderationChannel settings#general ACCESSpublicread-onlyprivateTYPEtextvoice & videopublicationsMEMBERSaliceadmindemotebobmemberremove+ add by npubNIP-29 relaychecks and enforcesrelay operator: the whole relaychannel admins: their channelevery click is a signed event

NIP-29 admins, members, and moderation

How admins run a relay community in Obelisk today. Channel admins edit their channel and its members from channel settings; the relay operator manages roles, members, emoji and layout from server settings. Every action is a standard NIP-29 event that any Nostr client can read.

#moderation#nip-29#admins
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

Obelisk is a pure Nostr client with no backend. Voice channels, NIP-46 signer-app login, NIP-44 v2 encryption and the installable app have shipped. Still ahead: a static-export build and push notifications while the app is closed.

#roadmap#nostr#nip-46
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

Obelisk Relay is a NIP-29 relay that decides for itself who may connect: a hand-written allowlist, the accounts your references follow, and the follow graph beyond them, each on a smaller share of the rate budget. Two commands to run one.

#relay#self-host#nip-29
A cell going critical on a Chain Reaction boardA dark grid of cells holding red, lime and cyan orbs. One cell is bursting and sending an orb into each of its four neighbours, the cascade that gives Chain Reaction its name, played over a Nostr relay in Obelisk.One orb over the limitevery neighbour takes one,and may burst in turnkind 2390 {"op":"move","cell":11}the cascade is replayed,never publishedseat 1seat 2seat 3

Chain Reaction, played on a relay

Drop an orb, take a cell, and when a cell holds one orb too many it bursts into its neighbours, and their neighbours. Chain Reaction runs in an Obelisk channel with no game server; every client replays the same event log and reaches the same board.

#games#chain-reaction#nostr
Two Stacker wells trading garbage linesTwo ten-column wells of falling coloured blocks side by side. A completed line in the left well sends grey garbage rows into the right one: the only thing that crosses the Nostr relay in a real-time Obelisk Stacker match.Clear a line……and somebody else digsop: attack lines 3 · hole 6 Every board runs locally at sixty frames a second; only the consequences are published.

Stacker: real-time falling blocks over Nostr

Six players, one shared piece order, and every line you clear buries somebody else. Stacker runs its board locally at sixty frames a second and publishes only the consequences: attacks, top-outs, and checkpoints anyone can replay.

#games#stacker#real-time
A Vesta island with dice derived from the event logA hexagonal island of forest, brick, wool, grain and ore tiles with numbered dice tokens and player settlements, beside the line of the Nostr event log the dice roll is derived from: nobody at the table rolls their own numbers.1058694Nobody rolls their own dicethe numbers come out of the event logentropy = 3f9c…a12 : 14 4 + 3 = 7…and every client derives the sameroll from the same log.

Vesta: settlements, trade, and dice nobody rolls

Vesta is a settlement-building game running inside an Obelisk channel. The rules come from an upstream package we track rather than fork, the dice are derived from the event log instead of rolled by a player, and every client checks every move.

#games#vesta#nostr
A message sealed by two layers of protectionA classic Nostr key exchange wrapped in an outer post-quantum shell, with a locked envelope at the center representing a hybrid-protected direct message.classic key exchangepost-quantum layer

Making your DMs quantum-safe

Encrypted messages you send today can be recorded now and read years from now, once a quantum computer breaks the key exchange Nostr uses. This is the one part of the problem you can fix in advance, and there are two ways to do it.

#security#post-quantum#direct-messages
Obelisk Bots and the zap botA stylish zap bot with black sunglasses listening for Nostr zap receipts and posting signed announcements into NIP-29 Obelisk groups.zap receipt kind 9735reaction kind 7 zapgroupsNIP-29 scanannouncementkind 9 post ZAP BOT9735kind 7NIP-29kind 9own nsecNIP-42PM2

Obelisk Bots: Nostr agents for groups, zaps, and ops

Obelisk-bots is the bot runtime for relay-only Obelisk groups: small Node scripts with their own Nostr keys that listen to NIP-29 group events, announce zaps, run tickers, and automate community operations without a backend.

#bots#nostr#nip-29
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

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.

#ecosystem#sovereignty#nostr

Ready to chat without a server?

Open the app, log in with your Nostr keys, pick a relay. That's it.

Launch Obelisk

Frequently Asked Questions.

Short answers about the new Nostr-only Obelisk.

Obelisk is an open-source, Discord-style group chat client that runs entirely on Nostr. There is no backend and no database: every message is a signed Nostr event published directly to the relays you choose. Groups are NIP-29 groups, DMs are encrypted Nostr DMs, and your account is a Nostr keypair.
No. Obelisk is a frontend. There is no signup, no email, no password, and no Obelisk account. You log in with a Nostr key and the app talks straight to your configured relays: there is no Obelisk application backend or database. Messages live on relays. Obelisk operates two public relays; every other relay is controlled by its own operator.
Whatever relays you tell it to. New installs currently include wss://public.obelisk.ar and wss://lacrypta-relay.obelisk.ar, both operated by Obelisk. You can add, remove, or replace relays from the relay rail. Every other relay is independent and controlled by its own operator.
No. Obelisk has no signup form. You log in with a Nostr key: through a browser extension (NIP-07), through a signer app such as Amber or nsec.app over NIP-46 (scan a QR code or paste a bunker link), or by pasting an nsec. The login screen can also generate a new key for you.
Obelisk uses NIP-29: relay-managed groups. Channels, members, admins and removals are all standard NIP-29 events that the relay enforces. Any NIP-29-compatible relay works. You can host your own relay, run a private one for your community, or use a public one.
Direct messages are end-to-end encrypted. Obelisk sends NIP-17 gift-wrapped messages by default, so relays cannot see who you are talking to, and you can switch a conversation back to NIP-04 if the other person's client needs it. Post-quantum protection is on by default: whenever your signer and the other person both have post-quantum keys, the message is sealed with a post-quantum envelope as well (you can turn it off in settings). Group messages are signed but public on the relay: anyone the relay lets in can read them, just like a Discord channel. Run a private relay if you need a closed group.
Yes. Obelisk is a Next.js app with no database to manage and no backend service of its own: its small server part serves the pages, sets security headers, unfurls link previews and renders the public note and profile pages. Run it locally with `npm run dev`, ship it to any Node host with `npm run build` and `npm start`, or expose it through a tunnel. A static-export build for GitHub Pages, S3 or a static CDN is still on the roadmap.
You can generate one in the login screen. If you want a standalone signer, install a NIP-07 browser extension like Alby or nos2x, or on mobile use Amber (Android) or nsec.app. Keep your nsec safe: it's your account, no one can recover it for you.
Voice is here. Voice channels use WebRTC with signaling over Nostr events, so there is no Socket.io server and no Obelisk server in between. Small rooms connect browsers directly (a peer-to-peer mesh of up to four people); big-room voice channels route through a mediasoup SFU the channel admin picks, for many more people. Both do audio, camera and screen sharing.
Yes. Obelisk is a responsive web app that works in any modern mobile browser, and you can install it to your home screen as a PWA from the browser menu, no app store needed. On a phone, log in with a signer app over NIP-46 (Amber, nsec.app), generate a new key, or paste an nsec.
To open quickly and remember where you were, Obelisk keeps a copy of channels, messages and profiles, your read positions, your preferences, your login and the direct messages you have opened (both encrypted) and the app's own files in your browser. None of it is sent to an Obelisk server: there is no account server, and what you publish lives on relays (the one exception is Google Analytics, which the site loads only if you allow it, and which you can turn off at any time). Remove any of it in Settings > Data on this device, or all of it with Remove everything from this device. You can also log out, clear the site data for obelisk.ar in your browser's settings, or use a private window, which keeps nothing once you close it. Clearing your device does not delete what you published: delete a message from its menu to send a deletion request (NIP-09), which each relay may or may not honour. Step by step: obelisk.ar/help/local-data.

Post-quantum messages.

Encrypted messages sent today can be recorded now and read years from now, once a quantum computer breaks the key exchange Nostr relies on. It is the one part of the problem that can be fixed in advance.

Live in Obelisk. Direct messages are gift-wrapped by default, and carry a post-quantum seal whenever post-quantum protection is on (it is by default) and your signer and the other person both have post-quantum keys. The keys themselves live in the Nostr WoT extension and the @nostr-wot/pq library.

Built in collaboration with