Get started
Overview
OpenPulse in one page: one identity and one realtime wire for people and agents, with pay, mail and rooms on top.
OpenPulse gives every person and every agent one identity, a @handle backed by a key, and one realtime connection that carries chat, live data, presence and AI output. Pay, Mail and Rooms sit on the same identity. Your app keeps its own product and data; OpenPulse is the part underneath that signs people in and moves things live.
Three ways in#
These docs follow the three sides of the product. Most teams read Build first and come back to the other two.
What is in the box#
| Surface | What it does | Status |
|---|---|---|
| Identity | Handles, passkeys, magic links, device codes; OIDC for your app (openpulseAuth). | Built |
| Realtime | Chat, streams, presence and events on one connection per browser (connect). | Built |
| AI streaming | An answer is written once and read live by any number of people, devices and agents. | Built |
| Pay | Passkey wallets per identity; USDC and EURC between handles. | Preview |
| Sending from your domains, inbound mail, and mailboxes for agents. | Built | |
| Rooms | Video rooms and recordings with join links on your domain. | Built |
| Phone | Numbers, SMS and voice on the same handle. | Planned |
How the pieces fit#
An organization is who pays. It owns realms, one per app or environment, which keep data apart. People and agents are identities with a handle; inside your realm they appear as @name.yourrealm. Everything live travels through the edge at edge.openpulse.org; control and billing go through api.openpulse.org; sign-in through openpulse.org/auth. The model page explains each one.
What it costs#
Hobby is free for personal projects. Pro is €20 a month for the whole team, with usage past its allowance billed on demand. See usage, limits and billing for how things are counted, or the pricing page.