A developer platform for identity, realtime, payments, mail, rooms, and phone. Every surface shares one @handle, and people and agents are the same kind of identity. One SDK integrates it; one Console and Management API run it.

How does Pay move money?

One ledger per realm with USD and EUR balances. Transfers between @handles are instant and free. Bank and USDC transfers run through Circle. Every movement requires a fresh second factor, for people and agents, and arrives on the session as an event. The ledger runs on testnet until launch.

Can I send email with OpenPulse?

Yes, from your own domain: send, receive, and broadcast for people and agents, with templates, audiences, webhooks, and SMTP. Until our own mail host is live, production mail routes through our current provider.

Can an agent have its own identity?

Yes. An agent gets a DID, a @handle in your realm, and its own keys. It authenticates with a signature, not a shared API key, sits in the same directory as your users, and can be suspended or rotated from the Console.

Do I still need a separate auth provider?

No. OpenPulse covers passkeys, email links, device codes for command-line tools, step-up authentication, and sessions. Your backend verifies tokens against published keys and issues seats for the wire.

Can OpenPulse read my users’ messages?

Not in a sealed room: the relay moves the packets and cannot read the words. Sealing is a setting today and we are making it the default. A room you do not seal is readable by the relay, and the SDK says which one you have.

Until launch, the SDK, Console, Lab, and Pay open by request. Tell us your use case; we review every request and reply by email. Claiming a personal @handle is open to everyone.

Hobby is free for personal and non-commercial projects: 100 million realtime messages, 50,000 users, plus email and rooms each month, no card required. A streamed AI answer counts as one message. Pro is €20 a month per team with larger allowances, then €1 per million messages and €6 per 1,000 users, with email and rooms billed by usage. Details at openpulse.org/pricing.

Is claiming a handle free?

Yes. Anyone can claim @you and see the identity layer their users would get. A handle does not grant Console or Pay access.

OP-01General arrangement

Developer platformOne identity · one edge

One wire forpeople and agents.

Identity, realtime, payments, mail, and phone on a single @handle for people and agents, integrated with one SDK and run from one Console.

Request access See the platform

Agents: Are users
Middle: Blind to sealed
Edge: … Helsinki
Mars: …

01Keys Created on this device. They never leave it.
02Sealed envelope Carried by the middle. Opened only at the ends.
03Edge link One address: edge.openpulse.org. Geo-DNS routes to the nearest edge.
04Relay Moves packets. Holds them while you are offline.

Plate I. Earth’s magnetosphere: field lines, bow shock, and tail. A relay orbits inside the field; the pulse marks the sealed packet.

OP-02System stack

Every surface runs on one identity.

Most teams stitch together an auth provider, a realtime service, a payments API, and an email sender, then keep four user lists in sync. On OpenPulse, Realtime, Pay, Mail, Rooms, and Phone share one @handle and one edge.

Surfaces

01Realtimeconnect()Chat, presence, live documents, and agent streams share one session per device. Messages are sealed on the device and held for anyone offline.Through the edge: Sealed relay on the edge
02Paypulse.pay.send()USD and EUR balances, instant transfers between @handles, bank payouts, and USDC. Every transfer requires a fresh second factor.Through the edge: Settle edge, then one ledger
03Mail@openpulse/mailSend, receive, and broadcast from your own domain. Templates, webhooks, and SMTP included.Leaves at: Public email
04Rooms@openpulse/roomsVideo rooms with invites and recording. Only signed-in identities can join.Leaves at: Video servers
05PlannedPhone@openpulse/phoneA number people can text or call, owned by the same @handle.Leaves at: Phone network

Shared by every surface

IdentityOpen

openpulse.org/auth

One @handle and key pair for every person and agent. People sign in with a passkey, email link, or device code. Agents sign with their own key. Sensitive actions require a second factor.

Under realtime and pay

Edge networkLive · Helsinki

edge.openpulse.org

One address for every client. Geo-DNS routes each connection to the nearest edge, which relays sealed traffic and holds it for offline recipients. The edge runs in Helsinki today.

Sealed, through our edgeLeaves at an outside network

Access is by request until launch. Phone is on the roadmap.

Read the docs →

OP-03Identity assembly

Agents are users too.

Every identity is a key pair with a name: a DID, a @handle, and the devices that hold the key. People unlock with a passkey. Agents sign with their own key. Both live in one directory with one audit log and one set of controls, so no agent needs a shared API key.

Assembly sequence · 5 steps · two kinds

Step Person Agent

01
Key
PersonA passkey created on the device. The private key never leaves it.
AgentAn Ed25519 key generated where the agent runs. Console issues the .env once and keeps only the public key.
02
Vouch
PersonOne verified email secures the name. We do not keep the inbox.
AgentThe realm owner approves with a second factor. A stolen session cannot mint an agent.
03
Name
Person@you, unique worldwide and reachable by people and agents.
Agent@support.acme within your realm. Delete the agent and the name is released.
04
Sign in
PersonPasskey, email link, or a code on another device.
AgentSigns a fresh challenge for a realm-scoped token. Replays are rejected.
05
Control
PersonMoving money requires a fresh second factor every time.
AgentSuspend, rotate keys, or revoke from the Console. Every sign-in is logged.

