Self-hosting Soketi the easy way
Yulei ChenSoketi is a fast, open-source WebSocket server that's fully compatible with the Pusher protocol. If you're using Pusher or Ably for real-time features, you know how quickly per-message pricing adds up. With Soketi, you get unlimited messages on your own infrastructure.
Sliplane is a managed container platform that makes self-hosting painless. With one-click deployment, you can get Soketi up and running in minutes - no server setup, no reverse proxy config, no infrastructure to maintain.
Prerequisites
Before deploying, ensure you have a Sliplane account (free trial available).
Quick start
Sliplane provides one-click deployment with presets.
Deploy Soketi >- Click the deploy button above
- Select a project
- Select a server (If you just signed up you get a 48-hour free trial server)
- Click Deploy!
About the preset
The one-click deploy above uses Sliplane's Soketi preset. Here's what it includes:
- Debian-based image (
quay.io/soketi/soketi:1.6-16-debian) for stability - Pre-configured app ID, key, and secret so you can connect immediately
- No persistent storage needed since Soketi is stateless (channel state lives in memory)
- HTTPS scheme configured by default (Sliplane handles SSL termination)
Soketi is lightweight and runs well even on small servers. A single instance can handle thousands of concurrent WebSocket connections.
Next steps
Once Soketi is running on Sliplane, access it using the domain Sliplane provided (e.g. soketi-xxxx.sliplane.app).
Connecting your app
To connect from your frontend or backend, use the Pusher client SDK with your Soketi credentials. Here's a JavaScript example:
import Pusher from "pusher-js";
const pusher = new Pusher("YOUR_APP_KEY", {
wsHost: "soketi-xxxx.sliplane.app",
wsPort: 443,
wssPort: 443,
forceTLS: true,
disableStats: true,
enabledTransports: ["ws", "wss"],
cluster: "default",
});
Replace YOUR_APP_KEY with the SOKETI_DEFAULT_APP_KEY value from your service's environment variables in Sliplane, and soketi-xxxx.sliplane.app with your actual domain.
Environment variables
These are the key environment variables you can customize:
| Variable | Description |
|---|---|
SOKETI_DEFAULT_APP_ID | Your app's unique identifier |
SOKETI_DEFAULT_APP_KEY | Public key used by clients to connect |
SOKETI_DEFAULT_APP_SECRET | Secret key used for server-side API calls |
SOKETI_DEBUG | Set to 1 for verbose logging |
SOKETI_DEFAULT_APP_ENABLE_CLIENT_MESSAGES | Set to true to allow client-to-client messaging |
Scaling with Redis
By default, Soketi stores channel and presence data in memory. If you need horizontal scaling (multiple Soketi instances), you can add a Redis backend by setting these additional environment variables:
| Variable | Example |
|---|---|
SOKETI_ADAPTER_DRIVER | redis |
SOKETI_CACHE_DRIVER | redis |
SOKETI_QUEUE_DRIVER | redis |
SOKETI_DB_REDIS_HOST | your-redis-host |
SOKETI_DB_REDIS_PORT | 6379 |
Logging
Soketi logs to STDOUT by default, which works well with Sliplane's built-in log viewer. Set SOKETI_DEBUG=1 to get detailed output when troubleshooting connection issues. For general Docker log tips, check out our post on how to use Docker logs.
Cost comparison
You can also self-host Soketi with other cloud providers. Here is a pricing comparison for the most common ones:
| Provider | vCPU | RAM | Disk | Monthly Cost | Note |
|---|---|---|---|---|---|
| Sliplane | 2 | 2 GB | 40 GB | €9 (~$10.65) | Flat rate, 1 TB bandwidth, SSL included |
| Fly.io | 2 | 2 GB | 40 GB | ~$18 | Disk and bandwidth billed separately |
| Render | 1 | 2 GB | 40 GB | ~$35 | 100 GB bandwidth, Disk billed separately |
| Railway | 2 | 2 GB | 40 GB | ~$67 + $20 plan | Pro plan floor, usage-based, bandwidth billed separately |
Click here to see how these numbers were calculated.
(Assuming an always-on instance running 730 hrs/month)
- Sliplane: flat €9/month for the Base server. Unlimited services on the same server, 1 TB egress and SSL included.
- Fly.io:
shared-cpu-2x2 GB = $11.83/mo + 40 GB volume × $0.15/GB = $6 -> ~$17.83/mo. Egress billed separately ($0.02/GB in EU). - Render: closest match is Standard ($25, 1 vCPU / 2 GB) plus 40 GB disk × $0.25/GB = $10 -> ~$35/mo. Stepping up to Pro (2 vCPU / 4 GB) costs $85/mo + disk.
- Railway (Pro plan): CPU 2 × $0.00000772/s × 2,628,000 s = $40.57; RAM 2 × $0.00000386/s × 2,628,000 s = $20.29; volume 40 × $0.00000006/s × 2,628,000 s = $6.31 -> ~$67/mo compute, plus the $20/mo Pro plan floor and $0.05/GB egress.
Bandwidth costs can add up fast on usage-based providers. Use our bandwidth cost comparison tool to see what your egress would cost on each platform.
FAQ
When should I use Soketi instead of Pusher?
Soketi makes sense when you have high message volumes or need predictable pricing. Pusher charges per message and per connection, which can get expensive fast for apps with many active users. With Soketi on Sliplane, you pay a flat €9/month regardless of how many messages you send.
Can I use my existing Pusher client code with Soketi?
Yes. Soketi implements the full Pusher protocol, so you can switch by changing the host configuration in your Pusher client SDK. No code changes needed beyond updating the connection parameters (host, key, secret).
How do I update Soketi?
Change the image tag in your service settings on Sliplane and redeploy. Check Quay.io for the latest stable version. Stick with the debian variant for the best compatibility.
Does Soketi support presence channels and webhooks?
Yes. Soketi supports all Pusher channel types: public, private, presence, and encrypted channels. It also supports webhooks for channel events. Configure webhooks by setting SOKETI_DEFAULT_APP_WEBHOOKS with a JSON array of webhook URLs.
How many concurrent connections can Soketi handle?
On a 2 vCPU / 2 GB server, Soketi can comfortably handle 5,000+ concurrent WebSocket connections. The actual limit depends on your message throughput and payload sizes. For higher loads, you can scale vertically (bigger server) or horizontally (multiple instances with Redis).
