Compare

For teams that need a tracker, not a workspace for everything.

Nothing Left is for software teams that run on issues, sprints, time on the issue and AI agents. ClickUp is one workspace for many kinds of work. Here is where each one fits, with sources for every claim.

An issue tracker with the pieces product and engineering teams use every day.

The jobs a software team hires a tracker for.

Rows follow the work rather than a feature count: triage, planning, knowledge, the wider workspace, time, reports, automation, agents, hosting and plan. Every ClickUp cell links to ClickUp’s own page, and Nothing Left’s cells link to its manual or terms.

ClickUp column last verified against its own pages on . Product names are trademarks of their owners.

The jobs a software team hires a tracker for. Nothing Left compared with ClickUp, by capability.
CapabilityNothing LeftClickUp
Planning
Issue triageYesIssues with keys, types, priorities, statuses and custom fields. One search language filters lists, boards, reports and agent searches.Search manualYesTasks with custom task types, statuses set per Space, Folder or List, four fixed priority levels and Custom Fields; lists sort, group and filter.ClickUp: custom task types
Agile planningYesSprints, an ordered backlog, boards by status, priority or type, story points and a burndown recorded every night.Sprints manualYesThe Sprints ClickApp adds Sprint Folders and Sprint Points; dashboard cards chart burndown, burnup and velocity.ClickUp: intro to Sprints
Project knowledgeYesA private knowledge base per project: markdown articles in a tree, linked to issues. No public publishing.Knowledge base manualYesDocs with nested pages, live co-editing, comments and links to tasks; a Doc can serve as a wiki.ClickUp: Docs
Cross-functional content: docs, chat, whiteboards, viewsLimitedProject articles, the issue list, backlog, boards and a Gantt report. No chat, whiteboards, calendar, workload or mind-map views.Reports manualYesList, Board, Calendar, Gantt, Timeline, Workload, Table and Mind Map views, plus Chat channels and Whiteboards in the same workspace.ClickUp: intro to views
Delivery
Time logsYesLogged on the issue with a work type, against its estimate, also over a date range; a timesheet and a time report. No running timer.Time tracking manualYesTimers and manual entries, billable flags, weekly timesheets that managers approve, and reports that export to CSV.ClickUp: time tracking
ReportsYesNine reports, from burndown to timesheet, each scoped by a query, readable by an agent and exportable as CSV.Reports manualYesDashboards with cards for sprint burndown, burnup, velocity, cumulative flow, cycle time and lead time.ClickUp: sprint reporting cards
AutomationLimitedStatus rules fired by git events, resolved subtasks and duplicate links, such as Close on merge; not a general rules engine, and no transition rules. Bulk updates handle other repeated edits.Automations manualYesA library of prebuilt trigger-and-action automations, and a builder that drafts one from plain language for you to edit.ClickUp: automations
Agents
MCP serverYesA hosted /mcp endpoint, or a local stdio shim. A scoped personal access token; the tools call the public REST API, acting as you.MCP setup guideYesA hosted remote server with tools for tasks, comments, time tracking, Docs and Chat. Sign-in is OAuth; API tokens are not accepted.ClickUp: MCP tools
AI inside the productNoNo built-in model or agent. Bring the MCP client you already use; it gets ready-made prompts such as a sprint report.MCP tool referenceYesBrain and Super Agents: AI teammates that run multi-step workflows, plus AI search, fields, automations and a meeting notetaker.ClickUp: Super Agents
Hosting and pricing
Self-hostingYesAGPL-3.0 code, the same build as the hosted service, with seat and storage limits as settings. Guides for Docker Compose and AWS.Self-hosting guideNoA cloud service hosted on AWS. Enterprise plans can choose a data region; no self-hosted edition is offered.ClickUp: data hosting
Source codeYesOpen source under AGPL-3.0, the same code as the hosted service.AGPL-3.0 licenceNoProprietary. The terms grant a licence to use the service, not its source.ClickUp: terms
PlanYesBeta: no subscription for any team size. The first 20 members stay free when billing arrives.Limits and billingYesA Free Forever plan and paid tiers. Prices change; read them on its own page.ClickUp: pricing
Yes
Built in and documented.
Limited
Present, with a narrower scope than the row suggests; the note says how.
Planned
Not available today; on the public roadmap or announced.
No
Not available.

