Track your build hours — on your own infra.

Two trackers, one goal

Coding time and general app usage are two different measurements. One tool won't do both well, so run the best of each. Both store data on your servers.

1Deploy Wakapi as a resource

On the boom-hosting droplet (24.199.95.101), add a new resource from the official image. Docker Compose is the cleanest path since it bundles the app + its own Postgres.

# Coolify → New Resource → Docker Compose
services:
  wakapi:
    image: ghcr.io/muety/wakapi:latest
    environment:
      WAKAPI_DB_TYPE: postgres
      WAKAPI_DB_HOST: wakapi-db
      WAKAPI_DB_NAME: wakapi
      WAKAPI_DB_USER: wakapi
      WAKAPI_DB_PASSWORD: ${WAKAPI_DB_PASSWORD}   # pull from Doppler
      WAKAPI_PASSWORD_SALT: ${WAKAPI_SALT}
      WAKAPI_ALLOW_SIGNUP: "false"              # lock it to you
    ports:
      - "3000"
  wakapi-db:
    image: postgres:17
    environment:
      POSTGRES_DB: wakapi
      POSTGRES_USER: wakapi
      POSTGRES_PASSWORD: ${WAKAPI_DB_PASSWORD}
    volumes:
      - wakapi-pg:/var/lib/postgresql/data
volumes:
  wakapi-pg:

2Put it on a real domain

Set the resource's Domains field to something like wakapi.boommedia.us and point a DNS A record at 24.199.95.101. Coolify + Traefik auto-issue a Let's Encrypt cert. Since signup is disabled, create your single account from the container:

# open the running container's shell, or use the web UI once with
# WAKAPI_ALLOW_SIGNUP temporarily "true", register, then set it back to "false".

Log in, open Settings, and copy your API key — you'll need it for the editor.

3Point WakaTime at your server

Install the WakaTime extension in VS Code (it also has a Claude Code / terminal plugin). Then edit ~/.wakatime.cfg so it reports to Wakapi instead of the hosted service:

# C:\Users\eric\.wakatime.cfg
[settings]
api_url = https://wakapi.boommedia.us/api
api_key = your-wakapi-api-key

That's it. Every file you edit now logs silently. Within a day you'll see hours per project on your Wakapi dashboard — each SaaS app becomes a project automatically based on its folder.

4Install ActivityWatch

For time outside the editor — browser, ClickUp, Canva, email, meetings — install ActivityWatch on your Windows PC. It runs a tiny local server and tracks the active window + browser tab, entirely offline.

• Download the Windows installer, launch it, set it to start with Windows.
• Add the browser watcher extension (Chrome/Edge) for per-tab detail.
• Review at http://localhost:5600 — categorized time, no cloud, no account.
• Optional bridge: the aw-watcher-wakatime module can forward activity into Wakapi so coding + app usage sit in one dashboard.

5Roll totals into ClickUp + feed Dashee

The raw hours now live in Wakapi/ActivityWatch. Two things to do with them:

• Billing / costing (now): weekly, glance at the per-app hours and log them against your ClickUp "Build Time" tasks. This is your real cost-per-app number for valuation and the Founderpath data room.
• Product research (later): living with a real tracker tells you exactly what the Dashee time-tracking feature must capture — auto vs manual, project mapping, idle handling, billable flag. You'll build it from experience, not guesswork.

Setup checklist