AUVY
DEBook a walkthrough

Protocol started by AUVY building

OpenPulse

One identity for people and agents, with realtime, payments, mail, video rooms and phone on the same @handle, built in with one SDK and run from one Console.

In its own words
“One wire for people and agents.”

openpulse.org

openpulse.org: one wire for people and agents.
openpulse.org: one wire for people and agents.

Why it exists

Work between companies still runs over tools that each own a piece: the mail, the chat, the files, the invoice. A change that crosses a company boundary gets lost in between.

OpenPulse gives every person and every agent one @handle and keys that stay on their device. Chat, live documents, agent output and files travel on one session, sealed on the device, so whoever runs the relay, including us, cannot read them.

Teams that today stitch together an auth provider, a realtime service, a payments API and an email sender get one directory, one audit log and one Console instead. AUVY's own live collaboration runs on it.

For
Developers building products where people and agents work together, and companies that work across company boundaries.
Where it stands
Access by request at openpulse.org. The edge runs in Helsinki, and payments run on testnet until launch.

What runs today

  • Sign-in with passkey, email link or device code, for people and agents
  • Realtime, mail and video rooms on one @handle
  • Messages sealed on the device, so the relay cannot read them
  • A Console and Management API for realms, people, agents and keys

The company

Stage
Access by request
Legal
Inside AUVY GmbH until it becomes its own company
Run by
AUVY, until it has its own team
Infrastructure
Its own fenced part of AUVY's servers in Helsinki, until it moves to its own EU server
Runs on
Live collaboration · Sign-in and secrets
Site
openpulse.org ↗

What happens next

  1. 1

    Open access beyond the first integrators

  2. 2

    Take payments off testnet

  3. 3

    Phone numbers on the same @handle

More built by AUVY