Skip to content

On…

OpenPulse

The OpenPulse app

One app for sign-in, messages and the private network.

The OpenPulse app runs on desktop and phone. It signs you in, keeps your keys and second factor on the device, carries your sealed messages and joins your organization’s private network.

Desktop and phone · with your organization’s access

The first day takes four steps.

A new colleague at Sorvenna Logistik GmbH opens the app once. There is no password to choose and nothing to configure.

  1. 01

    Sign in with a passkey

    The passkey is created on the device and confirmed with a fingerprint, a face or the device PIN. With single sign-on, the person starts at your provider.

  2. 02

    The device is registered

    The app makes a key for this device, in its secure hardware where the device has it. The device appears in your organization’s list with its owner.

  3. 03

    Messages arrive

    From here on, direct and group messages for this person arrive sealed and are opened on this device.

  4. 04

    The private network connects

    One switch brings the device onto the network. It reaches what the policy allows and nothing else.

Your keys are made on the device and stay there.

The app creates a person’s keys on the device and keeps them there. OpenPulse receives the public halves, so nobody who runs the servers can open a message or pose as the device.

Stays on the device

  • Message keysThe keys that open your direct messages and groups are made on the device.
  • The device keyIt proves this device to your organization and sits in secure hardware where the device has it.
  • The network keyThe private half of the key that joins the private network.
  • Authenticator secretsThe seeds your time-based codes are computed from.

Leaves the device

  • Public keysSo others can seal a message to you and your organization can recognize the device.
  • Sealed messagesThe relay sees who a message is for, its size and when it arrived. It does not see the words.
  • Traffic for your private resourcesEncrypted with WireGuard between the device and the server. Everything else goes its normal way.

The app is your second factor.

When a sign-in on another screen needs a second step, the app answers it.

Match a number
The other screen shows a number and you pick it in the app. A tap by mistake approves nothing.
Authenticator codes
Time-based codes for OpenPulse and for other services that use them.
Passkeys
The app holds passkeys and offers them where a sign-in asks for one.

Messages and the network live in the same place.

After day one the app is where a person reads, writes and reaches the organization’s servers.

Sealed messages
Direct messages and groups arrive sealed and are opened on the device. The app lists the devices that carry your messages, and you can take one off.
The private network
One switch joins the network and shows what the policy lets this device reach. Switch it off or sign out, and the device leaves.
Requests and approvals
Ask for access to a sensitive server with a reason and a duration, or confirm a colleague’s request with your passkey.

Your organization decides which devices and which second factor.

The person who rolls the app out sets the rules once in the Console, and the app follows them on every device.

Which devices
Require a registered device for sign-in. Every device is listed with its owner, its system and its last sign-in.
Which second factor
Set the level each group needs, with a grace period for people who still have to enroll.
Offboarding
Remove a person or a single device. Its sign-in ends, its messages stop arriving and it leaves the private network.

What people ask on the first day.

Can my employer read my messages?
No. A sealed message is opened only on the devices of the people in the conversation. An admin sees that your device exists, its system and when it last signed in.
Does all my traffic go through the private network?
No. The tunnel carries traffic for your organization’s private resources. Everything else on the device goes its normal way.
What happens when a device is lost?
You take it off from your account page, or an admin removes it in the Console. Its sign-in ends, its messages stop arriving and it leaves the private network. Nothing reaches into the lost device to erase it.

Where it stands today.

  • The app comes with your organization’s access. There is no public store listing.
  • The private network part of the app builds on NetBird’s open source client library and WireGuard.
  • Our use of libsignal, OpenMLS and WireGuard has not been independently audited.

How security and privacy work

Roll the app out to your first group.

Tell us how many people and which devices. We open your organization and set up the first devices with you.