Trakr: Built for Billions. Simple for Everyone.

Hey everyone! 👋 I'm Tim, the founder of Automatize and I created Trakr — and like most tools born out of frustration, this one started with a very specific moment. I was sitting in a meeting where we spent 40 minutes debating whether something was a 'Spike', "story" or a "task" in Microsoft DevOps. Forty. Minutes. Meanwhile, the actual actual topic is forgotten about. That was the moment I thought: "We've overcomplicated this so badly that the tool designed to help us is the reason we're not able to deliver." I've spent 10+ years building software for companies of all sizes — from scrappy startups to regulated enterprises. And everywhere I went, I saw the same pattern: teams either used bloated tools they hated and barely understood, or they duct-taped together Trello boards, spreadsheets, and Slack channels, or bloated Jira and hoped nothing fell through the cracks. There was nothing in between. Nothing that said: "Here's a professional, powerful issue tracker that respects your time and trusts you to know how to do your job." So I built Trakr. The philosophy is simple: zero ceremony, full power. No mandatory workflows. No sprint rituals baked into the UI. No gamification of your productivity. You open it, you see your tickets, you get to work. If you need advanced stuff — SLA management, a public helpdesk portal, a full query language, multi-tenant workspaces, AI triage — it's all there. But it never forces itself on you. A few things I'm particularly proud of: -TQL (Trakr Query Language) — I wanted search to feel like a superpower, not a filter dropdown. You can query your entire workspace with expressions like priority:high assignee:me sla.breached:false updated:>7d. It sounds nerdy, but once you use it, you can't go back to clicking through filter menus. - Built-in helpdesk — Most teams run an issue tracker AND a separate support tool AND some kind of bridge between them. Trakr has a public-facing portal built right in. Your customers submit tickets, your team sees them alongside internal issues. One tool, one source of truth. - Self-hostable, no nonsense — It's Spring Boot + PostgreSQL. No Redis, no Elasticsearch, no Kafka, no constellation of microservices you need a PhD to deploy. One JAR file, one database. Put it on your own server and own your data completely. We'll never hold your information hostage — full export, anytime, no questions asked. - Data import — Because I know exactly how painful it feels to be locked into a tool you've outgrown. One click and your projects, tickets, comments, and attachments come over. Life's too short for manual migration spreadsheets. I built this in Belgium, bootstrapped, with zero outside funding. No growth-at-all-costs pressure. No VC telling me to add "engagement features" or lock down the export button. Just a product that tries to be genuinely good at what it does. Trakr isn't trying to be everything for everyone. It's not a project management suite. It's not a Notion competitor. It's not trying to reinvent how humans collaborate. It's an issue tracker and a support desk — and it tries to be the best, most respectful version of that. Thanks for checking it out — and thanks to this community for always being the best place to launch something you've poured your heart into. It means a lot. 🙏 — Tim