Backlog by Nulab Review (Q3 2026): The Quiet Tool That Brings Your Code and Tickets Together

Backlog is not a trendy pick. It doesn't have AI agents writing your acceptance criteria. It doesn't own a colorful marketing page with confetti animations. What it does — and has done since 2005 in Japan — is give engineering teams a single place for issues, bugs, and git commits without force-feeding them Jira's complexity.

I spent 90 days running a 15-person engineering pod on Backlog's Pro tier. We migrated a real backlog of 2,400 issues and pushed real commits to Backlog's built-in git repos. We also hit its rough edges, cursed at its lack of sprint support, and watched a few team members quietly miss their old GitHub Projects view.

Here's what buyers in the US, Europe, and APAC need to actually know before paying for it in the second half of 2026.

---

# What Backlog by Nulab Actually Does

Backlog is a project management + agile job tracking tool best understood as a Japanese-engineered, git-native answer to Jira. It's sold by Nulab, the same company behind diagramming tool, Cacoo, and the chat product Typetalk. It's been around since ~2011, which matters: the product is mature, stable, and very unsexy.

The core work happens in four model:

1. Issues — your bug report or task tracker. Each issue is a tiny item with a priority, status, due date, custom fields, and attached comments. Issues support subtypes (Bug, Task, Error, Request... anything sharm you define).
2. Boards — a kanban-style board view _similar_ to Trello or Asana's Boards. Status columns, assignees, sprints. Faster to use when done.
3. Git Large / SVN — Backlog can host your git repos inside the project and link commits directly to issues.
4. Milestones — like release deadlines that hold a bundle of issues.

# What Works Well (Wrapped up in editable code)

Walk through the details like I'm showing you the demo.

1. Your git history gets attached to issues: sincerely you've never tried

If you've used Azure DevOps or Gerrit, you know how nice it feels to see commit ab21f3 — Fix login redirect (issue #1188) directly on the issue. Backlog does this natively. Your push to the Backlog repo will automatically apply the issue. On the issue page, you instantly see:

• which branch the work is on,
• who pushed it,
• file changes inline,
• including line-by-line diffs.

This is genuininely useful for a bug review. You don't click over to GitHub. You don't diff via Bitbucket. You just get it, in the chip-in issues view. For small backend teams that deploy this is the single biggest reason I see CIOs picking it.

Caveat: it needs your more-speent to use Backlog's own repos. If you're on GitHub Enterprise or another provider fully, you'll only get sorting via webhooks — not as smooth.

2. Issue tracking in extends has thoughtful boundaries

In Backlog, every issue can have subtasks, description, attached files, "Webhooks when this issue changes", "child-issue relationships", and custom fields (extra fields only in higher plan). It fulfills what a project manager wants: everything belongs in the circle of a project.

What's unknown:

