Maevu is born

Maevu is born. So — hello.

We’ve spent years building software for other people: shipping features, missing dates, explaining slips, and watching good teams drown in tools that promised clarity and delivered dashboards. Maevu is our answer to that. Not another tracker. A delivery platform that plans honestly, connects simply, and never holds your data hostage.

The pain we kept feeling

Three frustrations came up again and again.

Planning was theatre. Every tool could draw a Gantt chart and none could tell you the truth: that the person the sprint depends on is on holiday, that half the tickets have no estimate, that your architect is quietly booked as a developer on work he’s only meant to review. The plan looked confident and was wrong by Tuesday.

The data was never ours. Everything lived in someone else’s cloud, exportable in theory, gone in practice. You paid a subscription and paid again in lock-in.

Extending the tools meant becoming a programmer. Every workflow that mattered — “flag this as a change request,” “pull availability from our calendars” — required a plugin, an SDK, and a developer who had better things to do.

What we want to offer instead

Maevu starts from the work you already have and helps you turn it into a plan you can trust. Point it at a backlog and it will group, order and split the work, then schedule it against real capacity, real calendars and real skills — and explain every decision, because a plan you can’t interrogate isn’t a plan, it’s a guess with nice fonts.

And it treats your data as yours. Host it in the EU, or host it yourself. The core is open. When you want the door, the door is open — that’s the deal.

Connectors, for people who aren’t programmers

Here’s the part we care about most. Software is only as useful as what it connects to, and today connecting things is a job for engineers. We don’t think it should be.

So connectors in Maevu are written in a small, safe language designed for business people — the folks who actually know what “a change request” means and when a document counts as one. You describe what should happen, not how to wire an API. The result is something a delivery lead can read, change, and trust — without filing a ticket with engineering.

That’s the bet: put the power to extend the tool in the hands of the people who use it.

A word on how it’s built

We won’t bore you with the stack, but we won’t hide it either. Underneath, Maevu leans on Rust, Haskell, and a real constraint solver — the same family of technology used to schedule airline crews and factories, pointed instead at software delivery. We chose these because they let us be fast and correct, and because correctness is the whole promise. More on that another day.

Maevu is early. We’re opening an alpha to a small group soon. If any of this sounds like a tool you’ve wished existed, get on the list — we’d love to build it with you.