A developer’s Monday, in four steps.

5 Oct 2026 at Acme, the first working day of Sprint 08. Filter the bugs, plan the next sprint, log the work, then ask an agent where things stand. Every screen is drawn from the same fictional project. Pick a step to see it.

1 / 4Alex Lee filters the bugs · 5 Oct 2026, 9:15am

Acme/ACME/Issues

type: Bug #Unresolved8 issues

  • ACME-7Burndown ignores late additionsCriticalUnassignedOpen
  • ACME-5Accept invite while signed inMajorAlex LeeOpen
  • ACME-9Upload stalls at 100% on slow linksMajorUnassignedOpen
  • ACME-12Invite link blank after it expiresMajorAlex LeeOpen
  • ACME-2Password hint is cut off on small screensNormalJordanOpen
  • ACME-8Saved view count is staleNormalSam OrtizReopened
  • ACME-11Swimlane header overlaps countNormalCasey KimIn Progress
  • ACME-13Invite expiry date shown in UTCMinorCasey KimOpen

The same query works in the board filter, a report’s scope and the agent’s search_issues tool. Save it as a view and the whole team can open it by name.

2 / 4The team plans Sprint 09 · 5 Oct 2026, 4:00pm

ACME/Backlog

Sprint 08Running11 issues, 34 points · ends 17 Oct 2026

Sprint 09Planned19 Oct – 30 Oct 2026 · 4 issues, 11 points

Members can manage invitations without asking an admin

  • ACME-16Reminder email before an invite expires3 pts
  • ACME-17Show who invited each member2 pts
  • ACME-18Revoke a pending invitation5 pts
  • ACME-19Invite form explains each role1 pt

BacklogIssues in no sprint

  • ACME-3Make invitations clearerNot estimated
  • ACME-7Burndown ignores late additionsNot estimated
  • ACME-8Saved view count is stale2 pts

4 more issues

A Project Admin creates the sprint with its goal and dates; anyone who can edit issues drags them in and orders them. The board shows cards in the same order.

3 / 4Alex Lee logs the work · 5 Oct 2026, 5:05pm

ACME/Issues/ACME-10
FeatureNormal

Invite landing shows the inviter

Add spent time

Date
5 Oct 2026
Time spent
1h 30m
Type
Development
Assignee
Alex Lee
Status
In Progress
Sprint
Sprint 08
Spent time
1h 30m of 5h

Alex Lee logged 1h 30m, Development5:05pm

4 / 4Alex’s agent reads the sprint · 5 Oct 2026, 5:30pm

Your agentconnected as @alex

How is Sprint 08 going, and is anything outside it that should worry us?

  • get_sprintproject: "ACME", sprint: "Sprint 08"
  • search_issuestype: Bug #Unresolved sprint: {No sprint} severity: Critical, High

Sprint 08, “Make invitations clearer”, ends 17 Oct 2026. It started yesterday evening with 31 points; 3 points were added after the start (ACME-9 and ACME-13), so 0 of 34 points are resolved so far.

9 Open, 2 In Progress. In progress: ACME-11 (Casey Kim), ACME-10 (Alex Lee).

Outside the sprint, in the backlog:

  • ACME-7 Burndown ignores late additions, Critical, Open, unassigned
  • ACME-8 Saved view count is stale, Normal, Reopened, Sam Ortiz
  • ACME-20 Members list stops at 50 people, Normal, Open, unassigned

Both calls only read. Had Alex asked for a change, it would be made as @alex, within Alex’s role and token.

Hand-drawn product views with fictional data.

Where ClickUp covers more ground.

