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.

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
ServerLinux with Docker and Docker Compose 2.29 or newer; nothing else to install
CPU4 cores or more, x86_64 or ARM64
Memory8 GB or more
Disk50 GB for the system, plus room for your files and backups
DatabaseMySQL 8.0: the Compose file runs it, or use your own over verified TLS
NetworkTwo hostnames (the app and its kit editors) behind your HTTPS proxy, with certificates you manage

Install

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

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

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
Browserany modern browser
Your identity providerOIDC
Your server
One appaccounts · spaces · audit
Kit packages origineditors, separate origin
Kition Serverbuilt in · real-time rooms
Your data
MySQL 8metadata · audit
Disk or object storagefile contents · versions
Model endpointoptional · 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
TeamCPUMemoryDiskDatabase
20 people4 vCPU8 GB200 GBMySQL on the same host
50 people8 vCPU16 GB500 GBSame host, or a separate MySQL
200 people16 vCPU32 GB2 TBSeparate 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.