Self-hosted Getting Things Done, honestly reviewed. Stripped of methodology marketing, here’s what you actually get.

TL;DR

What it is: A web-based Getting Things Done (GTD) task manager built on Ruby on Rails, self-hostable on any server where Ruby runs [1].
Who it’s for: GTD practitioners who want their trusted system running on their own hardware, not locked inside a SaaS subscription. Technical users comfortable with Ruby/Rails deployment.
Cost savings: Todoist, Things 3, and OmniFocus charge $3–$100/year per seat. Tracks is free under GPL-2.0 — the cost is a VPS and setup time [1][2].
Key strength: Pure GTD implementation. Contexts, projects, ticklers, someday/maybe — the full Allen methodology is first-class, not bolted on [1].
Key weakness: This is old software. The Ruby on Rails deployment story is significantly more involved than modern Docker-native alternatives. The star count (1,225 on GitHub) tells you this is niche and lightly maintained [2].

What is Tracks

Tracks is a web application built to implement David Allen’s Getting Things Done methodology. Full stop. It doesn’t try to be a Jira clone with a GTD skin, or a Notion alternative with an “inbox” feature. The entire data model is organized around GTD primitives: next actions, contexts, projects, and the concept of trusted capture [1].

The project was started by a developer known as “bsag” and is currently maintained by Jyri-Petteri “ZeiP” Paloposki, sponsored by Ardcoras oy, a Finnish consulting firm. The principal maintainer also runs a hosted version called taskitin.fi, which is the only managed deployment of Tracks available [2]. There is no venture-backed company behind this, no Series A, no “AI-powered” rebrand. It’s a small open-source project run by one principal maintainer with community contributors.

The current version is 2.7.1. The license is GPL-2.0. It runs on Mac OS X, Windows, and Linux [1].

That context matters because it sets expectations correctly. Tracks isn’t competing with Linear or Asana. It’s competing with the dedicated GTD-methodology tools: OmniFocus, Things 3, Nirvana, Toodledo. The self-hosted angle is the differentiator — your task data lives on your hardware, not on someone else’s server.

Why people choose it

Independent reviews of Tracks are sparse. The project has 1,225 GitHub stars and a mailing list on Google Groups — it’s not a community generating hot takes on HackerNews every week [2]. What we have is the official documentation, the GitHub history, and the clear picture that emerges from the feature list.

The people who choose Tracks tend to be one of two profiles. The first is someone who read Getting Things Done seriously, built their system around contexts and projects, and wants software that matches the methodology rather than approximating it. The second is a self-hoster with a philosophical objection to trusting task data to a third-party SaaS — the GTD practitioner who wants their “trusted system” to actually be something they own.

Tracks makes a credible case to both groups. It’s one of the oldest GTD-specific web apps still maintained, which means the feature set isn’t shaped by a product manager trying to hit growth metrics — it’s shaped by people who actually use GTD [1][2].

What it doesn’t have is a marketing department. The homepage says “Tracks is a web-based application to help you implement David Allen’s Getting Things Done™ methodology.” That’s the entire pitch [1]. If you don’t know what GTD is, Tracks is not for you.

Features: what it actually does

Core GTD structure:

Actions organized by context — you see actions grouped by where/what you need to do them (office, phone, computer, errands) [1]
Projects with attached notes, status flags (active, hidden, completed) [1]
Hiding projects and contexts — the “someday/maybe” context works exactly as Allen describes: hidden from the daily view but still captured [1]
Default context per project — saves constant re-entry when most actions in a project happen in the same context [1]
Drag-and-drop reordering of contexts and projects [1]

Capture and review:

Ajax-based quick-add from the main page — no page reload [1]
Autocomplete for existing project and context names [1]
Tickler system — schedule actions to appear on the home page after a future date; this is the GTD “tickler file” concept implemented correctly [1]
Due dates with color-coded urgency (overdue = red, tomorrow = dark orange, within 7 days = orange, further out = green) [1]
Starred actions for quick priority flagging [1]
Tags as a cross-cutting organizational layer alongside contexts and projects [1]

Review and reporting:

Statistics page: average time to completion, actions completed by month/year, productivity patterns by day of week [1]
Completed items page (separate from main view, configurable visibility on home page) [1]
RSS feeds for next actions, due items, and completed actions [1]
iCal feeds for calendar integration [1]
Data export in YAML, CSV, and XML formats [1]

Multi-user and access:

