Kylth runs on a server you control. It creates Supabase projects on that server, gives each one its own HTTPS address, and takes care of the work around them, all from one dashboard: backups and restores, certificates, updates, and who has access.
The problem it solves
Supabase publishes everything you need to self-host a project. But every self-hosted project then needs its own configuration, secrets, HTTPS certificate, backups and updates, maintained by hand. Kylth does that work for every project on the server.
What Kylth manages
- Projects. Create Supabase projects from a template, start and stop them, and set their resource limits.
- HTTPS. Each project gets its own address, with a Let’s Encrypt certificate that is issued and renewed automatically.
- Backups and restores. On demand or on a schedule, to the server or to S3-compatible storage.
- Updates. Each project’s Supabase images, from the project’s page.
- Monitoring. Server and project resource use, certificate checks and alert rules.
- People and access. Users, organisations and roles, with an audit log of changes.
- Automation. A REST API with API keys, and deployments from GitHub.
- More than one server. With a commercial licence, one Kylth can manage projects on several servers.
What Kylth doesn’t do
- It doesn’t host your data. Projects run on your server.
- It isn’t a hosted service. Your projects don’t depend on a Kylth cloud, and Kylth checks its licence without contacting anyone.
- It doesn’t change Supabase. Projects run Supabase’s own open-source images.
- It doesn’t back up the server for you. Kylth backs up your projects. Backups explains what else you need.
Where it runs
Kylth itself is one Docker container on your Linux server. It uses the server’s Docker to run each project as a separate set of containers. How Kylth works shows how the pieces connect.
Terms used in these docs
| Term | Meaning |
|---|---|
| Server | The Linux machine you install Kylth on. |
| Host | A server whose projects Kylth manages. A single-server setup has one host: the server Kylth runs on. Licences count hosts. |
| Project | One Supabase project (its database, API, Auth, Storage and Studio), running as containers on a host. |
| Organisation | A group of users and projects inside Kylth. |
| Control plane | Software that manages other software. Here that’s Kylth; the projects it manages keep running without it. |
Is Kylth right for you?
Kylth is a good fit if you:
- want to self-host Supabase on a server you control
- want several projects managed from one place
- need your data to stay on your own infrastructure
- are comfortable running a Linux server with Docker
It’s probably not the right fit if you:
- want someone else to run the infrastructure for you
- don’t have an x86_64 Linux server you can run as root
- want a fully managed service. Supabase’s own hosted platform exists for that.
Next, How Kylth works explains what Kylth sets up on your server.