ClickUp is built as one workspace for many kinds of work, and its range is real. Nothing Left is narrower on purpose. If your team uses the pieces below every day, a focused tracker will not replace them.

  • Views

    ClickUp
    List, Board, Calendar, Gantt, Timeline, Workload, Table and Mind Map views over the same tasks.
    Nothing Left
    The issue list, backlog and boards, with a Gantt report. No calendar, workload or mind-map views.
    ClickUp: Intro to views
  • Docs and wiki

    ClickUp
    Docs with nested pages and live co-editing, for any team in the workspace.
    Nothing Left
    A private knowledge base inside each project, for runbooks and decisions next to the issues.
    ClickUp: Docs
  • Chat

    ClickUp
    Channels, direct messages and threads, with a message turned into a task in one step.
    Nothing Left
    Comments on issues and articles only. Keep the chat tool you have.
    ClickUp: Chat
  • Whiteboards

    ClickUp
    A shared canvas whose shapes become tasks, with live tasks and Docs embedded.
    Nothing Left
    None. Sketch elsewhere and link the issue.
    ClickUp: Whiteboards
  • Automation

    ClickUp
    Prebuilt trigger-and-action automations, and a builder that drafts new ones from plain language.
    Nothing Left
    Status rules only, fired by git events, resolved subtasks and duplicate links. Any status may follow any status, and bulk updates cover other repetitive edits.
    ClickUp: Automations
  • Agents and MCP

    ClickUp
    Super Agents inside the product, and a hosted MCP server for outside assistants.
    Nothing Left
    An MCP surface only: your own agent, a scoped token, the same rules as the web app.
    ClickUp: MCP tools

Which one fits your team.

Breadth suits some teams and gets in the way of others. The question is how much of the workspace your team would actually use.

Choose ClickUp if

  • Several departments, not only product and engineering, plan their work in one workspace.
  • People need many ways to see the same work: calendar, workload, timeline, mind map, table.
  • You want chat, whiteboards and company-wide docs next to the tasks rather than in separate tools.
  • You rely on general trigger-and-action automations or AI agents that run inside the tracker.
  • Timesheet approval and billable time are part of how you work.

Choose Nothing Left if

  • Your team ships software and mostly needs issues, sprints, time on the issue and project notes.
  • You want a short setup: lists of statuses, priorities and types, five fixed roles, no general rules engine.
  • Your agent should work through a documented API with a scoped token, as the person who connected it.
  • Open source matters, or you may want to run the same build on your own infrastructure.

Nothing Left for engineering teams

Looking for a self-hosted ClickUp alternative?

ClickUp runs as a cloud service on AWS, and Enterprise plans can choose the region their data is stored in. Nothing Left gives you two separate routes: the hosted beta, or the same open-source build on infrastructure you run.

ClickUp: data hosting

We run it

Hosted beta

Sign up and file the first issue; nothing to install. Upgrades, backups and email are ours.

You can keep attachments in your own Cloudflare R2 or AWS S3 bucket. That is not self-hosting: issues, comments and accounts stay in our database.

You run it

Self-hosted, AGPL-3.0

The same codebase and build as the hosted service, with no reduced edition. The seat and storage limits become settings you choose. The work that comes with it is yours:

  • Run the web app and the API, which also serves /mcp, as long-running processes.
  • Provide PostgreSQL, Redis and two buckets on an S3-compatible store.
  • Pull each release, run its migrations and restart.
  • Back up the database and both buckets.
  • Choose a mail provider (Resend, Zoho CPaaS or SMTP), and register your own OAuth apps for Google and GitHub sign-in.

Install guides for Docker Compose and AWS.

Moving your work across.

There is no ClickUp importer. There are two routes: a generic CSV import that works for any source, and an agent-assisted path for teams whose agent can reach both products. Both end with you reviewing the result.

Bulk

CSV import

  1. Start from a CSV of the tasks you are moving.
  2. Map its columns to issue fields in the project you import into.
  3. Read the rows that could not be imported, with the reason for each, and fix them.
  4. Import. The result is ordinary issues you can search, plan and export again.

When your agent reaches both

