Skip to content

On…

OpenPulse

Enterprise

One system your security team can run.

Sign-in, communication and the private network sit under one directory and one set of policies, with a record you can verify. OpenPulse connects to the identity provider you already have, is hosted in the EU and is bought by agreement.

By agreement · hosted in Helsinki

Your identity provider stays the source of truth.

People sign in through the provider you already run, and your directory creates and removes them. There is no second list of people to maintain.

Single sign-on
OpenID Connect or SAML 2.0, with setup steps for Okta, Entra ID and Google Workspace.
Provisioning
SCIM 2.0 for people and groups. Deactivating someone signs them out at once.
Verified domains
Your email domains belong to your organization and nobody else’s.

One set of policies, and a second person for sensitive actions.

The groups from your directory carry every rule, and all of it is set in one Console.

Sign-in policies
Allowed methods, required passkeys, registered devices and a second factor level by group.
Access policy
One document decides who reaches which server, and sensitive access is granted for a set time.
Two-person approvals
A sensitive admin action waits until a second admin confirms with their own passkey.
Sessions
See where your members are signed in. An admin ends one session or signs a person out everywhere.

A realm for each app and environment.

A realm keeps its people, agents, rooms and keys apart from every other realm in your organization.

Realm keys
Your servers hold a key for one realm, made in the Console.
Push keys per realm
Apple and Google keys saved on a realm serve that realm alone and are never shown again.

What you can verify yourself.

A security review should not rest on our word. Your own people can check these four things.

  • The audit chainRun the check from the Console. It walks every entry of your organization’s log and returns the newest hash, which you write down. The record for Private access is chained the same way.How it holds
  • The sourceThe SDK, the protocol, the apps and Private access are licensed under AGPL-3.0. The repositories are not public yet, so ask for them with your request and read the parts you depend on.Ask for it
  • The subprocessorsEvery provider that processes personal data for OpenPulse, with its purpose, what it sees and its region.The list
  • The security contactsecurity@openpulse.org takes vulnerability reports in private. The security page says what a report should contain.Contact

Hosted in Helsinki, operated by AUVY GmbH.

Sign-in, the directory, the relay, video rooms and the Console run on servers at Hetzner in Helsinki. OpenPulse is operated by AUVY GmbH in Gräfelfing, Germany.

Outside providers
Mail and Pay use providers outside our servers. Each one is listed on the security page with what it sees and its region.
Your own relay
An organization can run a relay itself, restrict traffic with realm keys and require sealed rooms.

No external audit and no certification yet.

OpenPulse has not been independently audited and holds no security certification today.

An evaluation runs in four steps, then a written agreement.

You try OpenPulse with your own provider and a first group of people before anything is signed. Commercial use then runs under a written agreement with AUVY GmbH that sets the scope and the prices. There is no price list and no online checkout.

  1. 01

    Request access

    Tell us your size, your identity provider and what you need to protect. A person at AUVY GmbH replies by email.

  2. 02

    A realm of your own

    We open your organization and a realm, the space that keeps your people, rooms and policies apart from everyone else’s.

  3. 03

    Your provider, connected

    You verify your email domain, connect single sign-on over OpenID Connect or SAML, and switch on SCIM.

  4. 04

    A first group of people

    They sign in through your provider, get the app and work under your policies. You run the audit chain check yourself.

An evaluation runs on the free monthly amounts listed in the developer docs.

Where it stands today.

  • Single sign-on supports one provider per organization. Signed requests, encrypted assertions and single logout are not supported yet.
  • Video rooms and mail are not encrypted end to end.
  • OpenPulse runs on one node in Helsinki today, and we publish no uptime commitment.
  • Private access opens by request, one organization at a time.

How security and privacy work

Talk to us about your organization.

Tell us your size, your provider and what you need to protect. A person at AUVY GmbH replies by email.