# Nothing Left

> Open-source project tracking for product and engineering teams: issues, sprints and project knowledge your team and AI agents can both use.

Nothing Left is in beta. The hosted service has no subscription charge for teams of any size during beta. The first 20 members of every organisation stay free forever; pricing for additional seats has not been announced, and any future charge will come with advance notice. Each organisation includes 5 GB of platform file storage, with an option to connect its own R2 or S3 bucket.

The code is licensed under AGPL-3.0. Hosted and self-hosted installations use the same build, with no reduced community edition. The repository’s Docker Compose file runs the complete application on one machine, and install guides cover Docker Compose and AWS. There is no setting that turns sign-up off on a self-hosted install.

AI agents connect through the Model Context Protocol (MCP), using personal access tokens constrained by token scopes and the user’s permissions. An agent is optional: the web app also supports the core workflows directly.

## What is included

- Issues with subtasks, links, custom fields and attachments
- Sprints, backlog and boards
- Time tracking against the issue
- Nine reports, each exportable as CSV
- Search, saved views and bulk updates
- A private knowledge base per project
- GitHub and GitLab links on issues, with status automations
- MCP access for AI agents with scoped tokens
- Five built-in roles

## Get started

- [Join the hosted beta](https://work.nothingleft.dev/sign-up)
- [Getting started](https://nothingleft.dev/docs/getting-started.md)
- [Pricing and beta terms](https://nothingleft.dev/pricing.md)
- [Self-hosting](https://nothingleft.dev/solutions/self-hosting.md)
- [Connecting an AI agent](https://nothingleft.dev/docs/mcp.md)
- [Source repository](https://github.com/nothingleft-dev/nothingleft)
- [AGPL-3.0 licence](https://github.com/nothingleft-dev/nothingleft/blob/main/LICENSE)

## Questions about the product

### Do we need an AI agent to use it?

No. It is a complete web app for issues, sprints, time, reports and project knowledge. Agent access is there when you want it, through a token you create and can revoke.

### What happens when we join the beta?

You sign up with Google, GitHub or an email address, name your organisation and create a first project; the key is derived from its initials and you can change it. Inviting people is a step you can skip. You land on the project's issue list, usually within a few minutes. There is no approval queue.

### Can we try it on one project first?

Yes. Create an organisation and a single project, invite people later, connect an agent later or never. Issues export to CSV at any time, so a trial does not lock anything in.

### What stays free?

No subscription charge for any team size during beta. The first 20 members of every organisation stay free forever once billing exists. We will give notice before charging for seats beyond that; nothing is priced today.

[Pricing](https://nothingleft.dev/pricing.md)

### How does file storage work?

Each organisation has 5 GB of platform storage for attachments; avatars do not count. You see usage at 80% and 95% before anything is refused. Connect your own Cloudflare R2 or AWS S3 bucket and the limit lifts the moment the bucket is verified.

[Limits and storage](https://nothingleft.dev/docs/limits-and-billing.md)

### Can we self-host?

Yes. The code is AGPL-3.0 and the hosted service runs the same build: PostgreSQL, S3-compatible storage, the web app, the API and the MCP server. Seat and storage limits are environment settings you can change. One Docker Compose command runs all of it, and a second guide covers AWS.

[Self-hosting guide](https://nothingleft.dev/docs/self-hosting.md)

### Which integrations exist today?

MCP for any agent client, over HTTP or locally over stdio. GitHub and GitLab: branches, commits and pull requests linked to issues by key, with review and CI state on the issue, and status rules that move an issue on a branch, a pull request or a merge. Google and GitHub sign-in. CSV export and generic CSV import.

Not built yet: deployment status on issues, outgoing webhooks, native importers from other trackers, Bitbucket, and general workflow rules beyond those status rules. An agent connected to both your old tracker and this one can help carry issues across, with you reviewing the mapping.

[GitHub and GitLab](https://nothingleft.dev/features/git-integration)

### What is deliberately left out?

A workflow or transition-rules engine: any status may follow any status, and automations only set a status when git work or subtasks move. Custom roles and permission schemes: there are five built-in roles. Per-comment visibility: comments follow the issue. These keep setup short and the agent surface predictable.

---

[Read the web page](https://nothingleft.dev/)
