For startups and growing teams
Start with work, not settings.
Sign up, name your organisation and create a first project, and you are looking at its issue list. Statuses, priorities, types and a board are already in place, so the team files real work today and adds sprints, time and reports when it needs them.
Beta terms
- No subscription charge during beta
- Your first 20 members stay free forever
- 5 GB of storage per organisation, or your own R2 or S3 bucket
A tracker you can start using before you have a process to configure.
Onboarding asks for two names: your organisation and a first project. The project is the one step you cannot skip, because an organisation with nothing in it is a dead end. Inviting people can wait. The first screen after that is the project’s issue list, with an agent connection offered right beside the first issue.
1. Sign up
Create your account
Free for twenty people per organisation, forever. No card.
or sign up with email
Next comes a short profile check: name, avatar and time zone, pre-filled. An email sign-up verifies its address here; Google and GitHub continue straight on.
2. Name the organisation
- Your profileConfirm your name and time zone.
- OrganisationName your team’s workspace.
- First projectCreate a place to track work.
- Invite peopleAdd teammates, or skip for now.
Step 2 of 4
Create your organisation
Give your team’s workspace a name. Your projects and teammates will live here.
The ID is derived from the name as you type, and you can change it before saving. Nothing is created on your behalf.
3. Create the first project
- Your profileConfirm your name and time zone.
- OrganisationName your team’s workspace.
- First projectCreate a place to track work.
- Invite peopleAdd teammates, or skip for now.
Step 3 of 4
Create your first project
Name your first project. This is where your team will track work.
The key is derived from the name: initials for several words (Partner Portal becomes PP), the first three letters for one. Acme would give ACM; Alex typed ACME instead.
4. Invite people, or skip
- Your profileConfirm your name and time zone.
- OrganisationName your team’s workspace.
- First projectCreate a place to track work.
- Invite peopleAdd teammates, or skip for now.
Step 4 of 4
Invite your teammates
Anyone you add joins Acme and ACME in one step. You can also invite people later.
Or share a link
Anyone with the link can join. You can revoke it at any time.
Alex skips. A solo trial is a normal way in, and the product does not act broken without a team.
5. Land on the issue list
Acme has no issues yet.
Three ways to put the first one in. No demo data: what you see is yours.
What Connect an agent does
- Creates a personal access token with
issues:readissues:writecomments:writetime:write. Admin scopes are yours to add. - Shows the config for the agent you pick, token filled in, with one Copy button.
- Watches for the first call and flips from Waiting for the first call to Connected.
6. File the first issues
- ACME-3EpicMake invitations clearerNormalOpen
- ACME-2BugPassword hint is cut off on small screensNormalOpen
- ACME-1BugSign-up form rejects plus addressesNormalOpen
Alex Lee created ACME-11 Sep 2026
Alex Lee created ACME-21 Sep 2026
Alex Lee created ACME-31 Sep 2026
Only a title was typed for ACME-1 and ACME-2; they took Open, Normal and Bug. ACME-3 was switched to Epic, so it becomes a swimlane on the board. The key is now fixed.
Hand-drawn product views with fictional data. Acme, its people and its issues are invented.
What the new project already has.
Nothing was configured during onboarding, and nothing needed to be. Every new project starts with these lists and a board. A Project Admin can rename, recolour, add or delete values later; there are no transition rules to design, so any status can follow any status.
| Status | Category | Resolves the issue |
|---|---|---|
| Submitted | backlog | No |
| OpenDefault | unstarted | No |
| In Progress | started | No |
| Reopened | unstarted | No |
| Can’t Reproduce | cancelled | Yes |
| Duplicate | cancelled | Yes |
| Fixed | done | Yes |
| Won’t fix | cancelled | Yes |
| Obsolete | cancelled | Yes |
| Closed | done | Yes |
New issues start at Open. Moving one into a done or cancelled status records when it was resolved; moving it back out clears that.
- Show-stopper
- Critical
- Major
- NormalDefault
- Minor
Each value has a one-letter badge and a colour. The issue list shows the letter; click it to change the priority in place.
- BugDefault
- Feature
- Task
- Epic
An issue with subtasks shows their story points added up, so an Epic carries its whole scope.
- To doSubmittedOpenReopened
- In progressIn Progress
- DoneCan’t ReproduceDuplicateFixedWon’t fixObsoleteClosed
The board shows one sprint at a time. Moving a card to another column gives the issue that column’s first status. Columns can be switched to priorities or types, and more boards added.
- DevelopmentDefault
- Documentation
- Implementation
- Investigation
- Maintenance
- Observation
- Testing
Time tracking is on in a new project. Each logged entry takes a work type, starting at Development.
Add structure when the work asks for it.
The same project, the same issue keys, the same people. Each of these is already there in the project; you start using it when a plain list is no longer enough.
When a week needs a plan
Sprints, a backlog and the board
Plan a sprint, drag issues in from the backlog and start it. The board the project already has follows the running sprint, with story points and a burndown.
Sprints and boardsWhen effort needs counting
Time on the issue
Time tracking is on in every new project. Log time where it was spent, set an estimate, and read the same entries in the timesheet.
Time trackingWhen an issue needs one more fact
Custom fields
A Project Admin adds a Severity, a customer or a launch date. The field shows in the list, in search, in the CSV export and to agents.
Issue trackingWhen someone asks how it is going
Reports
Nine reports read the same issues and time, from burndown and issue age to the timesheet. Click any bar, slice or cell to open the issues it counts.
Reports
Try it on real work, then decide.
Nothing Left is in beta. Sign up and you are in: no sales call, no card, no trial clock. The point is to run real work through it and find out whether it fits.
Setting it up for the team? Read the docs or ask support
No subscription charge during beta.
Any team size, every feature. Invite everyone who does the work.
Your first 20 members stay free forever.
When billing arrives, the first 20 members of every organisation remain free, including organisations that joined during beta. We will give notice before charging for additional seats.
5 GB of storage, or your own bucket.
Each organisation has 5 GB of platform storage for attachments. Connect your own Cloudflare R2 or AWS S3 bucket and the limit lifts as soon as the bucket is verified. Limits and storage
Open source under AGPL-3.0.
The hosted service runs the same build as the public repository, so you can read the code you are trusting with your work. Source on GitHub · Licence
Questions before the first project.
Setup, team size, bringing work across and what the beta costs. Short answers here, details in the docs.
Do we need to design a workflow before we start?
No. After a short profile check, onboarding asks for an organisation name and a first project; nothing else is configured. Statuses, priorities, types, work types and a board are already there. A Project Admin can rename, add or delete values later in the project’s settings.
Can I try it alone before inviting anyone?
Yes. The invite step has a Skip for now button, and the project works the same with one member. Invite people by email or with a share link whenever you are ready.
Is there a team size this is meant for?
No. During beta there is no subscription charge for any team size. When billing arrives the first 20 members of every organisation stay free forever, and invitations past the 20th keep working today. We will give notice before charging for additional seats. Pricing
Can we bring issues from the tracker we use now?
Generic CSV import is one of the three ways in on the empty project: map the columns, dry-run every row, then import. There are no native importers from other trackers. An agent connected to both your old tracker and this one can help carry issues across, with you reviewing the mapping.
What does connecting an agent involve?
On the empty project, Connect an agent creates a personal access token with issue, comment and time scopes, then shows the config for your agent with the token filled in and one Copy button. It switches to Connected when the agent’s first call arrives. Your email address has to be verified first, and Settings → Access tokens revokes the token. Connecting an agent
What happens when we fill 5 GB?
Banners appear at 80% and 95%, and at 100% new uploads are refused with the two ways out: delete files from the storage screen, or connect your own Cloudflare R2 or AWS S3 bucket. The limit lifts as soon as the bucket is verified. Avatars never count. Limits and storage
Create the first project and see what is there.
Join the beta and sign up with Google, GitHub or an email address. Name your organisation, create a first project, and skip the invitations if you are trying it alone. You land on the project’s issue list, with a first issue and an agent connection one click away.