Questions engineering leaders ask.
What it does
Does Blue Mantis replace my engineers?
No. It takes routine, well-specified work off their plate. Scoping, architecture, and approval stay human.
What kinds of work does it handle well?
Well-defined tickets: features with clear acceptance criteria, bug fixes, refactors, test coverage, dependency and API updates.
What does it not do?
It does not merge its own work, invent requirements, or touch anything outside the permissions you grant.
Getting started
What does onboarding involve?
Connecting your PLM and repositories and setting permission scopes. Most teams are running on a real ticket in the first week.
Do we need to change our workflow?
No. Tickets, branches, and reviews work exactly as they do today.
How is it priced?
Beta pricing is set per engagement during onboarding. Request access and we will walk you through it.
Security and code ownership
Where does our code go?
Work happens against your repositories under scoped credentials. Code is not retained beyond the task and is never used for training.
Is there an audit trail?
Yes. Every agent action is logged and traceable to the originating ticket and resulting PR.
Can we self-host or use our own model keys?
Talk to us during onboarding; deployment options depend on your environment.