How Kard compares — honestly.

Most comparison pages exist to make the competition look bad. This one doesn’t. Codecks, HacknPlan, Jira, Linear, Notion, and Obsidian are all good tools, and for a lot of teams one of them is the right answer. Kard is built for a narrow, specific job — planning work inside Unreal Engine — and it’s the best tool in the world at that job and a poor fit for several others. Here’s the honest version, so you can decide quickly.

What Kard is for — and what it isn’t

Kard is for solo developers and small teams building in Unreal Engine, especially ones working alongside an AI assistant. It lives in the editor, stores your plan as assets in your own project, and understands what a level, an actor, a Blueprint, and an asset actually are.

It is not built for large studios. There’s no cross-team portfolio reporting, no real-time multi-user sync yet, no mobile app, and it only runs on Windows inside Unreal. If you’re a sixty-person studio with producers who never open the editor, you want Jira, and we’ll happily say so.

Where Kard is genuinely unmatched

Nothing else on this list can do these, because nothing else runs where the work happens:

• It’s in the editor. You never alt-tab to a browser to check the plan. The plan is a panel in Unreal.
• It speaks Unreal. Tasks, notes, and pages can be pinned to a spot in the level — an actor, a class, a point in the world — and you fly the camera straight to them. A task can link to the actual asset, Blueprint node, or line of code it’s about, so nobody writes a bug report with screenshots and coordinates. They just click through to the thing.
• It captures work you’d otherwise lose. Kard scans your C++ and Blueprint comments for TODO / FIXME / HACK, and turns Unreal’s Message Log warnings into tasks already linked to the asset that raised them.
• It’s native, not a web app. Written in C++ and Slate, it runs at editor speed — no browser tab, no loading spinner.
• Your plan lives in your repo. Every card is a .uasset in your project, versioned with Perforce or Git alongside everything else. Local-first by default; no account, no server.

The comparison at a glance

Capability	Kard	Codecks	HacknPlan	Jira	Linear	Obsidian	Notion
Runs inside the Unreal Editor	Yes	No	No	No	No	No	No
Understands Unreal assets & Blueprints	Yes	No	No	No	No	No	No
Pin tasks/notes in the 3D viewport	Yes	No	No	No	No	No	No
Link a task to an exact asset or location	Yes	No	No	No	No	No	No
Auto-capture code TODOs & editor warnings	Yes	No	No	No	No	No	No
Built for game developers	Yes	Yes	Yes	No	No	No	No
Perforce integration	Yes	No	No	Add-on	No	No	No
Git integration	Yes	Partial	No	Yes	Yes	Plugin	Partial
Data stored locally, in your repo	Yes	No	No	Self-host	No	Yes	No
Native app speed (C++/Slate)	Yes	No (web)	No (web)	No (web)	No (web)	Yes	No (web)
Real-time multi-user sync	Via VCS	Yes	Yes	Yes	Yes	Paid	Yes
Enterprise reporting & portfolio	No	Partial	Partial	Yes	Partial	No	Partial
Runs outside Unreal / on mobile	No	Yes	Yes	Yes	Yes	Yes	Yes

The pattern is the whole story: Kard wins every row that’s about Unreal, and loses every row that’s about scale and reach. Codecks and HacknPlan share Kard’s audience — they’re built for game developers too — but not its home: they plan the game from a browser, while Kard plans it from inside the engine.

Kard vs Codecks

Codecks is the closest tool here to Kard’s world: a project-management tool built specifically for game developers, with a card-based (“decks of cards”) workflow and a standout Discord integration that turns community bug reports and feedback straight into cards. For an indie studio that wants a polished, game-focused tracker in the cloud, it’s a genuinely good pick — and if your project isn’t in Unreal, it may be the better one.

Where the two part ways is where they live. Codecks organizes the work about your game from a browser tab; it doesn’t run inside the engine, and it can’t link a task to an actor or a Blueprint. Kard’s bet is that for Unreal work, the tracker belongs in the editor, next to the thing it describes.

Choose Codecks if you want a game-focused, cross-platform tracker with strong community and Discord features, and you’re happy for it to live outside the engine.