Multi-user with per-user data isolation [1]
Admin user creates and manages accounts; non-admins can’t self-register [1]
Login-protected instance [1]

Developer/integration:

REST API for scripting and third-party integration [1]
Translation support via Hosted Weblate (multiple languages) [2]
Mobile-friendly lightweight interface for browser-based phone access [1]

What’s missing from this feature list is anything that’s not GTD. There’s no Kanban board, no timeline view, no embedded documents, no comments on tasks, no @mentions, no integrations with Slack or GitHub. That’s not an oversight — it’s the point. Tracks is narrow by design.

Pricing: SaaS vs self-hosted math

Tracks self-hosted:

Software: $0 (GPL-2.0) [2]
VPS: $5–10/month (Hetzner, Contabo, DigitalOcean)
Tracks is a Ruby on Rails application — you’ll need Ruby, Rails, a database (SQLite or MySQL/PostgreSQL), and Rack/Puma serving it, or the built-in webserver for local use [1]

taskitin.fi (the maintainer’s hosted version):

Pricing not published in the available data. If you want managed hosting, this is the only officially endorsed option [2]. Check the site directly.

What you’d pay for alternatives:

Todoist: $4/mo (Pro), $6/mo (Business per user)
Things 3: $49.99 one-time purchase per platform (iOS, Mac, iPad sold separately)
OmniFocus: $9.99/mo or $99.99/year (Pro)
Nirvana HQ: $5/mo
Toodledo: $3.99/mo

For a solo GTD practitioner, self-hosting Tracks on a $6/month VPS saves roughly $50–$120/year versus paid GTD apps. Across two or three users on the same instance, the math improves further — the VPS cost doesn’t multiply per seat [1].

The catch is Ruby on Rails deployment. This isn’t a “pull the Docker image and done” situation (though containerized deployments exist in the community). If you’re not comfortable with Ruby environments, budget for either the learning curve or professional deployment help.

Deployment reality check

This is where Tracks asks more from you than most modern self-hosted tools.

What you need:

A Linux VPS or server
Ruby runtime (version matching what Tracks requires — check the repo’s .ruby-version)
A database: SQLite works for personal use; MySQL or PostgreSQL for multi-user [1]
A web server: Puma (built in) for simple setups, nginx or Apache as a reverse proxy for production
Optional but recommended: SSL certificate via Let’s Encrypt, domain name

What makes this harder than, say, a Docker-native tool:

Ruby version management (rbenv/rvm) adds a layer compared to just running a container image
Gem dependency installation via Bundler
Database migrations when upgrading versions
No official Docker image in the primary repository (community images exist but aren’t the canonical deployment path)

The README links to the wiki for full installation instructions and upgrade paths [2]. The wiki is where the real deployment documentation lives — not in the README itself. If you’re upgrading from an older version, read the migration notes carefully; the project explicitly warns about this [2].

Who actually has a smooth time:

Developers with Ruby experience
Sysadmins comfortable with Rails apps
Anyone who’s deployed a Heroku-style app before

Who will struggle:

Non-technical founders unfamiliar with Ruby environments
Anyone expecting a docker-compose up experience

The built-in webserver option means you can run Tracks on your local machine as a personal GTD system without a VPS at all [1]. For personal use, that’s actually the lowest-friction path — run it locally, access it via browser, skip the server setup entirely.

Pros and cons

Pros

Genuine GTD implementation. Contexts, projects, tickler, someday/maybe, starred actions — these map directly to Allen’s methodology without compromise [1].
GPL-2.0 license. Your data, your code, your server. The license doesn’t expire, doesn’t change pricing, doesn’t get acquired [2].
Multi-user without per-seat pricing. Add five users to your family or small team, pay nothing extra [1].
Data portability. Export everything in YAML, CSV, or XML at any time. No vendor lock-in at the data layer [1].
Statistics that matter for GTD. Productivity patterns, completion rates, average time-to-done — useful for the weekly review [1].
iCal and RSS feeds. Integrate your action list into a calendar or feed reader without building a custom integration [1].
REST API. Script your way in and out of Tracks — shell scripts, Ruby scripts, mobile shortcuts [1].
Actively maintained (if modestly). The CI badge is green, Weblate translations are ongoing, and the maintainer is reachable [2].

Cons

