Welcome to Tergum
Tergum provides automated high-availability failover for WordPress websites. When your primary server goes down, Tergum automatically redirects traffic to your backup server—keeping your site online while you resolve the issue.
How It Works
┌─────────────┐ Real-time ┌─────────────┐
│ Master │ ──────────────────▶│ Slave │
│ Server │ Replication │ Server │
└─────────────┘ └─────────────┘
│ │
│ Heartbeats │ Cloudflare
▼ │ Tunnel
┌─────────────┐ │
│ Tergum │◀─────────────────────────┘
│ Backend │
└─────────────┘
│
│ Failover detected?
│ Update DNS ──────▶ Traffic redirected to slave
▼
┌─────────────┐
│ Cloudflare │
│ DNS │
└─────────────┘
- Real-time Replication: Database and files sync continuously from master to slave
- Health Monitoring: Agents on both servers report health every 30 seconds
- Automatic Failover: When master is unreachable, DNS updates to point to slave
- Instant Recovery: Cloudflare Tunnel provides immediate public access to slave
Quick Start
Prerequisites
Before you begin, ensure you have:
- ✅ Two servers (master with WordPress, slave for backup)
- ✅ Root SSH access to both servers
- ✅ Ubuntu 20.04+ or Debian 11+ on both servers
- ✅ A Tergum account
- ✅ A Cloudflare account (free tier works)
- ✅ A Tailscale account (free tier works)
Setup Steps
- Create your account and log into the dashboard
- Run the Initial Setup wizard in the dashboard
- Install Tailscale on both servers for secure networking
- Run the installer scripts on master and slave
- Add your domains and configure failover
The entire setup typically takes 30-60 minutes.
Key Features
| Feature | Description |
|---|---|
| Database Replication | MySQL/MariaDB master-slave replication with lag monitoring |
| File Synchronization | Real-time file sync using inotify + rsync |
| Automatic Failover | DNS updates via Cloudflare when outages are detected |
| Health Dashboard | Real-time monitoring with historical analytics |
| Email Alerts | Instant notifications for outages, lag, and disk space |
| Cloudflare Tunnel | Secure public access to slave without port forwarding |
Architecture Overview
Tergum uses a push-based architecture:
- Agents run on your servers and push metrics to Tergum (outbound HTTPS only)
- No inbound ports need to be opened on your servers
- Tailscale provides secure server-to-server communication
- Cloudflare Tunnel handles public access to the slave during failover
This design works behind NAT, firewalls, and residential internet connections.
Need Help?
- 📖 Continue to Installation
- ❓ Check the FAQ
- 🔧 See Troubleshooting
- 📧 Contact [email protected]