---
title: "Self-host Kition One — requirements, install and operations"
description: "Run Kition One on your own Linux servers: requirements, a Docker Compose or install-script install, the architecture, backups, upgrades and sizing for 20, 50 and 200 people."
canonical: "https://one.kition.ai/self-hosting"
---

> Canonical HTML: [https://one.kition.ai/self-hosting](https://one.kition.ai/self-hosting)

Kition One · Self-hosting

# Run it on your own servers

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.

[Request early access](https://one.kition.ai/demo?kind=early-access)[Book a demo](https://one.kition.ai/demo)

## Requirements

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.

-   Container images for x86\_64 and ARM64.
-   TLS on every connection, including to MySQL.

Server requirements

| 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 |

## Install

1.  **Point two hostnames at the server**One for the app, one for the kit editors, which run on their own origin.
    
2.  **Run the install**With Docker Compose, or the install script, which writes the settings and secrets for you.
    
3.  **Open `/setup`**Create 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.

shell

```
# 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
```

shell

```
# 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>
```

## Architecture

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.

-   A built-in Kition Server for real-time collaboration.
-   No telemetry: nothing phones home.
-   Bring your own model key, or a private endpoint.

People

Browser*any modern browser*

Your identity provider*OIDC*

Your server

One app*accounts · spaces · audit*

Kit packages origin*editors, separate origin*

Kition Server*built in · real-time rooms*

Your data

MySQL 8*metadata · audit*

Disk or object storage*file contents · versions*

Model endpoint*optional · your choice*

## Operations

### 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.

### Upgrade and roll back

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.

### Health checks

Point your monitoring at the status endpoint, or read it on the Operations page.

### Support bundle

One click downloads a diagnostic file with versions and health observations, and no file contents. Your admin decides whether to send it.

## Sizing

Starting points by team size

| 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 |

Disk depends most on your files: design, video and CAD files are large, and versions and backups add to them. Watch the space quotas on the admin console and grow storage before it fills.

## Plan your install with us

Tell us about your environment and we will help you plan the install.

[Request early access](https://one.kition.ai/demo?kind=early-access)[Book a demo](https://one.kition.ai/demo)
