Two records
Hours live in another tab
The tracker holds the work and a second tool holds the time. One of the two is always stale, and someone spends Friday reconciling them.
For studios running work for more than one client
Every client in their own room.Every hour on the right one.
TaskView is a self-hosted project manager for a team that serves several clients at once. Roles are set per project, so a client sees their own work and nothing else. Hours are logged on the task instead of in a second tool. And nobody — contractor or client — costs you a seat.
ClientIn flightHours this week
Northwind Retail
Checkout flow UIPayment SDK v22Android crash
0h
Vantage Health
Onboarding screensAccessibility pass
0h
Meridian Bank
Security reviewBiometric loginRelease notes
0h
Loft & Co
Brand site rebuild
0h
4 clients · 9 in-house · 3 contractors0 h logged · 0 h billable this week
The leak
Where the hours go missing
None of these is a tooling problem on its own. Together they are the difference between a project that made money and one you only believe did.
Seats
A three-week contractor costs a month
Per-seat plans bill by the head, not by the engagement. So you either pay for the month or share a login and lose track of who actually did the work.
Seats
Letting the client look costs the same as hiring
A read-only reviewer is priced like a full teammate, so clients get emailed screenshots instead — and the email thread quietly becomes the source of truth.
The answer
Nobody can say whether this one made money
The estimate sits in the proposal, the hours in a timesheet, the invoice in the accounting app. The answer arrives a quarter after you needed it.
Access
Give a client a window, not a key
Roles are defined inside each project, one at a time. Pick a role below and watch the same workspace change around it.
Pick a role — or keep scrolling
An example set of roles — you build your own from 28 permissions, and a role in one project never carries into another.
“Permissions are enforced on both client and server — even if someone inspects the UI or calls the API directly, the server checks permissions before allowing any action.” TaskView documentation
Hours
Hours, and money, where the work already is
Time tracking and the numbers it feeds sit on the task, not in a parallel system you reconcile on Fridays.
Log
Start the timer on the task
Run a timer while you work, or add the entry by hand afterwards. Every entry belongs to the task it came from, so the record of what happened and the record of how long it took never drift apart.
- Start, stop, and see the timer that is running right now
- Every entry carries a billable flag — filter any report to billable only
- Manual entries you can edit, each with its own change history
- Reports by day, by person, by task, and by contributor
Settle
Find out which project actually paid off
Income and expense amounts sit on the tasks, next to the work that earned them, and analytics rolls them up. The question every studio asks at the end of a phase has an answer on a screen instead of in a spreadsheet somebody has to build first.
- Net profit, total income and total expense across the projects you can see
- Income and expense per project and per tag, month by month
- Planned against actual, and top projects by amount
- An estimate on every task, to hold the hours against
At invoice time
The same reports are API endpoints. A scoped token lets your billing script — or an AI assistant through the MCP server — pull the month's billable hours by project and by person, without giving anything a login it doesn't need.
The cast
Everyone on the job. Nobody on the invoice.
A studio's roster changes every month. Your tooling bill should not notice.
In the workspacePer seatTaskView
9In-house team$0 / mo$0
3Contractors this month$0 / mo$0
6Client reviewers$0 / mo$0
2Freelance designers$0 / mo$0
20 people in the workspace$0 / year$0
The Community Edition has no seat limit and no bill. Add the contractor on Monday and remove them when the phase ships. Give the client a reviewer role for the length of the engagement. Neither one ever appears on an invoice.
Compared against $6 per user / month, a common list price for commercial self-hosted plans. Use your own quote.
The workspace
The rest of what the studio runs on
One project per client, lists inside it, and the views your team actually uses.
The paperwork
Passes the client's security review
TaskView runs in your own Docker, on your own domain. Client work stays on infrastructure you control, which is what most MSAs and NDAs are really asking about when they ask where the data lives.
- The app, the database and the files sit on a host you picked — a VPS, a box in the office, a node in your cluster.
- Single sign-on with SAML 2.0 or OIDC, plus SCIM provisioning, free in the Community Edition.
- API tokens are scoped and revocable, so an automation never holds more access than its job.
$ docker compose up -d
✔ db · migrations · api · web
→ tasks.yourstudio.com
Price
The studio pays once. Not once per head.
The Community Edition is the whole product at no cost and no seat limit. The Special Edition adds commercial extras — one payment per organisation, per major version.
Founding customer pricing — the first ten licences at about 30% off
Community
Unlimited people
$0
Free forever
- Projects, boards, sprints, graphs
- Time tracking and reports
- 28 permissions, roles per project
- SSO, SCIM, API tokens, MCP server
Starter
Up to 20 people
$990$690
One payment
- Everything in Community
- Upgrade to 2.x later: $490, optional
Team
Up to 50 people
$2,490$1,740
One payment
- Everything in Starter
- Upgrade to 2.x later: $1,190, optional
Business
Unlimited people
$4,990$3,490
One payment
- Everything in Team
- Upgrade to 2.x later: $2,490, optional
Every licence includes perpetual use of 1.x · all 1.x updates, new features and all · audit log · priority support from the maintainer · an invoice your accounting will accept
Order
Request a licence and an invoice
Tell me about the studio and I'll reply within 24 hours with an invoice and payment options. No sales call, no procurement maze.
Perpetual
The licence never expires
Keep using the last version you received, forever. If the project stopped tomorrow, your instance keeps running.
Updates
All 1.x updates included
Every update inside the major version you bought, new features and all. You pay again only for the next major version, and only if you want it.
Security
No enterprise tax on logging in
SSO with SAML 2.0 or OIDC and SCIM provisioning stay free in the Community Edition, at any number of people.
Paperwork
An invoice your accounting will accept
A proper invoice referencing the SE License Agreement, so it clears your books like any other software purchase.
Would rather just write? Email [email protected] or message me on Telegram.
Run the studio, not the spreadsheet.
Stand it up on a spare VPS this afternoon, move one client onto it, and see whether Friday gets shorter.