# OpenPulse > Identity, realtime, payments, mail and phone for people and agents on one @handle. Agents sign in with their own keys. One SDK, one Console. Request access. OpenPulse is the developer platform for identity, realtime, payments, mail, and phone. People and agents share one @handle across every surface, and the platform is integrated with one SDK and run from one Console. Operator: AUVY GmbH, Am Haag 8, 82166 Gräfelfing, Germany. Register Amtsgericht München HRB 311039. Contact contact@auvy.ai. Security security@openpulse.org. ## What it is OpenPulse is a developer platform for identity, realtime, payments, mail, rooms, and phone. Every surface uses the same @handle, and people and agents are the same kind of identity. One SDK connects an app, and one Console and Management API run it. Messages, live documents, agent runs, and files share one session per device through one edge address (edge.openpulse.org, in Helsinki today). Pay keeps one ledger with instant sends between handles and bank and USDC routes through Circle; every move needs a fresh second factor. Mail, rooms, and phone leave at the outside network each one needs. - One identity: people and agents in the same directory, keyed by DID. - One connection: messages, live docs, agent runs, and files on one session. - One ledger: instant sends between @handles, bank and USDC in and out, and a second factor on every move. - Mail from your domain: send, receive, and broadcast, with templates and webhooks. - One edge address: edge.openpulse.org relays sealed traffic and holds it for anyone offline. - Private in the middle: the relay can move your users’ words and cannot read them. - Current status: access is by request until launch, and Phone is planned. Claiming a handle is open to everyone. ## Who it is for - Developers who need sign-in, realtime, messaging, payments, and email without gluing five vendors together. - Teams giving AI agents a real identity: their own keys, handle, activity log, and a switch to suspend them. - Anyone who wants a personal @handle; claiming one is open. ## Identity for people and agents 01. Key. Person: A passkey created on the device. The private key never leaves it. Agent: An Ed25519 key generated where the agent runs. Console issues the .env once and keeps only the public key. 02. Vouch. Person: One verified email secures the name. We do not keep the inbox. Agent: The 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. Person: Passkey, email link, or a code on another device. Agent: Signs a fresh challenge for a realm-scoped token. Replays are rejected. 05. Control. Person: Moving money requires a fresh second factor every time. Agent: Suspend, rotate keys, or revoke from the Console. Every sign-in is logged. ## How to claim a name 01. Pick: Choose @you. No suffix, worldwide. 02. Verify: One email so nobody else can take the name. We do not keep your inbox. 03. Unlock: Set a passkey on this device. We cannot reset it for you. Claiming a name does not open Lab, Console, or Pay. ## What is open today - Claim @you: open. - Identity (passkey on this device): open after claim. - SDK, Console, Lab, Pay, agent identities, mail, rooms: by request until launch. Use https://openpulse.org/request-access. - Phone: planned, not built yet. ## Privacy We can move it. We cannot read it. Message keys remain on client devices in sealed production modes. Relays see routing metadata, not plaintext. Demo and staging may use plaintext for debugging; those modes are not production privacy claims. ## Mail, pay, rooms, phone - Identity: Keys are made on this device. One verified email keeps the name. A passkey, an email link, or a code on another device opens the same account. Status: Claim is open. Your name and how you unlock it live here. - Mail: Send, receive, and broadcast from your own domain, for people and agents. Templates, audiences, webhooks, test addresses, and SMTP. Status: Production mail routes through our current provider until our own mail host is live. - Pay: Send prepaid money to a named person. Every transfer asks for a fresh second factor. Status: Test ledger until launch. Outside funding is gated. - Rooms: Video rooms with invites and recording. You need an account to join. Status: Video runs in one region today, as a separate service next to private chat. - Phone: A number people can text or call, owned by the same @handle. People and agents are reachable from any phone. Status: Planned. Design is complete and the Console slot is reserved; the number service is not yet built. ## Questions ### What is OpenPulse? 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? No. Private messages stay between the people and agents in them. The relay moves the packets. It cannot read the words. ### How do I get access? 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. ### What does it cost? 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. ## Do not over-claim - Signal and MLS: Official libsignal and OpenMLS are wired and smoke-tested behind build flags. They are not the production default yet, so we do not say Signal-grade. - Sealed streams: A stream is sealed when its room has a seal key, and the relay fails closed rather than downgrade. Lab soaks deliberately run a plaintext mode, and that mode is not operator-blind. It is never scored as if it were. - Regions: The wire is one node in Helsinki today: edge.openpulse.org goes straight to the Helsinki origin of record. Clients set one hostname; the HUD is RUM of that connection. There is no multi-region SLO. - Scale: Ten thousand concurrent stream subscribers on one node, measured in the eval harness. That is a subscriber count, not ten thousand full product tenants. - Availability: The SDK is unpublished and access is by request until launch. Claiming a handle is open to everyone; the platform is not. ## Start 1. Request access for your team: https://openpulse.org/request-access 2. Try the identity layer by claiming a handle: https://openpulse.org/#claim 3. Privacy model: https://openpulse.org/security