Ship the roadmap. Autonomously.
Maelo is an autonomous product team behind one lens: it researches, specs, prototypes, builds, and proves every feature — keeping context from the first idea to a merged, QA’d change.
An engineering org’s workflow, run by AI
Every stage of turning an idea into shipped software — with you steering in plain language.
Deep research & validation
Vendor research, pricing, buy-vs-build matrices, and live API validation — so an idea is de-risked before it becomes a build.
PRDs from your real code
Maelo reads across all your connected repos and synthesizes user-facing feature PRDs — not folder names — each a bundle of spec, build plan, and test guide.
Roadmaps & epics
Time-phased timelines, Now / Next / Later swimlanes, and parent epics that decompose into interconnected child PRDs. Publish a shareable snapshot.
A prototype with every PRD
See and feel a working prototype of the feature before committing engineering time — generated with Maelo’s own engine or v0 / Lovable.
In-house builder
The orchestrator decomposes a plan into parallel workstreams, then builds them on your own always-on runner or on Maelo Cloud.
Autonomous QA
Maelo compiles your TEST plan into a real click-through and runs it against a live pre-merge deploy, writing back pass/fail with evidence. (Runs on your paired Maelo desktop.)
Bugs → fixes from Sentry
Production errors surface in the lens and turn into a scoped PRD fix you can review and ship — closing the loop from incident to patch.
Escalations & control
When a decision needs a human, Maelo escalates instead of guessing. Every doc, build, and QA run is inspectable and reversible.
Autopilot auto-merge
Today Maelo opens clean PRs for human review. Full Autopilot — auto-merge the instant tests and QA are green — is on the way.
It reads the code, then writes the spec
Instead of naming folders, Maelo behaves like a VP of Product: it broadly samples your API surfaces, screens, and vocabulary across every connected repo, then synthesizes the user-facing capabilities of the system as a whole.
- Cross-repo PRDs that span marketing, web, and API
- Each PRD is a talkable bundle: spec, AI build plan, test guide
- Prototype attached, versioned docs, revert any change
PRD
PLAN
TEST
Proof, not vibes, before it merges
Maelo compiles your test plan into a real browser flow, runs it against a live pre-merge deploy, and writes pass/fail with evidence back to the PRD. It executes on your paired Maelo desktop today. When Autopilot arrives, a QA skip will never count as a pass — anything red or unverifiable escalates to a human.
- TEST plan compiles into a real navigate / click / assert flow
- Runs against a live deploy of the integration branch — not the prototype
- Review PRs for a human today · Autopilot auto-merge coming soon
Trigger anywhere, execute where you choose
Register a machine once — a Mac Studio, a build server — and it becomes an always-on runner. Where you trigger a build (web, desktop, mobile) is decoupled from where it runs. Maelo Cloud is the always-available fallback.
- Runners dial out and heartbeat capabilities — no inbound ports
- Short-lived, scoped push tokens per dispatch — never your long-lived keys
- Pick a named runner by capability, or fall back to cloud
Mac Studio · studio-01
local models · repo cloned
Maelo Cloud
Agent SDK · always available
Build server · ci-eu
last seen 2h ago
Give Maelo your backlog.
Connect your repos and let Maelo research, spec, build, and QA the next feature — while you review the parts that matter.
No credit card required · Bring your own model keys