Early access

Host Rhema on your own servers

Organisations can run Rhema on their own infrastructure. Your messages and files then stay on servers you control, and your people use the same apps as everyone else.

Self-hosting is in early access. We are working with a small number of organisations while we finish the tooling and documentation. Contact us at hello@siliconblast.com if you would like to take part.

What you run

Rhema ships as container images and a Docker Compose file. A server is made up of these parts:

Rhema web: The web app, served as static files.
Rhema API: The HTTP API and the realtime gateway that delivers messages to connected devices.
Rhema worker: Background jobs such as push notifications and clearing disappearing messages.
PostgreSQL: Accounts, chat membership, device keys and encrypted messages.
Redis: Presence, typing indicators and the job queue.
S3-compatible storage: Encrypted files and media. Amazon S3, MinIO or any compatible service will work.
LiveKit: The media server for voice and video calls.

Signing in

Today a self-hosted server signs people in with SiliconBlast Identity. Support for your own OpenID Connect provider is planned, so people will be able to use the accounts your organisation already has.

Encryption works the same way

Messages, files and calls are end-to-end encrypted on a self-hosted server exactly as they are on ours. Whoever runs the server can see the same metadata that we can on our servers, and no more. The security page lists what that is.

Updates

New versions arrive as new container images. You decide when to pull them and restart the services.

Getting started

Email hello@siliconblast.com with your organisation's name and roughly how many people will use Rhema.
We send you the Compose file, the configuration guide and access to the images.
You point a domain at your server, fill in the configuration and run docker compose up -d.