Estates moved in weeks, not quarters.
The agentic migration toolchain behind the Banyan Method. Five modules take the repetitive lift out of a replatform, from estate extraction to cutover, while senior engineers keep the judgement.
The catalogue
Four tools, earned on live estates.
None of these started life as a product plan. Each one was working code on a client problem first, and the verdict on each is the one the estate gave it.
See Graft →
What the estate is doing, live in days.
Estate analytics inside the Magnolia authoring environment. Content performance, journey signals and authoring-time insight, surfaced where publishing decisions are actually made.
Every acquired page on brand, with an audit trail.
The post-acquisition brand-conformance sweep. Scion works through an acquired estate, finds what is off brand, brings it into line, and keeps a record of every change it makes.
The complex journey guided, not abandoned.
The guided-journey agent behind work for a leading international ferry operator, a major insurer and Nikon: conversational booking, servicing and product discovery, built into the live estate.
How tools reach the catalogue
Practice first, product second.
We do not build products in a lab and go looking for problems. The pipeline runs the other way: a tool earns its way out of an engagement, and only then does it get a name, a licence and a roadmap.
01
Built inside an engagement
Every tool starts as working code on a real client problem, written because the engagement needed it, not because a roadmap said so.
Proof: running on a live estate before it has a name
02
Reviewed for viability
Before anything ships, two questions get answered honestly: does it hold up beyond the estate it was built on, and do enough estates share the problem.
Gate: technical and market review
03
Launched via AWS Marketplace
Tools ship through AWS Marketplace, so procurement runs through the AWS relationship your estate already has. No new vendor onboarding cycle.
Tag: Available via AWS Marketplace
04
Run with a roadmap
Each tool has a named owner, a release cadence and a roadmap fed by every engagement it runs on. The practice keeps it honest.
Owner: the practice that built it
The product pipeline Tools earn their way out of engagements, pass a viability gate, and ship through AWS Marketplace. The launch carries the one lime mark. The loop back is the point
Fig 1 · The product pipeline Tools earn their way out of engagements, pass a viability gate, and ship through AWS Marketplace. The launch carries the one lime mark. The loop back is the point: the practice keeps every product honest.
Earned in practice
Every tool ran on a live client estate before it carried a product name.
Questions
Frequently asked questions.
Are these products or services?
Products, with a service history. Each tool was built inside a client engagement and hardened on a live estate before it carried a product name. They are licensed as software with a roadmap, and the practice that built them still runs them on engagements every week.
Do the tools come with engineers?
If you want them. Every tool feeds a named practice service, so you can license the software on its own or take it with the senior engineers who built it. Most clients start with the practice service and keep the tool; some license the tool directly for their own teams.
How are the tools priced and licensed?
Licensing is shaped to the estate, not a seat count, and pricing is on request while the AWS Marketplace listings complete. Talk to us with the size and shape of your estate and we will give you a straight answer.
Are the tools on AWS Marketplace?
That is the route to market. Graft leads, with listings in progress across the catalogue. Each tool carries an Available via AWS Marketplace tag, and procurement runs through your existing AWS relationship once a listing is live. Until then, start with a conversation.
Does the tooling replace the practice?
No, it feeds it. The tools do the mechanical lift: extraction, generation, monitoring, sweeping. Senior engineers keep the judgement, and output is reviewed, not typed. The practice came first and the practice stays in charge.
Start here
Take the tool, or take the practice behind it.
Either way you get software that has already survived a live estate. Tell us what your estate is carrying and we will tell you which tool, or which service, fits.