v0.8.22New: serve from home with edges, logins and databases

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.

Get started206 downloads
~/code/myapp
$
Built onFirecrackerWireGuardCaddyBuildKitSQLite

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

  1. 01

    Install

    $ curl -fsSL …/install.sh | sudo sh

    On a fresh Ubuntu or Debian server with KVM. Your SSH keys can deploy right away.

  2. 02

    Push

    $ git push jokku main

    Jokku builds your Dockerfile, boots it and prints a working URL.

  3. 03

    Add a domain

    $ jokku domains:add myapp myapp.com

    Point your DNS at the server. Every server can take traffic.

  4. 04

    Turn on HTTPS

    $ jokku letsencrypt:enable myapp

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

web.1firecracker microVM
your processas the image’s USER
volumesvdd · /app/data
scratch layervdc · writable
root diskvda · read-only, shared
kernel 6.1init is PID 1
web.2firecracker microVM
your processas the image’s USER
volumesvdd · /app/data
scratch layervdc · writable
root diskvda · read-only, shared
kernel 6.1init is PID 1

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.

$ jokku cluster:join-command
server-1control
server-2worker
server-3worker
WireGuard mesh · udp/51820

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.

v11
v12
bootswitchretire
● checks pass, then traffic moves

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.

$ jokku letsencrypt:enable myapp
https://myapp.comrenews itself
https://www.myapp.comrenews itself
https://api.myapp.comrenews itself

HTTPS without thinking→

Let’s Encrypt certificates for every domain, renewed for you, by the Caddy built into Jokku and shared across your servers.

$ git push jokku main
$ jokku builder:compose shop
$ jokku builder:image cache redis:7
Dockerfile · compose.yaml · any registry image

Dockerfiles, compose, images→

Build a Dockerfile, deploy a whole compose file with each service as a process, or run any image from a registry.

$ jokku edge:add root@203.0.113.7
browserhttps
edge1
public · certs · logins
home dials out
home labno open ports
shopmicroVMs
ha192.168.1.50:8123
WireGuard · the edge reaches only what it routes

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.

$ jokku http-auth:enable photos wes sam
Log in to photos
wes
482 913
Verify

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.

$ jokku nodes:drain server-1
server-1server-2
data82%
copied while the app keeps running

Volumes that move→

Give a database a disk that moves with it when its server is drained, copied while the app keeps running.

$ jokku backups:list shop data
BACKUPTAKENADDED
2026-10-09T14-15-00Z2m ago+1.8 MB
2026-10-09T14-00-00Z17m ago+640 KB
2026-10-09T13-45-00Z32m ago+2.3 MB
● server-2 down 5m: restored on server-3

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.

$ jokku db:postgres:create shopdb
$ jokku db:postgres:link shopdb shop
# set on shop
DATABASE_URL=postgres://…@postgres-shopdb.internal
Postgres · MySQL · Redis, each on its own volume

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.

# shop’s config
REDIS_URL=redis://cache.internal:6379
JOBS=http://worker.shop.internal
resolves on any server, follows deploys

Apps find each other by name→

cache.internal reaches your cache app from any app, on any server, over WireGuard.

$ jokku logs myapp -t
app[web.1]: Listening on :3000
app[router]: GET / status=200 4.2ms
$ jokku enter myapp
/app $

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.

$ sudo jokku update
-----> Updating jokku from v0.8.19 to v0.8.20
-----> Backing up the database
-----> Restarting jokku
jokku v0.8.20 is running
● apps kept serving · rolls back if it fails

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-command prints 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:drain empties a server for maintenance with no downtime, and jokku update updates every server, one at a time.
Add a server
ssh -t jokku@your-server top
jokku top · control server-1 · 3/3 nodes · 3 apps · 6/6 instances healthy
1 Overview2 Nodes3 Apps4 Instances5 Events
Nodes
● server-1cpu ██░░░░░░░░ mem ████░░░░░░api web.1shop web.1
● server-2cpu ██░░░░░░░░ mem ████░░░░░░api web.2blog web.1
● server-3cpu ██░░░░░░░░ mem ████░░░░░░api web.3shop web.2
Recent events
nodeserver-3server-3 is updated to v0.8.20
nodeserver-3server-3 joined the cluster (8 CPUs, 16384 MiB)

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

