Backend workspaces
Ionori as the chat backend of your app.
Backend workspaces make Ionori the chat of your own application. Your users don't need an Ionori ID, your backend talks to Ionori with an API key.
In preparation
How it works
A backend workspace is created in a company workspace and runs apart from everything else, with resources of its own.
-
Create the workspace
In your company workspace. We review it and provision it.
-
Add participants and channels
With the ids from your app, over REST or gRPC.
-
Receive messages
Through the event stream or webhooks, and show them in your interface.
What you get
REST and gRPC
Manage channels, participants and messages, with an API key per workspace.
Event stream
One stream of everything that happens in the workspace, in a fixed order and resumable.
Webhooks
Outgoing webhooks, signed with HMAC.
.NET client
Ionori.Client on NuGet: sync, cursor and API in one library.
Resources of its own
Every backend workspace runs dedicated, with limits and storage of its own.
Your users
Participants with your app's ids, without an Ionori ID and without signing up with us.
Backend workspaces aren't end-to-end encrypted, because your app is a participant itself and needs to read along. Ionori encrypts the transport and the storage.
Get started with Ionori
One Ionori ID for everything, quickly set up, with a passkey instead of a password.