Deploy and Host Freelancer Coding Ledger with Wakapi on Railway

Self-host coding statistics with durable heartbeats and HTTPS cookies.

About Hosting Freelancer Coding Ledger with Wakapi

Freelancers who want project-level coding-time estimates under their control.

Register your account, then set WAKAPI_ALLOW_SIGNUP=false in Railway and redeploy. Obtain your personal API key and point your editor WakaTime plugin at https://YOUR_DOMAIN/api/compat/wakatime/v1. Send a heartbeat before relying on reports.

Included services and storage

Service	Persistent storage	Public access
App	/data	HTTPS domain

First deployment

Review required inputs in the deploy form and supply your own administrator email where requested.
Deploy the services and wait for the application and any database migrations to finish.
Open the generated HTTPS domain and follow the workflow above.

Why Deploy Freelancer Coding Ledger with Wakapi on Railway

The definition supplies an HTTPS endpoint, generated credentials where supported and explicit storage paths. PostgreSQL, when present, stays private. Public upstream image manifests are locked to immutable digests so an upstream tag change does not silently replace a running version.

Common Use Cases

Compare coding effort between client projects.
Review languages and editor usage.
Keep a private coding history.

Dependencies for Freelancer Coding Ledger with Wakapi

Upstream application and its documentation. The upstream authors own the application and its license. This recipe does not claim application authorship or official endorsement.
A Railway plan with resources sufficient for these services. Hosting, storage and outbound traffic are billed by Railway; no software subscription, bank connection, SMTP account or provider credit is included.

Operational limits and backups

Registration is initially enabled so the first owner can join; close it after setup. Raw heartbeats are retained for 12 months. Coding activity does not capture meetings or all billable time and is not an invoicing or payroll system.

Run one replica for volume-backed applications. Schedule volume backups and export important application data; a persistent volume is not a backup. Keep generated secrets with the backups and review upstream migration notes before changing the pinned image. Credentials cannot all be rotated by changing first-run environment variables after accounts already exist.

Validation status

Prepared on 2026-10-18 from upstream installation documentation and public image manifests. Railway schema, variable references and publication metadata are checked before publication. Application runtime boot checks were not performed. This is an independently authored deployment recipe for existing software, not a claim of novel software, audited security or Railway partner verification.

Deploy this recipe

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

FastAPI REST Web Starter — Python REST API starter with HTTPS and a pinned upstream source snapshot.
Django PostgreSQL Web Starter — Django LTS starter with Postgres, generated secrets and DEBUG disabled.
Meilisearch with Persistent Indexes — Search API with persistent indexes, production auth and a generated key.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.