EmberMission
From finding to verified delivery.
EmberMission is the EmberNest application for teams that change software on behalf of customers, or commission others to. It turns an assessment into a priced backlog, gets each item approved, delivers it against its own acceptance test, and keeps the evidence of what shipped.
Start with a question every team has
How many of your unmerged branches are really unmerged?
A recovery scan compares patches rather than branch history, so work that was squashed, rebased or cherry-picked is not reported as abandoned. On our own repository, the history count said 59 abandoned branches carrying 177 unmerged commits. The patch count showed that 12 of those branches had already shipped in full, and that 47 held 152 genuinely unapplied commits.
Every EmberMission instance includes recovery scans, as often as you like.
One board per customer codebase.
- The DNA scan and grade, with findings tied to business impact
- A priced backlog your customer approves in their own portal
- Delivery against one acceptance test per Sortie, with evidence of what shipped
- Recovery scans, as often as you like
- Database changes rehearsed against a real database before they ship
- Cloud cost and waste surfaced across the estate
- Review of third-party code and incoming change requests, including checks for low-quality AI-generated changes
A typical improvement backlog
Six prioritised improvements on one existing system, from £450 to £1,500 each, £5,650 in total.
Demonstration values, to show the shape of a backlog. Not a published price list, and not drawn from completed customer work.
How it is priced
Per customer, from £295 a month.
The scans and grade, the mission board, recovery scans and the customer portal, with £25 of managed AI a month pooled across your account.
Delivery work.
Quoted item by item in the backlog the customer approves.
Recovery engagements.
Priced per branch you actually land. A branch marked safe to delete costs nothing.
Confirm the fit. Then prove the value.
Discover
Confirm the delivery problem, the stakeholders and the use case.
Protect
A mutual NDA before any protected information or access is shared.
Demonstrate
A controlled walkthrough, focused on your environment.
Pilot
One application, agreed success criteria, approval roles and commercial terms.