Backups
Set the daily time and how many to keep in Admin. One backs itself up and keeps a history of every run; copy the backups off the server with your own tools.
Kition One · Self-hosting
One Linux server with Docker is enough for most teams; MySQL runs next to One in the same Compose file. Install in 10 minutes with Docker Compose.
The minimum for a team of up to 20. One runs in containers; you do not need Node, Rust or any SDK on the server.
| Server | Linux with Docker and Docker Compose 2.29 or newer; nothing else to install |
|---|---|
| CPU | 4 cores or more, x86_64 or ARM64 |
| Memory | 8 GB or more |
| Disk | 50 GB for the system, plus room for your files and backups |
| Database | MySQL 8.0: the Compose file runs it, or use your own over verified TLS |
| Network | Two hostnames (the app and its kit editors) behind your HTTPS proxy, with certificates you manage |
/setupCreate the organisation and the first owner, then invite your team.The container images and the install script are not published yet; they come out at launch.
# In the folder with compose.yaml, mysql-init/ and env.example
cp env.example .env
# Fill in four settings
# KITION_ONE_URL=https://one.example.com
# KITION_ONE_KITS_URL=https://kits.one.example.com
# KITION_ONE_SECRET_KEY= (openssl rand -hex 32)
# MYSQL_PASSWORD= (openssl rand -hex 16)
nano .env
# Start MySQL, the migration, then One
docker compose up -d
# The setup token for the first owner
docker compose logs one | grep 'setup token'
# Open https://one.example.com/setup# A menu: install, upgrade, backup, restore, logs
sh install.sh
# Checks Docker Compose, writes ~/kition-one/.env with
# generated secrets, starts One and prints the setup token
sh install.sh install --url https://one.example.com \
--kits-url https://kits.one.example.com
# Backs up, moves to the new image, rolls back on failure
sh install.sh upgrade --image <new image>
sh install.sh backup
sh install.sh restore <backup>Everything runs inside your network. Kit editors load from their own hostname, so a file’s editor is isolated from the rest of the app.
Set the daily time and how many to keep in Admin. One backs itself up and keeps a history of every run; copy the backups off the server with your own tools.
The install script backs up, then moves to the new image. If it is not healthy within ten minutes, the previous version and the pre-upgrade backup come back.
Point your monitoring at the status endpoint, or read it on the Operations page.
One click downloads a diagnostic file with versions and health observations, and no file contents. Your admin decides whether to send it.
| Team | CPU | Memory | Disk | Database |
|---|---|---|---|---|
| 20 people | 4 vCPU | 8 GB | 200 GB | MySQL on the same host |
| 50 people | 8 vCPU | 16 GB | 500 GB | Same host, or a separate MySQL |
| 200 people | 16 vCPU | 32 GB | 2 TB | Separate MySQL, with its own backups |
Tell us about your environment and we will help you plan the install.