Set up an edge
the internetanyone
  • ●visitorphone · Denver
  • ●visitorlaptop · Berlin
  • ●scanner45.148.10.82
https
edge-1$5 VPS · 203.0.113.7
✓ HTTPS certificates
✓ routes and logins
✕ firewall3 banned
↑← WireGuard, dialed from home
home labno open ports
●server-1shopblog
●server-2apiwiki
→ha192.168.1.50:8123
1,284 requests served from home
One command
jokku edge:add root@203.0.113.7 logs 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:8123 gives 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.

Tour jokku top
ssh -t jokku@your-server top
jokku top · control server-1 · v0.8.20 · 3/3 nodes · 4 apps · 7/7 instances healthy
1 Overview2 Nodes3 Apps4 Instances5 Events6 Traffic
35.7 req/s·p50 5.1ms p95 24ms·0.4% errors·18,204 total
api19.2/s
myapp9.8/s
shop6.0/s
docs0.6/s
requests by node server-1 12.1/s · server-2 11.6/s · server-3 12.0/s
Recent requests
1-6/tab views p pause c clear ? help q quit

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

Tour the Databases view
ssh -t jokku@your-server top
jokku top · control server-1 · v0.8.20 · 3/3 nodes · 3 apps · 3 databases
1 Overview2 Nodes3 Apps4 Instances5 Events6 Traffic7 Backups8 Databases
DATABASEENGINECONNECTIONSACTIVEQUERY/SLATENCY p50 p95 p99HIT
mysql blog-db on server-2 · looked 2s ago · at most 31 connections since it started
PER SECLATENCYHIT
last minute42310µs 2.8ms 41msp50 310µs p95 2.8ms p99 41ms-
last hour39300µs 2.6ms 37msp50 300µs p95 2.6ms p99 37ms-
last day35290µs 2.4ms 33msp50 290µs p95 2.4ms p99 33ms-
CONNECTED
blog web.1blog7 (1 active)
blog web.2blog7
SLOWEST QUERIES, BY TOTAL TIME
4.1ms×18200SELECT option_name, option_value FROM wp_options WHERE autoload IN (?, ?, ?, ?)
23ms×2400SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = …
900µs×51000SELECT meta_key, meta_value FROM wp_postmeta WHERE post_id IN (…)
USERS blog all
last minute · minute/hour/dayclick a database to look inside1-9 views ? help q quit

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

  1. 01

    git push

    Your source streams to the control server.

    source.tar

  2. 02

    BuildKit

    Your Dockerfile builds to an OCI image.

    oci image

  3. 03

    Root disk

    Layers flatten into one read-only disk.

    rootfs.ext4

  4. 04

    Release

    Build, config and sizes, numbered and immutable.

    v12

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

muscle memory, intact
$ dokkujokku apps:list
$ dokkujokku apps:create myapp
$ dokkujokku config:set myapp SECRET=s3cret
$ dokkujokku domains:add myapp myapp.com
$ dokkujokku letsencrypt:enable myapp
$ dokkujokku ps:scale myapp web=3 worker=1
$ dokkujokku logs myapp -t
$ dokkujokku ps:report myapp
$ dokkujokku storage:mount myapp data:/app/data
$ dokkujokku http-auth:enable myapp
dokkujokku
Runs apps inContainersFirecracker microVMs
ServersOneAs many as you add
ProxynginxCaddy, built in
storage:mountA host directoryA disk that moves with its app
BuildsBuildpacks, Dockerfile, …Dockerfile, compose, images
Databasespostgres:* pluginsdb:postgres:*, built in
Behind NATOpen your portsAn 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.

  1. M0 Done

    Control plane

    API, SQLite, CLI over SSH, git receive, the installer, safe updates

  2. M1 Done

    Single-server deploys

    BuildKit builds, Firecracker microVMs, embedded Caddy, rollouts, logs, ps:*

  3. M2 Done

    Clusters

    WireGuard mesh, one-command joins, scheduling, failover, jokku top

  4. M3 Building

    Remote API

    Registry images and logins are done; HTTPS API tokens, git:sync and deploy keys are next

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

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

$curl -fsSL https://raw.githubusercontent.com/wes/jokku/main/install.sh | sudo sh

Installed and updated 206 times·Installs v0.8.22