Agent-assisted, with review

  1. Connect one agent to ClickUp’s MCP server and to Nothing Left’s.
  2. Ask it to read the unresolved tasks and propose a mapping before it creates anything.
  3. Check the mapping, duplicates, attachments, history and who each person becomes.
  4. Approve. It creates projects, tags and issues and invites members through the MCP tools, as you, within your token’s scopes.

Read the unresolved tasks in our ClickUp list “Web app”. Propose how each one maps to an issue in the ACME project: type, status, priority, assignee and tags. List likely duplicates. Create nothing until I approve the mapping.

What your ClickUp bill becomes during beta.

ClickUp is selected, starting from its lowest paid plan. Replace that with what you pay now and see what the beta takes off it. Check ClickUp’s current prices on its own page; nothing you type leaves this page.

The calculator is not available in this browser right now. Reloading the page may bring it back. The short version: during beta the subscription is zero, whatever you pay today.

Currently using

Check your plan on ClickUp's pricing page

Currency

You know

members

Digits only, such as 1250, 1,250.50 or 1.250,50.

Filled in from ClickUp's lowest paid plan: US list price, billed monthly, checked 11 Oct 2026. Higher plans cost more, and annual or volume pricing differs. Replace it with your invoice figure.

Current subscription spend
-
Nothing Left subscription during beta
$0
Illustrative subscription spend avoided during beta if you replace and cancel the current plan
-

Enter what you pay today to see the comparison.

Monthly subscription only, in the currency you chose, with no exchange conversion. Filled-in prices are US list prices for each tool's lowest paid plan, billed monthly, checked 11 Oct 2026; they apply in USD only. Migration effort, add-ons, storage and any future seat pricing are outside this comparison. Product names are trademarks of their owners.

Questions from teams leaving ClickUp.

Docs, time, agents and what a focused tracker leaves out. Short answers here, the rest in the manual.

Does Nothing Left have docs like ClickUp Docs?

It has a knowledge base inside each project: markdown articles in a tree, up to three levels deep, linked to the issues they explain and readable by an agent. Drafts are private until published, and only the project’s members can read them.

It is not a company-wide wiki and has no public publishing. If several departments write together in ClickUp Docs today, keep a docs tool for that and use the project knowledge base for runbooks and decisions. Knowledge base manual

Can we track time the way we do in ClickUp?

You log time on the issue with a duration, a date or a date range, and a work type. The issue shows spent time against its estimate, an epic adds up its subtasks, and the timesheet and time report export to CSV.

There is no running timer and no timesheet approval; ClickUp has both. A project can add its own attributes to each time entry, such as Billable, but a team that invoices from approved timesheets should check that gap first. Time tracking manual

ClickUp has AI agents and an MCP server. What is different here?

ClickUp runs AI inside the product, including Super Agents, and offers a hosted MCP server that assistants sign in to with OAuth. Nothing Left has no built-in model. It gives the agent you already use an MCP surface with a personal access token that you scope and can revoke.

Every tool calls the same public REST API as the web app, so an agent cannot do anything the API does not allow, and its changes appear under your name. Clients that only accept OAuth connectors cannot connect yet. Connect an agent

What would we give up by moving from ClickUp?

Chat, whiteboards, forms, general rule-based automations, in-product AI, and calendar, workload, timeline and mind-map views. Nothing Left does not try to replace those. It also has no native importer from ClickUp.

What it keeps in one place is the engineering loop: issues, sprints, boards, time on the issue, reports and project notes, with the same capabilities available to an agent.

Can we bring our ClickUp tasks across?

The dependable route is a generic CSV import: you map the columns, review the rows it could not read and import. There is no ClickUp importer.

If your agent can reach both ClickUp’s MCP server and Nothing Left’s, it can read your unresolved tasks and recreate them as issues with tags and assignees. That is a guided migration, not a one-click transfer: you check the field mapping, duplicates, attachments and who each person becomes before it runs.

Put one sprint through it.

Join the beta, create a project and run your next sprint in it. If it fits, bring the rest of the work across; if your team needs the whole workspace, you will know quickly.