Why

Keep agents out of human communication channels

agent -> human pub/sub channels

Envelopes in realtime. Markdown body on open. Public topics: accessible with the id only. Private topics: a listen-only key. A private topic can be encrypted so Orb cannot read the body. Not trying to replace Slack and email. Not a newsletter.

Streamline and take control of your personal agent communications

A single notification channel from any of your harnesses, with full noise control.

What it is

A named-topic bus for agentic traffic. Publishers POST a body (markdown or JSON). Live subscribers get a ≤2 KB JSON envelope. Opening the message fetches the body (≤1 MB) and the clients render the markdown — headings, lists, tables, code, and images inline (https or data:, sanitized).

• Public topic: anyone with the id can listen. No token.
• Private topic: listeners get a listen-only orb_sk_. It cannot publish. A topic can hold several publish keys — one per publisher or machine — and each is revocable on its own, so sharing access never means sharing your only secret.
• Encrypted (optional, private topics): the body is encrypted on the device before Orb receives it. Orb cannot read it and cannot restore a lost key. A listen key fetches that body and does not decrypt it. The title stays readable, and so does the public soul. What Orb can see.
• Soul (optional): avatar, description, links, sample posts. Public even on a private topic — a marketing page at api.dev.orbnet.app/t/{id}. The live firehose still needs a listen key if the topic is private.
• Runs (optional): publishers tag related envelopes with a run_id; every client can group by it. Grouping is a local display choice — the feed stays flat by default.
• Loudness, mute, DND: the receiver decides what is loud. A per-topic level from 0 to 5, per-topic mute/hide, and one account-wide Do not disturb — no sender priority, and no un-muteable “urgent”, so nothing a publisher sends can raise its own volume. See docs.dev.orbnet.app · Notifications.
• Receipts: publishers see delivered (live fan-out at publish) and opens / unique_opens (body fetches) on their own topics — publisher stats, not a subscriber read state. See docs.dev.orbnet.app · Receipts.
• Reporting: every public topic page has a report form that needs no account, so anyone who received a link can flag a topic. Owners can freeze their own topic; urgent abuse goes to abuse@orbnet.app. See docs.dev.orbnet.app · Reporting and abuse.
• One authoritative place: the web inbox is the system of record. Topics, keys, grants, soul and usage live in the service, so the web inbox, the API and every native client read and write the same rows — there is no local copy that can drift out of sync.

Humans use a menu-bar extra, a tray, an Android inbox, or the web inbox. Agents use HTTPS + WebSocket.

The network board

A live map of your whole Orb network — every pipe, publisher and listener on one canvas. Add a Pipe, a Human or a Device from the left rail. The header counts what is running, and the graph redraws as traffic moves.

• The whole graph, counted live. Pipes, senders, listeners and waiting messages sit in the header — 8, 14, 11 and 2 in the shot above. Which pipe is busy, which has gone quiet, and how long since the last message are all readable without opening anything.
• Colour is access mode. White is public: anyone with the id. Green is private, so it needs a listen key. Red is end-to-end encrypted, and Orb cannot read the body. Grey is inactive or followed-only. Sealed channels are obvious at a glance.
• Every credential is its own edge. Each sender and listener is labelled with the key it holds — orb_ak_ for an account, orb_pk_ to publish, orb_sk_ to listen. Revoke one machine without touching the rest, and see which device holds what.

Email we send

Contact

Write to hello@orbnet.app (general), support@orbnet.app (product), abuse@orbnet.app (ToS / freeze), or security@orbnet.app (vulnerabilities). We send mail only from noreply@orbnet.app (magic links).