About
A work tool should not be one more thing you fight with.
You already negotiate with payroll, HR, and procurement. Planning the work itself should not join that list — and yet the tools meant to help a team plan kept becoming work of their own. Not because any of them are bad software: they are shaped by who they are sold to.
Sold upward, a tool grows the surface a manager wants to see and the team below inherits the upkeep. Sold on novelty, it chases whatever is fashionable that year. Sold to everyone, it grows until the thing you need is buried behind the things you don't.
So the question we start from is not which features are missing. It is who a decision is being made for.
We build for the people who open the board on Monday morning.
Three ways a good tool goes wrong.
None of these come from bad engineering. They come from who the product is being built for.
Built for the org chart
Heavyweight suites are shaped around what leadership wants to see. Configuration becomes a project of its own, and the people doing the work carry the cost of a reporting layer they never asked for.
Built for the demo
A tool can spend its roadmap on whatever is loudest that year. The headline features move; the everyday ones — a filter that holds, a board that repaints instantly — stay where they were.
Built for everyone
Cover every workflow and every surface fills with things most teams switch off on day one. Breadth is easy to sell and expensive to use: the feature you need sits three menus behind nine you don't.
What we optimise for.
Four commitments that decide what gets built and, more often, what doesn't.
Set up in minutes
A workspace is useful the moment it exists. Projects, statuses, and cycles have working defaults, so configuration is something you do when a team actually needs it — not a prerequisite for the first task.
Built around the work
Boards, tables, and cycles exist to move tasks forward. Reporting reads what the work already produced rather than asking anyone to maintain it by hand.
Open by default
A public REST API and an MCP server ship as part of the product, not as an enterprise add-on. Your workspace is reachable from your own scripts and from AI agents you choose to connect.
Your data stays yours
Your workspace runs on servers in Warsaw, with storage and backups in the EU. Analytics are self-hosted and shared with nobody. You can export everything you own at any time, and dormant accounts are anonymised instead of kept forever. Every processor we rely on is named in the DPA.
Decisions, not omissions.
Restraint only counts if it is deliberate. A few limits we picked on purpose, and why.
- Subtasks nest one level
- Deeper trees hide work instead of organising it. One level answers what belongs to what, and keeps a board readable at a glance.
- One free tier, with real limits published
- Every plan limit — seats, storage, labels, API rate — is written down before you sign up, starting with 7 seats on the free plan. No quote, no call, no discovering the ceiling in production.
- Rules, not a workflow canvas
- Automation should read like a sentence: when a task moves to In review, assign it to the reviewer. Rules like that stay readable to whoever inherits them a year later. A canvas that can express anything ends up needing someone whose job is to maintain it.
Ready to work without the clutter?
Get started free