One product: issue tracker, Support Desk, ITSM platform, agentic coding layer and MCP server. Grouped below, with a deep dive behind each group. Nothing here is an add-on, a plugin or a higher tier.
Every group below links to its own page. Start here if you already know what you are evaluating.
The primitives. Everything else in Trakr is layered on top of these.
The parts Atlassian sells as a separate product and a shelf of marketplace apps.
What the data tells you, and what an agent can do with it.
Tenancy, identity, migration, operations and the shell your team actually looks at.
Absences worth stating, because each is a decision rather than a gap. If one of these is a hard requirement, you should know now and not in month three.
Yes. Trakr is priced on your organisation's revenue, not on seats or on a feature matrix. SLA, SCIM, multi-tenancy, the Support Desk portal, email-to-ticket, AI, the MCP server and self-hosting are present at every tier. The only thing that changes with price is support response time.
Agentic coding and the internal git server are opt-in and off by default, and an organisation can only enable agentic coding after its tenant has. ITSM and ITIL are organisation switches that default off, and ITIL can only be on while ITSM is. To-do lists, timesheets and the Support Desk are organisation feature flags that default on.
No. Trakr runs on Java and PostgreSQL only, with Flyway-managed schema migrations. Webfonts are self-hosted, so there are no external font requests. AI is optional and can be pointed at a self-hosted OpenAI-compatible runtime such as Ollama, vLLM or LM Studio, in which case no prompt leaves your network and the recorded cost is zero.
TQL covers the same ground — boolean logic, grouping, IS EMPTY, IN, ordering — and adds history operators (WAS, WAS NOT, CHANGED, CHANGED FROM, CHANGED TO), signed relative date math such as -7d, -1q and +3d, a full-text field backed by a GIN index, and live autocomplete on fields and values in one syntax.
Validation returns the position of the error and suggests a field name. A clause is never silently dropped.
Two ways. A built-in Model Context Protocol server at /api/mcp exposes nine tools, five prompts and a set of resources to Claude Desktop, Claude Code, Cursor and other MCP hosts, authenticated by a per-organisation API key whose scope cannot be overridden by a tool argument.
Separately, the agentic coding layer hands a validated ticket to a coding agent — Claude Code, OpenCode, Mistral, Aider, Cline, OpenHands or Moon — which branches, works, pushes and opens a pull request, pausing to ask a human when it hits something it cannot decide.
It disappears rather than greying out. Turning off the Support Desk hides the page, the portal (every portal URL 404s), the project-settings switch, the wizard option, the scope pickers and the keyboard shortcut — and the switch itself refuses to flip while a project is still in Support Desk mode, naming the projects concerned.
All of it, with the exceptions listed under "what Trakr deliberately does not do" and one more stated plainly there: invitations are a stub whose endpoints return placeholders. This page is generated from a feature inventory of the codebase — 2,346 Java files, 132 templates, 120 Flyway migrations and 134 REST controllers — not from a roadmap.
Everything on this page is included at every tier, on your own infrastructure, for an unlimited number of users.