Skip to main content

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 │
└─────────────┘
  1. Real-time Replication: Database and files sync continuously from master to slave
  2. Health Monitoring: Agents on both servers report health every 30 seconds
  3. Automatic Failover: When master is unreachable, DNS updates to point to slave
  4. 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

  1. Create your account and log into the dashboard
  2. Run the Initial Setup wizard in the dashboard
  3. Install Tailscale on both servers for secure networking
  4. Run the installer scripts on master and slave
  5. Add your domains and configure failover

The entire setup typically takes 30-60 minutes.

Key Features

FeatureDescription
Database ReplicationMySQL/MariaDB master-slave replication with lag monitoring
File SynchronizationReal-time file sync using inotify + rsync
Automatic FailoverDNS updates via Cloudflare when outages are detected
Health DashboardReal-time monitoring with historical analytics
Email AlertsInstant notifications for outages, lag, and disk space
Cloudflare TunnelSecure 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?