Ruby on Rails deployment complexity. Not insurmountable, but meaningfully harder than Docker-native alternatives [1][2].
Modest community. 1,225 GitHub stars and a Google Groups mailing list. If you hit an unusual bug, the support surface is small [2].
No mobile app. Browser-only, including a mobile-optimized web interface. Works, but it’s not native [1].
UI shows its age. The interface has been refined over years but the design language predates modern design systems. Functional, not beautiful.
No integrations with modern productivity tools. No Slack, no GitHub, no email-to-task by default. The REST API is your extension point [1].
Single maintainer risk. One principal maintainer, sponsored by a small Finnish firm. If that arrangement ends, the project’s future is uncertain [2].
No team collaboration features. Tracks is multi-user in the sense that multiple people have separate accounts on one instance — not in the sense of shared projects, task assignment, or comments [1].
Limited third-party ecosystem. No browser extensions, no official integrations, no community plugin marketplace.

Who should use this / who shouldn’t

Use Tracks if:

You run your life on GTD and want software that takes the methodology seriously rather than treating it as a feature checkbox.
You’re comfortable with or willing to learn Ruby on Rails deployment, or you’ll pay someone to set it up once.
You want task data on your own hardware with no third-party access.
You need multi-user GTD for a household or small team without paying per seat.
You want a system you can script — the REST API makes automation straightforward [1].

Consider taskitin.fi instead if:

You want Tracks without managing a server — the maintainer runs a hosted version [2].

Skip it (use Todoist or Things 3) if:

You’re not deeply committed to GTD as a methodology. Both are easier to use and have better mobile apps.
You need collaborators to assign, comment on, or share tasks.
You want native iOS/Android apps.
You’re not technical and have no one to help with deployment.

Skip it (use Vikunja or Planka) if:

You want a modern, Docker-native self-hosted task manager with a current UI.
Team features (assignments, comments, boards) matter more than GTD fidelity.

Skip it (use OmniFocus) if:

You’re on Apple ecosystem exclusively and willing to pay. OmniFocus has a deeper GTD feature set, a polished native app, and better integration with Apple platforms — at the cost of pricing and vendor lock-in.

Alternatives worth considering

GTD-specific alternatives:

OmniFocus — The GTD gold standard on Apple platforms. Expensive ($99.99/year Pro), closed source, no self-hosting. Feature depth that Tracks doesn’t match [general knowledge].
Nirvana HQ — Clean GTD SaaS at $5/month. No self-hosting option [general knowledge].
Toodledo — Flexible GTD-adjacent tool at $3.99/month. Long-running, slightly dated UI [general knowledge].

Self-hosted task managers (not GTD-pure):

Vikunja — Modern self-hosted task manager with Docker-native deployment, kanban and list views, clean UI. Less GTD-specific but actively developed [general knowledge].
Wekan — Kanban-focused, not GTD. Docker-native deployment [general knowledge].
Planka — Simple Trello clone for teams. No GTD structure [general knowledge].

The honest trade-off: If GTD fidelity is your requirement, Tracks has no peer in the self-hosted space — there simply aren’t other maintained GTD-specific self-hosted options. If GTD is a preference rather than a hard requirement, Vikunja gives you a much smoother deployment experience and a more current UI.

Bottom line

Tracks earns its place by doing one thing right that no modern alternative bothers to do: implementing GTD as David Allen actually described it, on infrastructure you control. The tickler file works. Someday/Maybe works. Context-based views work. The REST API and data export mean you’re never locked in. For a GTD practitioner who self-hosts their infrastructure and wants their trusted system to actually be trusted — meaning it’s on their server, under their control — Tracks makes a credible case.

The honest caveat is that this is a Ruby on Rails application from the pre-Docker era, maintained by one person. If you’re a non-technical founder hoping to replace Todoist with minimal setup friction, Tracks is the wrong choice. But if you’re willing to invest an afternoon getting the server configured — or to pay someone to do it once — you end up with a zero-recurring-cost GTD system that will keep working for as long as you maintain the VPS. That’s a different kind of value than the SaaS alternatives offer, and it’s exactly the kind of value that justifies self-hosting in the first place.

Sources

Tracks Official Website — https://www.getontracks.org/ — Feature descriptions, methodology overview, version 2.7.1 documentation.
Tracks GitHub Repository (TracksApp/tracks) — https://github.com/tracksapp/tracks — README, license (GPL-2.0), maintainer information, contributor list, CI status, 1,225 stars.
taskitin.fi — https://www.taskitin.fi/ — Hosted Tracks service run by the principal maintainer, mentioned in GitHub README.