Skip to content

On…

OpenPulse

Developer platform

One SDK for identity, sealed rooms and agent output.

People and agents sign in as the same kind of identity. Sealed rooms and streamed agent output share one connection, with push, mail and video rooms beside it, and one Console runs all of it.

SDK by request · docs open

Connect, subscribe, publish.

This is a room, written on your server. The SDK is one package, and a realm key from the Console is the only credential your server holds.

server.ts
import { connect } from '@openpulse/sdk' const pulse = await connect()const room = pulse.chat('general') room.subscribe((event) => show(event))await room.publish('app.chat@v1', {text: 'On my way',})
connect()
Reads your realm key from the environment and trades it for a 15-minute token. The key itself never reaches a relay.
subscribe and publish
Every lane speaks the same two verbs. Subscribing joins a room, and the first publish opens it.
Sealed or not sent
A room goes out only when the SDK can seal it. Without a key the write is refused as ROOM_NOT_SEALED and nothing leaves your process.

A group gives the room its key.

Members derive the key on their own devices. Take someone out, and the room moves to a key they never get.

const team = await pulse.createGroup({members: ['@bob', '@carol'],})const room = team.room('general') await room.publish('app.chat@v1', {text: 'On my way',})

An agent writes its answer once.

Every reader gets it as it streams and catches up after a break. Here, model is your own model client.

const run = await pulse.run()const stream = model.stream(prompt) for await (const text of stream) {await run.write({kind: 'text_delta',text,})}await run.end()

People and agents are the same kind of identity.

A person signs in with a passkey through OpenID Connect and PKCE. An agent signs a fresh challenge with its own Ed25519 key. Both get a DID and a @handle, and both join the same rooms.

No user list to sync
The identity that signs in is the identity in the room.
No shared API key
An agent holds its own key. You suspend the agent or rotate the key in the Console.
Tenants and seats
Serve many customers from one realm with short-lived seats your backend issues.
Your customers’ own sign-in
An organization connects single sign-on over SAML 2.0 or OpenID Connect and provisions people over SCIM 2.0. Its admins list and end sessions.

A realm for each app and environment.

A realm keeps its people, agents, rooms and keys apart. Your server holds that realm’s key, and the Apple and Google keys for Push are saved on the realm they serve.

One connection per device carries every lane.

Chat, presence, live documents and agent output share one session. WebTransport comes first, with WebSocket and polling as fallbacks for restrictive networks.

Writes survive a lost link
Chat messages and agent output wait while the link is down and go out in order when it is back, each exactly once.
Sealed unless you say otherwise
The SDK seals rooms by default, and an app has to opt out on purpose. A room it opts out of is readable by the relay.
Lanes do not block each other
Keystrokes never queue behind a file, and agent output never queues behind either.

The docs are open to read.

They cover sign-in, realtime, AI streaming, tenants, agents, organizations and each product. Every page is also Markdown for coding agents.

  • QuickstartFrom a realm key to a live room and a streamed answer, with the browser side and seats.Start
  • SDK referenceEvery entry point of the package and what it is for.Reference
  • HTTP APIThe relay, management and sign-in endpoints, for languages without an SDK.Endpoints
  • PushApps, devices, the three modes and the Apple and Google keys of a realm.Push
  • OrganizationsSingle sign-on, SCIM, sign-in policies, the audit log and Private access.Set up
  • Docs for agentsllms.txt, a Markdown copy of every page and stable URLs for a coding agent to read.For agents

Where it stands today.

  • The SDK installs from a private registry once access is granted.
  • Mail is in preview, Pay runs on the Base Sepolia test network where tokens have no value, and Phone is planned.
  • Our use of libsignal and OpenMLS has not been independently audited.
  • Free amounts for evaluation are listed in the docs. Paid use runs under a written agreement.

How security and privacy work

Build your product on OpenPulse.

Tell us what you are building. We review every request and reply by email with install instructions.