Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A minimalist, WakaTime-compatible backend for coding statistics. Editor plugins send heartbeats to your server instead of wakatime.com, and Wakapi turns them into dashboards of time per project, language, editor, machine and operating system, with leaderboards, badges and a public API. It is a single Go binary that stores data in SQLite by default, with MySQL and PostgreSQL as options, and it can import your existing WakaTime history.
Runs on a VPS from $4/mo (Kamatera 1GB, 1 GB RAM) · prices checked Nov 2026
Fits home hardware (23 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Wakapi when you already use WakaTime editor plugins and want the data on your own server. It is a minimalist, WakaTime-compatible backend written in Go and licensed MIT: you point the plugins at your instance and it builds dashboards of coding time by project, language, editor, machine and operating system, with badges, leaderboards and an API, and it can import history from WakaTime. Our snippet follows the README's Docker instructions with Compose, pinned to ghcr.io/muety/wakapi:2.18.2, released 2026-10-14, using the default SQLite database on a named volume and a password salt generated with `openssl rand`. We did not find an upstream RAM minimum, so our 128 MB floor is an estimate. The other trackers in the catalog differ in what they record: Kimai and solidtime are manual or timer-based tools with customers, projects and invoicing, and Traggo and TimeTagger are tag-based timers you start yourself. Wakapi is the only one fed automatically by your editor, so it measures coding time and does not replace billing time sheets.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Wakapi — adapted from the README's Docker instructions (SQLite default, named volume), pinned to 2.18.2
mkdir -p wakapi && cd wakapi
echo "WAKAPI_PASSWORD_SALT=$(openssl rand -hex 16)" > .env
cat > docker-compose.yml <<'EOF'
services:
wakapi:
image: ghcr.io/muety/wakapi:2.18.2
init: true
restart: unless-stopped
env_file: .env
ports:
- 3000:3000
volumes:
- wakapi-data:/data
volumes:
wakapi-data:
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:3000/api/health; do sleep 3; done'
# → http://SERVER_IP:3000 (register the first account, then set WAKAPI_ALLOW_SIGNUP=false in .env; plain HTTP, so put TLS in front and set WAKAPI_INSECURE_COOKIES=false)Wakapi's README and configuration reference flag these before you rely on it:
Wakapi used 23 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 128 MB.
The Wakapi install snippet is marked verified on Ubuntu 26.04 (Nov 2026).