FEATURES
Everything you need to operate self-hosted Supabase.
Kylth covers the operational surface that appears the moment you run Supabase yourself — deploying it, migrating it, backing it up, keeping its certificates valid, and knowing what changed.
Everything in one place.
Manage your infrastructure
Hosts, projects and environments in one place.
Deploy without the busywork
GitHub integration and deployment management.
Database changes that move with your code
Supabase migrations applied per environment, as part of a deployment.
Backups when you need them
Backup destinations, scheduled backups and restore.
Know what's happening
Audit logs, status and operational visibility.
MULTI-HOST
One control plane. As many servers as you need.
Enrol a server once and Kylth manages Supabase on it from then on. Hosts join a private WireGuard mesh, so only the machine running Kylth is ever exposed publicly — every other server keeps its ports closed and is reached through the tunnel.
- Host 18 vCPU · 32 GB10.77.0.2Slots3/8
no public ports
- Host 24 vCPU · 16 GB10.77.0.3Slots1/4
no public ports
- Host 316 vCPU · 64 GB10.77.0.4Slots2/8
no public ports
- kylth.example.com
- *.supabase.example.com
- tls certificates
- the only public ports
How a request reaches a project
- your users
- acme-api.supabase.example.com
- Caddy on the primary
- wireguard tunnel
- Kong on hel-01
Only the primary answers on the public internet. A project's own gateway is bound to its host's loopback and the tunnel, so the machine it runs on never opens a port — and moving a project between hosts changes nothing anyone outside can see.
Enrolling a host
Give Kylth SSH access to a fresh server. It provisions the machine itself and reports each step as it goes, so a failed enrolment tells you which stage broke rather than leaving you to guess.
- 01Install Docker
- 02Create an isolated agent user
- 03Prepare the projects root
- 04Join the WireGuard mesh
- 05Scope the firewall
- 06Verify connectivity
Everything you need to operate self-hosted Supabase.
INFRASTRUCTURE
Manage Supabase across several servers from one Kylth instance.
Create and operate Supabase projects per host.
Separate production, staging and preview configuration.
DEPLOYMENT
Connect repositories and deploy from a branch.
Track deployment state, history and health per project.
Apply Supabase migrations as part of a deployment.
DATA
Scheduled backups to the destinations you configure.
Restore a project from any retained backup.
Bring an installation in, or export it back out.
SECURITY
Issue and renew certificates for project domains.
Configure Supabase auth providers per environment.
Organisation roles and per-project access, with an audit trail.
AUTOMATION
Drive Kylth from your own scripts and pipelines.
A record of every operational change and who made it.