Self-host Soketi with Levelrail
A simple, fast, Pusher-protocol-compatible WebSockets server for real-time app features.
- Authorsoketi
- LicenceAGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Soketi
-
Pull the images
One image is pulled on your server.
Show images
quay.io/soketi/soketi:1.6-16-debian
-
Create the app
One service starts in a single Compose app, on port 6001.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Soketi requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 6001
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 6001 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Soketi. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Soketi docs page.
Deploy Soketi your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Soketi from the CLI
levelrail-cli templates deploy soketi --name my-soketi Deploy Soketi with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/soketi/deploy Soketi configuration
Soketi services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| soketi | quay.io/soketi/soketi:1.6-16-debian | 6001 | none |
Soketi environment variables
| Variable | Service | Value |
|---|---|---|
| SOKETI_DEFAULT_APP_ID | soketi | Generated at deploy |
| SOKETI_DEFAULT_APP_KEY | soketi | Generated at deploy |
| SOKETI_DEFAULT_APP_SECRET | soketi | Generated at deploy |
| SOKETI_PUSHER_SCHEME | soketi | Preset by the template |
Ports and volumes
- Ports
- 6001
- Volumes
- none
Soketi FAQ
How much memory does Soketi need?
The catalog lists about 256 MiB of memory for Soketi.
Does Soketi run on arm64?
For Soketi, an arm64 image is published; amd64 is image published.
What licence is Soketi under?
Soketi is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Soketi need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Soketi use?
Soketi listens on port 6001 inside the stack.
Can I deploy Soketi on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id soketi for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image quay.io/soketi/soketi:1.6-16-debian is what you deploy there.