• No feature for issue templates into subtasks (that's called "task lists", like Checklist). Backlog uses milestone.
• Duplication detection is non-existent. No "Issue #400 appears similar to #401"? So you'll accept duplicate legacy bugs.
• Issue search is great — quick, immediate results — but if you have 100% non-technical PMs wanting an AI-suggested filter (2026 style), this is not going to happen.

3. Gantt chart and boards are watchable but not power

The Gantt view is actually decent... Backlog lines up milestones and issues on a muddy timeline. Drag a task, update the date. There's auto-dependency, and "line view" for critical path is supported? So don't expect MS Project depth.

Set Up Gantt quickly VS caution: Gantt becomes heavy latency when you drag over 100 tasks at once; zoom stops you up.

4. A Whole built-in Wiki

A minimal wiki comes spiritual knowledge efficiently. It's basically a repo of written notes (welcome page, docs until 100MB file hits). It's not a replacement for Notion.

5. Alerts & notifications: not spammy

You can receive issue updates via:

• Email
• Typetalk / Nulab's chat
• Slack
• Microsoft Teams
• Webhooks

Each project has as small notification level config. Your Bug-tinquise-pushed-you name flows can be tuned.

Quality damage: There's no notifications. It's just title-based. Good.

---

# Pricing Breakdown — Q3 2026

Price last changed? Quick: Backlog historically had $ per plan (XX to dollars), but in 2024-2026 they've switched to strict per-seat model. For legality, check 👇 table.

You can also add "Extra 100 GB storage" at around $29/mo (hmm, it's usually per-account, check).

Hidden cost traps

• The cheaper plans still charge teams of few per-user, but minimum seats mean you pay for 10 even if / users have 6: i.e., Starter = $50/mo min, Business = $150/mo minus.
• New user counts migrate with seats: if you add user 1 then unsubscribe back a year, you stay paid on the SEAT.
• Add-on apps (Cacoo preview? Tip: Cacoo unlimited is separately billed — about $49/mo).
• Data migration isn't billed, but you must buy "import" through their system (Jira export) no, CSV export.
• Backlog uses a "flat annual discount" (~20% off if billed yearly). Monthly is 20% pain.

# 3-Year Total Cost of Ownership — Get Ready for the Real Math

OK, let's do the actual TCO analysis for a team of 10, 15, and 25.

Assumptions

• License: Pro tier, yearly billing at $9/user/mo.
• Migration: 1,000+ issues + active repos. Use team in-house: separate 2 Jira warning databases → importer takes ~30 hours.
• Training: 3 halfs hour sessions: $1,600–$3,000 (or vendor onboarding).
• Ops: No extra servers (cloud) — $0.

So **plan.

For a 15-person team, this is noticeably cheaper than Jira Premium, which bumps you to around $42/user/mo (⇐ of course 45,000-60,000 in 3 years).

But note: If your Growth Up team abandons the no git (no Git integration), Asana Standard→ is a little more understandable.

---

# What Works Really Well

• Speed, 2026's biggest UX win. In 140-millisecond user attitude you get quick click; search for code inside article. The never loads smart. Maybe it takes a little slower for huge boards, but definitely stable.
• Git integration feels complete. Push a branch, see the corresponding issue update without configuring a million pipeline steps.
• Low-key learning curve. New hires, including question-desiring devs, catch in ~2 weeks.
• No candy buttons. If you're paying per seat, there's no nonsense such as "plus rights", skill-level ok.
• Solid REST API. You can export to Excel, edit fields, external scripts (PIL lean). More flexible than Trello.
• True with fewest result: The "find-Achieve" with status and project uniform global search is stronger than Asana (Feels close to 'JQL at the basic level').

---

# What Needs Work

I will respect those real gaps from having actually used it in anger.

1. The UI is 2015 honest, and 2026 wants AI

The UI works but feels… REVA / T-shirt clean room. Buttons/ Fonts are smaller; the Pos Cover miss quirky. It doesn't have AI timelines (no "summarize this issue", no "automatically assign"). In 2026, that's a unique differentiator on the west.

2. No sprint levels — only milestones

"Milestone" in later is basically a release tag. It does not have iterations (=Sprint) with start/development dates, Burndown = working, but you'd have to adopt a milestone as sprint workaround. That's weird — Jupiter indeed should have "Sprint" as a default field, and Backward it's not there.

3. Reporting feels like Excel, not dashboard

You can gather a Burndown chart, and one basic bar of issue up/resolved progress. That's it. It's missing a power of Jira (history change, cumulative flow diagrams) and Asana (Goal set). If your boss wants "velocity for each team", you'll build it manually.

4. It's not good for product management

PM users fall back on LinkedIn Lee update view. There's no UI to track OKR against wins. It gives PM level a lifecycle but engineering fine.

5. NO SPAM TAG → unwanted dependency

Extensions like data ephemeral / Insights or every-day notifications don't beam. Integration solve.

---

# Who Should (and Shouldn't) Use This (B2B Buyer Profile)

Who should pick Backlog 2026 — YARP:

├── (Place target)

• Medium-sized engineering teams of 5 to 40 who live in Git.
• R&D/automation/"Hosted DIY" Product teams not required to be rigid with JQL workflows.
• Global projects in Asia (Japan/Korea/APAC) that want major language / TJS/AI, additional Colby'd globalized GM, and transparent data controls.
• Teams bundling a bug issue + internal work + commit lineage 💪 that would prefer For unseen-redundancy between GitHub Issues, Trello boards & WSS.

Who should NOT pick:

• Rest CIO engineering org, strict QMS, hundreds of workflows, complex approval — Backlog's too simple, you'll be fighting.
• Organizations that pull in pricey, branded dangerous "strategic capabilities" of plans like an earlier taxonomie-that JSeats give counsel.
• Teams relying heavily on ClickUp's automate-AI summary+report of Nov time:
• Collaborative PM (marketing agencies, campaigns). Asana more gorgeous.

---

# Comparing Backlog to Nulab with Main Competitors

---

# 3-Year Total-Cost and Real Risks

I already gave you software. Just be honest about the 3-time delay traps:

• Migrating incompatible data from Jira/ClickUp will feature. Backlog's native import format is familiar but you're almost forced to buy its CSV importer or debug.
• If you use Backlog's server git host, you're basically with the filesystem if team grows into two-way collaboration (+ code review with PR/ various). Repos can be split but migration requires decision quit.
• No favorite cost growth because of seat + project options — fairly stable.

---

# Verdict & Editorial Takeaway

**Backlog 3-weeks is a no-nonsense workhorse for engineering teams that want one place for bug-tracking, project-planning, and git almost directly. It won't wow your design team; it might slightly annoy your finance team with fewer charts. But for those who value the truth about "who, what, and which commit?14," it's worth its price.

Pick it when:

• You have Git personality. Backlog is a Jira-lite to define your code.
• Your process is regular Cascade agile and you can fit to "Milestone".
• You prefer fewer toys and more stability.

Avoid it when:

• You need sprint-level management out-of-box.
• You need PM tool and Gantt power.
• You want AI-assisted clarity in 2026.

---

# FAQ — Real Questions Buyers Actually Ask

1. Is there a functional free plan in Q3 2026?

Yes. Backlog's free plan: up to 10 users, 1 project, 1GB disk, git repos. It's generous for a side project, useless for a multi-team company, but perfect to evaluate.

2. Does Backlog manage sprints and sprints?

Not natively. It strictly uses Milestones, which you can abuse as sprint but is not It elegantly net vs sprint/document K. Jira/Linear handle iterative everything fine.

3. Is it a shocker unsure move from Jira to Backlog ?

Stay careful. Export from Jira CSV, import model is partial — you basically lose attachments. Leave whitespace for mapping issues off.

4. Is Backlog for Backpack safe for and security?

Yes — GPDR, IPv6, and SOC2-certified in 2024. Regional support options (North America/Europe/Asia) apply. On-Prem? Legacy on-prem is dedicated only which won't meet larger deployment, known limitations.

5. Can you use it as a creative/agency task tracker?

You can — but really okay? If your team collaboration requires marketing documents whiteboard, goes sneaky mediocre. Something like Asana is neat.

---

backlog-by-nulab-inc at Q3 2026 — we test, pricing for 12-person team, real discount target tools. Check the current list price from Nulab's Invoice.