Your apps, your servers. Every instance a microVM. Deploy with git push.
Jokku is an open source, self-hosted platform modeled on Dokku. It builds your Dockerfile, boots each instance in its own Firecracker microVM, puts your domains on HTTPS, and spreads your apps across every server you add.
-----> getting started
From a bare server to HTTPS in four commands.
Nothing to configure, and nothing to install on your laptop. Just git and ssh.
- 01
Install
$ curl -fsSL …/install.sh | sudo shOn a fresh Ubuntu or Debian server with KVM. Your SSH keys can deploy right away.
- 02
Push
$ git push jokku mainJokku builds your Dockerfile, boots it and prints a working URL.
- 03
Add a domain
$ jokku domains:add myapp myapp.comPoint your DNS at the server. Every server can take traffic.
- 04
Turn on HTTPS
$ jokku letsencrypt:enable myappCertificates are issued, renewed, and HTTP redirects to HTTPS.
-----> what you get
Everything a platform does. On servers you own.
Deploys, scaling, certificates, databases, backups, logins and private networking, running on hardware you control, even at home, from one binary.
A microVM for every instance→
Each instance boots in its own Firecracker virtual machine, with its own kernel, from a read-only disk built from your image. Restarting or updating Jokku leaves them running.
Clusters in one command→
One server is a complete Jokku. Join more over an encrypted mesh and apps spread across them. If one dies, its apps start on the others.
Zero-downtime deploys→
New instances boot beside the old ones and take traffic once they pass checks. A failed deploy is rejected, and the old version keeps serving.
HTTPS without thinking→
Let’s Encrypt certificates for every domain, renewed for you, by the Caddy built into Jokku and shared across your servers.
Dockerfiles, compose, images→
Build a Dockerfile, deploy a whole compose file with each service as a process, or run any image from a registry.
Serve from home, no port open→
Run Jokku in a home lab and add an edge: a small public server your servers dial. It serves your domains, and the services on your network you route to it, like Home Assistant or a NAS.
A login in front of anything→
A shared password, or your users with authenticator codes, before any app. One login for every app, share links that expire, and nothing to change in the app.
Volumes that move→
Give a database a disk that moves with it when its server is drained, copied while the app keeps running.
Backups that restore themselves→
Every 15 minutes, incremental and encrypted, to any S3-compatible bucket. If a server dies, its volumes come back on another one from their latest backup.
Databases in one command→
Postgres, MySQL and Redis from their official images, linked to your apps with a connection URL, reachable only from them, and backed up from the start.
Apps find each other by name→
cache.internal reaches your cache app from any app, on any server, over WireGuard.
Logs and a shell, anywhere→
Follow every instance and every request in one stream, or open a shell inside a running microVM with jokku enter.
Updates you don’t worry about→
One command updates every server, one at a time. Your apps keep serving, the state is backed up first, and a release that doesn’t come up is rolled back.
-----> clusters
One server, or a rack of them.
One server is a complete Jokku. Add another with one command and your apps spread across both, over an encrypted network. When a server dies, its apps start on the others.
jokku cluster:join-commandprints a one-liner. Run it on a new server and it joins the cluster over WireGuard.- Apps spread across every server, and every server takes web traffic.
- A server that stops reporting is marked down within 30 seconds. A minute later its instances are running on the others.
- Volumes with backups are restored onto another server after five minutes, so their apps come back too.
jokku nodes:drainempties a server for maintenance with no downtime, andjokku updateupdates every server, one at a time.
-----> edges
Serve from home. Open no ports.
Run Jokku on the servers in your closet and put a $5 VPS in front of them. Your servers dial out to the edge, and the edge serves your domains, with certificates, logins and a firewall out where the internet is.
- ●visitorphone · Denver
- ●visitorlaptop · Berlin
- ●scanner45.148.10.82
- One command
jokku edge:add root@203.0.113.7logs in over ssh, installs Jokku on the VPS and connects it.- Nothing open at home
- Your servers dial out over WireGuard. The edge reaches only what its routes need: not ssh, and not the rest of your network.
- Scanners stop at the edge
- The firewall bans them by their own address before they touch your home connection, and your logs show every visitor’s real address.
- Quick over a slow upload
- Each request goes straight to the server that runs the app, which compresses the response before it leaves home.
- Anything on your network
jokku external:create ha http://192.168.1.50:8123gives Home Assistant, a NAS or Proxmox a domain, HTTPS and a login.- Databases too
- Expose a database through the edge for a desktop client, or keep it on your network only.
-----> jokku top
Watch every request land.
A live view of your servers, apps and microVMs, right in your terminal. Press 6 and every request flies across its app’s lane, green, yellow or red, and lands on the instance and server that answered.
-----> jokku top
See inside every database.
Press 8 for each database’s connections, queries a second and how long they take: p50, p95 and p99 for MySQL and Redis, the average for Postgres, and how often the cache answers. Pick one to see which apps are connected and its slowest queries.
-----> under the hood
From git push to a running microVM.
Every deploy takes the same path, whether it started as a push, a compose file or a registry image. Nothing changes until the new version is healthy.
- 01
git push
Your source streams to the control server.
source.tar
- 02
BuildKit
Your Dockerfile builds to an OCI image.
oci image
- 03
Root disk
Layers flatten into one read-only disk.
rootfs.ext4
- 04
Release
Build, config and sizes, numbered and immutable.
v12
- 05
microVMs
Instances boot, pass checks, take traffic.
web.1 web.2 web.3
-----> coming from dokku
If you know Dokku, you already know Jokku.
Same command names, same argument order, same output, same git push. What changes is where your apps run, and how many servers they can use.
| dokku | jokku | |
|---|---|---|
| Runs apps in | Containers | Firecracker microVMs |
| Servers | One | As many as you add |
| Proxy | nginx | Caddy, built in |
| storage:mount | A host directory | A disk that moves with its app |
| Builds | Buildpacks, Dockerfile, … | Dockerfile, compose, images |
| Databases | postgres:* plugins | db:postgres:*, built in |
| Behind NAT | Open your ports | An edge your servers dial |
-----> status
Early, and moving fast.
One server or a cluster, git push deploys work today. Here’s what’s built and what’s next.
- M0 Done
Control plane
API, SQLite, CLI over SSH, git receive, the installer, safe updates
- M1 Done
Single-server deploys
BuildKit builds, Firecracker microVMs, embedded Caddy, rollouts, logs, ps:*
- M2 Done
Clusters
WireGuard mesh, one-command joins, scheduling, failover, jokku top
- M3 Building
Remote API
Registry images and logins are done; HTTPS API tokens, git:sync and deploy keys are next
- M4 Building
Depth
enter, volumes, backups (scheduled, restored automatically when a server dies) and databases are done; the jailer, run, rollbacks and SQLite are next
- M5 Done
Home labs
Edges your servers dial, so a home lab serves the internet with no open port; external apps; logins with authenticator codes
Your servers. Your apps. One push.
Bring a fresh Ubuntu or Debian server with KVM and ports 80 and 443 free. The installer does the rest.
Installed and updated 206 times·Installs v0.8.22