Tasks was not built to become a product. It was built because I needed it and could not find anything that did what I wanted.
Why it exists
I work in operations. That means many small things to keep track of: a certificate that expires, a pod that restarts, an idea in the middle of a debugging session. I tried what was out there. The big tools could do everything except get out of the way — pages that load, fields I never fill in, reports nobody reads. The small ones were too small.
So I built my own. First it was a board with cards. Then columns I could rename, subtasks that could cross project boundaries, labels, a log of everything that happened. Nothing remarkable — just exactly what I used, and nothing else.
What made it worth sharing
Meanwhile I started using an AI assistant in all my other work. And it became obvious it could handle the cards too — if only it could reach them. So I built an MCP server into the backend.
The difference was bigger than I expected. “File these three bugs and set the first one to in progress” became one sentence instead of five minutes of clicking. The assistant could read the board before suggesting anything. Cards appeared while I was talking about them.
That is the part I could not find anywhere else, and that is why this is on the internet instead of just on my machine.
How it is run
On my own hardware in Sweden, by one person, next to a day job. That has consequences worth saying plainly: no uptime guarantee, no round-the-clock support, and a real chance that something breaks one evening when I am away from the computer. The current status is on status.tasks.nu, and that page deliberately lives somewhere other than the service it watches.
The upside of the same fact: there is no investor who wants to see growth, nobody who profits from your data being hard to move. Export and deletion have been built in from the start, not bolted on when someone asks.
Where it is going
Tasks is in beta and free while it lasts. Documents arrived recently, so runbooks and decisions live next to the cards instead of in a wiki nobody opens. What gets built next is what I miss myself — the same principle as before: I build what I use.
If you have an opinion about what should exist, get in touch. It is still small enough that it matters. Contact details are here.