Kard vs HacknPlan

HacknPlan is another tracker built for game developers, best known for pairing task boards with a Game Design Document module — so your planning stays tied to the design it serves. For a small team that wants their design doc and their board in one place, it’s a thoughtful, game-aware option.

Like Codecks, though, it lives in the browser and knows nothing about your engine. It plans the game from the outside; Kard plans it from within Unreal, where a task can point at the actual level or asset it’s about.

Choose HacknPlan if you want a game-focused planner that keeps your design document and tasks together, and you don’t need it inside the engine.

Kard vs Jira

Jira is the most capable project-management tool on this list, full stop. For a large studio it’s genuinely hard to beat — configurable workflows, sprints and story points, roadmaps and portfolio views, dashboards, granular permissions, and a marketplace of thousands of integrations. If you have multiple teams, producers, and a QA department that all need one system of record, Jira was built for exactly that.

What Jira can’t do is stand inside your engine. It doesn’t know what a level or a Blueprint is; a task about “the collision on the far crates” is just text, and someone still has to go find the crates. Kard’s whole premise is to close that gap.

Choose Jira if you’re a mid-to-large studio that needs cross-team reporting, portfolio management, and a mature agile process. Big teams should still use Jira — Kard won’t serve you there.

Kard vs Linear

Linear is, by a distance, the best-designed issue tracker for software teams. It’s fast, it’s opinionated in the right ways, and its cycles-and-triage model with deep GitHub and GitLab integration makes it a pleasure for a product-engineering team shipping code.

But Linear’s world is code and pull requests on Git. An Unreal project is levels, Blueprints, and multi-gigabyte binary assets, usually living in Perforce — and Linear has no awareness of any of that, and no Perforce integration. It’s a superb tool aimed at a workflow that isn’t quite yours.

Choose Linear if you’re primarily a software team living in a Git/PR workflow. If your project is levels and assets in Perforce, its strengths don’t land on your work.

Kard vs Notion

Notion is the most flexible tool here. As a company wiki, a docs hub, or a lightweight database it’s excellent; its templates are best-in-class, and its apps are polished on every platform. Plenty of studios rightly run their whole knowledge base on it.

The trade-offs are that Notion lives in the cloud — your data on their servers — and knows nothing about your engine. It’s a great home for the studio’s general docs; it’s not where you plan work tied to a specific asset or a spot in a level.

Choose Notion if you want a flexible, cross-team wiki and docs hub across the whole studio, not just the part that happens inside Unreal.

Kard vs Obsidian

Obsidian shares Kard’s core belief: your data should be plain files on your own machine, not someone else’s server. As a personal knowledge base it’s superb — local Markdown, a massive plugin ecosystem, and it runs everywhere, including mobile.

Where it differs is purpose. Obsidian is a note-taking and knowledge tool, not a task tracker for a team, and it has no idea what an actor or a Blueprint is. Kard takes the same local-first philosophy and applies it to project management inside the engine.

Choose Obsidian if you want a general-purpose, cross-platform personal knowledge base. If you specifically want tasks and notes that live in your Unreal project, that’s Kard.

So — should you use Kard?

Choose Kard if:

• You build in Unreal Engine 5.8 on Windows and want your plan to live where you work.
• You’re a solo developer or a small team, especially one working with an AI assistant.
• Your project is in Perforce or Git and you want tasks versioned alongside it.
• You’d rather link a task to the actual asset or spot in the level than write a report about it.

Choose something else if:

• You want a game-focused cloud tracker with strong community and Discord features — Codecks.
• You want your task board tied to a living game-design document — HacknPlan.
• You’re a large studio needing portfolio management and enterprise reporting — Jira.
• You’re primarily a software team on a Git and pull-request workflow — Linear.
• You want a flexible, studio-wide wiki and docs hub — Notion.
• You want a general, cross-platform personal knowledge base — Obsidian.
• You need real-time multi-user sync, a mobile app, or access for people who never open Unreal — Kard isn’t there yet.

If you’re still reading and you build in Unreal, you’re probably exactly who Kard is for.