The same identity joins sessions, payments, mail, and rooms, so an agent needs no second account.

Try it: claim a handle Agents in the docs

Try itForm OP-25 · the identity layer, live

Claim @you before someone else does.

This is the identity layer, running live. Pick a name and verify one email, and it is yours worldwide with no suffix and no password. It unlocks from this device.

OP-04Wire anatomy

Every live thing on one connection.

Chat, live documents, agent output, notifications, and files share one session per device. WebTransport comes first, with WebSocket and polling fallbacks for restrictive networks.

Chat, a page, and an agent at the same time. If you drop, you pick up here.

Each keeps its own pace on one private path.

Each lane keeps its own priority. Keystrokes never queue behind a file, and agent output never queues behind either.

Stn 01 · Your app

Browsers and mobile apps open one session with connect() and get every lane their seat allows.

Stn 02 · Your agents

The same session API on the server: subscribe, publish, and wake on named triggers.

Stn 03 · Your backend

Issues seats to your users and keeps your data. It never proxies a socket.

Plate II. An orrery with one transfer orbit from Earth to Mars. The envelope that leaves Earth is the envelope that arrives.

OP-05Seal boundary

Seal it, and we can move it but cannot read it.

A sealed room is encrypted on the device and readable only by the people and agents holding its key. The relay routes by room and size, and whoever runs the servers, including us, cannot read sealed words. Sealing is a setting today; we are making it the default, and until then the SDK tells you which kind of room you have.

Running the servers yourself changes who owns them. They still cannot read sealed messages.

Two tracks, drawn together: private to a person, readable as email.

How privacy works →

OP-06Operating console

One Console runs it.

Realms, people, agents, keys, traffic, billing, mail, and payments in one place. Every screen runs on the Management API, so anything the Console does, a script can do.

TrafficRequests, messages, and live rooms per realm, sampled every minute.
IdentitiesPeople and agents in one list, with the same detail view and controls.
KeysServer keys for your backend. Creating an agent requires a second factor.
Management APIEvery screen is an API call you can script with your own token.

Illustration with sample data. The Console signs in with your own identity and calls the same Management API as your scripts.

1: connection per deviceMessages, live docs, agent runs, and files on one session.
1: directory per realmPeople and agents in one list, under one set of controls.
0: passwordsPasskeys for people. Signed challenges for agents.

General notes Questions

What you get, and what is live today.

: A developer platform for identity, realtime, payments, mail, rooms, and phone. Every surface shares one @handle, and people and agents are the same kind of identity. One SDK integrates it; one Console and Management API run it.
: One ledger per realm with USD and EUR balances. Transfers between @handles are instant and free. Bank and USDC transfers run through Circle. Every movement requires a fresh second factor, for people and agents, and arrives on the session as an event. The ledger runs on testnet until launch.
: Yes, from your own domain: send, receive, and broadcast for people and agents, with templates, audiences, webhooks, and SMTP. Until our own mail host is live, production mail routes through our current provider.
: Yes. An agent gets a DID, a @handle in your realm, and its own keys. It authenticates with a signature, not a shared API key, sits in the same directory as your users, and can be suspended or rotated from the Console.
: No. OpenPulse covers passkeys, email links, device codes for command-line tools, step-up authentication, and sessions. Your backend verifies tokens against published keys and issues seats for the wire.
: Not in a sealed room: the relay moves the packets and cannot read the words. Sealing is a setting today and we are making it the default. A room you do not seal is readable by the relay, and the SDK says which one you have.
: Until launch, the SDK, Console, Lab, and Pay open by request. Tell us your use case; we review every request and reply by email. Claiming a personal @handle is open to everyone.
: Hobby is free for personal and non-commercial projects: 100 million realtime messages, 50,000 users, plus email and rooms each month, no card required. A streamed AI answer counts as one message. Pro is €20 a month per team with larger allowances, then €1 per million messages and €6 per 1,000 users, with email and rooms billed by usage. Details at openpulse.org/pricing.
: Yes. Anyone can claim @you and see the identity layer their users would get. A handle does not grant Console or Pay access.

Access points

Request access

Console, SDK, Lab, and Pay for your team. We review every request.

Open Console

Already approved? Sign in with your passkey.

Claim @you

Try the identity layer yourself. Claiming is open to everyone.

Enterprise requests

One wire forpeople and agents.

Every surface runs on one identity.

Agents are users too.

Key

Vouch

Name

Sign in

Control

Claim @you before someone else does.

Every live thing on one connection.

Seal it, and we can move it but cannot read it.

One Console runs it.

What you get, and what is live today.

01.What is OpenPulse?+

02.How does Pay move money?+

03.Can I send email with OpenPulse?+

04.Can an agent have its own identity?+

05.Do I still need a separate auth provider?+

06.Can OpenPulse read my users’ messages?+

07.How do I get access?+

08.What does it cost?+

09.Is claiming a handle free?+