Maevu turns a messy backlog into a plan you can trust — requirements, customer sign-off, capacity-aware planning, and the evidence to prove it.
you pay with your money, not your data.
What Maevu does
Point Maevu at your backlog. It groups, orders, buckets by quarter and splits the work — so planning starts from signal, not a spreadsheet.
A real constraint solver schedules by capacity, calendars, skills and customer dates — and explains every placement instead of hiding it.
A two-gate lifecycle where the plan reflects when the customer actually approved. Delay approval → the milestone slips, visibly.
Jira, calendars, storage — and a small, safe language to build your own, aimed at business users, not only programmers.
EU-hosted or self-hosted. Open-core. Free/busy over private detail. Your data stays yours — that's the whole point.
ISO 27001 evidence falls out of the work you already track — traceability from requirement to release to test.
A glimpse
An illustration of the flow — order the work into buckets, balance it across the team, and lay it on a calendar. (Example data.)
Where we're headed
We build Maevu with Maevu. This roadmap is generated from our own instance — dogfood, in public.
Built different
Most delivery tools sell you visibility and keep your data. Maevu inverts it: a real planning engine, connectors you can read, and an exit that's always open.
EU cloud or your own servers. We collect the minimum — free/busy, not your calendar's contents.
The core is AGPL and self-hostable. No hostage data, no lock-in.
Extend Maevu in a small, safe DSL meant for business people — not a plugin SDK only coders can love.
Rust, Haskell and a real constraint solver — the technology that schedules airlines and factories, pointed at software delivery. Fast, and correct.
Non-profits can ask for free access. Students use it for free. On purpose.
We're opening the alpha to a small group. Send us a line and we'll reach out.
Email us to request accessNo spam. No data resale. Ever.