Time tracking that lives in your GitHub repo.

Built for the twenty times a day you touch it.

A tracker earns its place in the small moments — starting without thinking, fixing the time you forgot to stop, seeing the week at a glance. That is where the work went.

Then bill from it.

Reports reads every teammate's branch in the shared repository as one view. Rates stay on your machine, so you can share the hours without sharing what they cost.

• →Repository-wide reports across everyone writing to the shared repo
• →Break down by day, week, month, person, source or task
• →Total time, average per task, distinct task count and billable amount
• →Effective-dated hourly rates, stored in your browser and never committed
• →Mixed currencies converted at the rate for each day
• →Export to CSV or JSON, or print straight to PDF
• →Invoice from the filtered report — numbered, taxed, printed or saved as PDF

Why people move to it.

Everything a tracker normally charges for, and a few things they cannot offer at all.

How it compares.

Open source is not unique to Clockoli: Kimai and solidtime offer it too. The difference is owning your records without operating a separate time-tracking backend. Clockoli uses GitHub; self-hosted trackers give you more control and more software to maintain.

	Clockoli	Toggl Track	Clockify	Harvest	Kimai	solidtime
Where your hours live	Plain JSONL files in your GitHub repo	Vendor-hosted service	Vendor-hosted service	Vendor-hosted service	Your database; managed Cloud also available	Your database; managed Cloud also available
Writing to several places at once	+One install, a repository per client, each one owned by that client	Several workspaces, one account; all of it in Toggl	Several workspaces, one account; all of it in Clockify	A separate Harvest account per company	Customers and projects inside the one instance you host	Organizations and projects inside the one instance you host
Own your data without running a server	+GitHub is the backend; no separate tracker server or database	No customer-controlled backend in SaaS	No customer-controlled backend in SaaS	No customer-controlled backend in SaaS	Run the Kimai application and database	Run the solidtime backend and database
Source code	Open source (GPL-3.0 or later)	Proprietary service	Proprietary service	Proprietary service	Open source core (AGPL-3.0)	Open source core (AGPL-3.0)
Free plans and team costs	Core is free; no seat or usage limits. GitHub limits apply	Limited free plan; paid team features	Free: up to 5 people; paid upgrades	Free: 1 seat, 2 projects; paid teams	Free core; hosting and optional plugins extra	Free self-hosted core; Cloud solo free, teams paid
Reporting	Cross-repo team reports; browser-local billable rates	Basic reports free; advanced/team features paid	Reports included free; advanced features paid	Time reports; advanced reporting by plan	Team, project and customer reports	Reports; Cloud sharing/PDF and team controls paid
Who can read task titles	Anyone with repo read access; hosted by GitHub	Workspace access and roles	Workspace access and roles	Account roles and project access	Your server admins; team/role permissions	Your server admins; organization/project roles
Hourly rates and teammate access	Browser-local, not in shared time files; protect browser access and exports	Service-stored; role-controlled visibility	Service-stored; rate visibility controls	Service-stored; role-controlled visibility	Your database; check roles and export templates	Your database; access depends on role
Getting your data out	+Canonical files already in Git; clone, CSV/JSON, print to PDF	Report exports and API; plan limits apply	Report exports and API; plan limits apply	Report exports and API	Own database, exports (CSV/XLSX/PDF) and API	Own database, report exports and API
Corrections kept as history	Git commits, not an immutable compliance audit log	Audit log: Premium/Enterprise	Audit log: Enterprise	Activity log: Enterprise	Paid Audit Trail plugin; included in Cloud	Full change-audit log not verified in docs
Tracking while on GitHub	In-page issue/PR timer; any URL via popup	GitHub browser-extension integration	In-page GitHub extension timer	In-page issue/PR integration	Third-party GitHub bridge; check compatibility	Extension lists Linear/Jira/Plane; GitHub not listed
Invoicing	Built in and free; rendered in your browser, never committed	PDF invoices even on Free; paid branding options	Standard and above	Included; plan/usage limits apply	Core invoices; advanced e-invoicing plugin	Paid Cloud or on-premise Business feature
Mobile app	-None	iOS and Android	iOS and Android	iOS and Android	Responsive web; third-party mobile apps	Web app; native mobile app not verified
Browsers and desktop	-Chrome Web Store extension; Firefox and Safari builds in testing	Web, browser extensions and desktop apps	Web; Chrome/Firefox/Edge; desktop apps	Web, browser integrations; Mac/Windows apps	Modern web browser; third-party desktop clients	Web; Chrome/Firefox extensions; Mac/Windows/Linux apps

Checked September 10, 2026. Kimai and solidtime columns describe self-hosting unless marked Cloud; Tempo describes Timesheets Cloud. Free core software does not make hosting or paid add-ons free. Sources and details.

Read the long version — what each of these is actually good at, and when you should pick one of them instead.

Two minutes to your first tracked hour.

Same setup whether it is you alone or a company. Nothing to deploy, nothing to host, no workspace to provision, no card.

1. Sign in with GitHub. Clockoli uses GitHub’s device flow: you approve a one-time code on github.com, so there is no password and no token to paste.
2. Choose a private repository to keep time in. A fresh empty one is fine.
3. Open any page and start the timer. Roughly two minutes, start to finish.

Everything that ships today.

Everything in Clockoli Core is free and open source. No seat or usage limits.

Structured enough to hand to an agent.

Each completed entry is one line of JSON in a monthly file in your repository; the running timer has its own JSON file. Not a blob in someone's database and not a CSV you have to request: a documented schema you can git clone today and query tomorrow. Point a coding agent at the clone and ask it where the quarter went, which tasks ran over, or how many hours to bill this month. It reads the files directly — no API key, no rate limit, no export step.

{
  "schema_version": 1,
  "actor": { "id": "github:12345678", "name": "sergey" },
  "work_item": {
    "kind":  "github_issue",
    "url":   "https://github.com/acme/foo/issues/123",
    "title": "Fix replication failure"
  },
  "activity": {
    "state":      "completed",
    "started_at": "2026-08-26T08:15:00.000Z",
    "ended_at":   "2026-08-26T09:42:00.000Z",
    "local_date": "2026-08-26",
    "timezone":   "Europe/Berlin"
  },
  "description": "Investigated replication failure",
  "metadata": { "billable": true }
}

What you gain, and what you give up.

Clockoli trades SaaS convenience for control. That trade is real and it is not free — here is the whole of it.

What we build next is your call.

These are the things actually on the table. The counts decide the order, and we can tell you when one ships if you want.