What You Get With Multiple Gateways
One gateway drops? Consumers are rerouted to another in seconds. No action required from you.
Updates roll out one gateway at a time. Your services never go offline for an update.
Place gateways in different regions. Consumers connect to the nearest one automatically.
No external load balancer. No shared database. No pairing step. Start the container — done.
Live Cluster
Event log
Simulations are visual only — they do not affect the live cluster.
Enable HA in Three Steps
Your first gateway is already HA-ready
Every Sertone gateway supports clustering out of the box. Nothing to configure on the first one.
Start a second gateway anywhere
Deploy the same container on a second machine — different server, different cloud provider, different country. Give it its own data volume.
docker run -d --name sertone \
-p 80:80 -p 3002:3002 \
-v sertone-data:/app/data \
--restart unless-stopped \
sertonenet/gateway:latestDone
The two gateways find each other automatically. Open your dashboard and you will see the second gateway appear in the Cluster section. Add a third for production-grade resilience — take one offline for maintenance while the other two keep serving.