Your host.
Your network.
Your record.
Kodela runs on one Linux machine you control: the console, the workspaces, the brokers, the firewall and the audit trail. Nothing about your code passes through us. If a platform operator grants it and your organisation turns it on, members’ own computers can host workspaces too.
Set the sliders to a machine you have. The readout uses only the figures we publish, and says where they stop.
RAM ÷ (2 GB per active workspace + 1 GB with the browser IDE). No host reserve is subtracted, because none is published: the host's own services come out of this ceiling.
- MemoryAt or above the 8 GB we run on.ok
- DiskAt or above the 30 GB we run on. No per-workspace disk figure is published, so disk sets no count.ok
- CPUEach workspace is capped at 2 CPUs. A cap is not a reservation, so 8 cores set no count.no count
Not a tested maximum. We have not published one. These are the figures we run on, not a sizing guarantee.
What you need
One machine for the platform. No cloud provider, no managed database and no Kubernetes.
- Operating system
- Ubuntu 24.04 with systemd
- Runtime
- Docker
- Python
- Python 3.12 (standard library only, no pip install)
- Tools
- git, curl, jq, openssl, sudo
- Memory
- 8 GB RAM or more
- Disk
- 30 GB disk or more
- Per workspace
- Plan about 2 GB of memory per active workspace, and about 1 GB more for each person using the browser IDE
- Limit
- These are the figures we run on, not a sizing guarantee.
What stays in your hands
Eleven things you run yourself, each with the line where it stops.
Deployment
One commit's files are published byte-exactly (
bin/deploy push), verified (verify) and rolled back (rollback).Limit: the remote bring-up tool,
bin/provision-host, has not yet been proven against a second machine.Infrastructure
Your host OS, your Docker, your disk.
Limit: Kubernetes, Helm, Docker Compose and Terraform are not supported. The platform is one host.
Data
Code, audit, chat and credentials live on your host. Model calls go from your host to your provider.
Limit: egress starts in observe, which logs and lets traffic through until you switch it to deny. A workspace on a member’s own computer, if turned on, keeps its code on that computer’s disk, and egress there is observed, not enforced.
Networking
The front door listens on your host. Put TLS in front of it, for example a reverse proxy or a Cloudflare Tunnel. Only 80 and 443 need to face users.
Limit: plain HTTP unless you supply TLS. There is no built-in certificate automation (ACME).
Upgrades
bin/deploy, with the local CI gate before release. A schema-skew guard refuses API calls, with a sentence, when the store is newer than the code.Limit: you run each upgrade. Nothing on the host updates itself; only the small agent on a member’s computer does.
Administration
The operator console plus about 30 command-line tools.
Limit: there is no public API. The console's routes are internal.
Security
The host is the trust anchor: who has root and who is in the Docker group decides everything.
Limit: the audit chain and the authorship record do not protect against the host's root user.
Compliance
Your host's controls plus the evidence report, scored against ISO 27001, SOC 2 or NIST 800-53 controls.
Limit: Kodela holds no certification. The report is evidence for your audit, not a certificate.
Backup
bin/backupproduces encrypted, per-unit parts and supports partial restore. It refuses to run until you set a key.Limit: nothing schedules it for you. Add a timer.
Scale
One host today. Additional worker hosts are built and off by default. Members’ own computers can host workspaces when an operator grants it and the organisation turns it on.
Limit: no high availability. The control plane is one store on one host.
Air-gapped (partial)
Every component is version-pinned and checksum-verified, and images can be moved with
docker save.Limit: there is no offline installer bundle yet.
Which deployment model is right for you?
Hosted by us: not available. There is no hosted version of Kodela. Everything on this site describes software you run on your own host. If a managed version would decide it for you, tell us: that decision is still open.
- You have a Linux host and want control.Self-host today
- Your developers want workspaces on their own computers, beside the host. An operator grants it and your organisation turns it on. Egress there is observed, not enforced; tested end to end only on Windows.Off by default
- You need someone else to run it.Not available yet. Tell us.
- You need high availability or an air-gapped installer.Not available yet. Tell us which.
What it does not do yet
Read this before you size a machine. The full list is on known gaps.
- No hosted version. You run the host, or nobody does.
- No high availability. One host and one store; worker hosts are built and off.
- Members’ computers are observed, not fenced. Workspaces run on your Kodela host. If a platform operator grants it and your organisation turns it on, a member’s own computer can host their workspaces too. There, internet access is observed, not enforced; DNS filtering is not enforced; the source on its disk is readable by whoever uses it; and Docker is not available. Tested end to end only on Windows (Linux laptops up to enrolment; Mac only in a simulation).
- No tested workspace maximum. Plan by memory, about 2 GB per active workspace.
- No scheduled backup.
bin/backupruns when you run it. - No offline installer. Air-gapped installs are partial.
- No TLS of its own. Plain HTTP until you put a TLS front end in place.
Check your host
Three steps, starting with a read-only check that changes nothing.