The SD-Agile Platform
Four parts. One discipline.
You can practise SD-Agile with a text editor and a lot of willpower. The platform is for when willpower stops scaling — when it is forty people across six teams and nobody can hold the whole specification in their head.
What's in it
Two shipping. Two in beta.
We would rather tell you which is which than let you discover it during an evaluation.
Spec Studio Available now
Where intent gets encoded before any code is generated: Elicit, Review & Instruct, and Library. This is the one most organisations start with.
Learn more →Learning Platform Available now
How training gets delivered and credentialed at scale — cohorts, progress, attestation, six languages. It is the platform this training runs on.
Learn more →App Builder & Deployment Beta
Turn an approved specification into running, deployed software. Free for beta customers now; general availability planned for Q4 2026.
Learn more →Compliance Corridor Beta
Compliance as hard walls before generation rather than a review afterwards. Free for beta customers now; general availability planned for Q4 2026.
Learn more →How they fit
The specification is the through-line.
Each part hands the same artefact to the next one. That artefact is the Build Package, and it is the thing that survives.
Spec Studio produces a Build Package — Constitution, Requirements, Design, Tasks, and Test-Scenarios. Compliance Corridor constrains what that package is allowed to say before anyone generates from it. App Builder generates against it. The Learning Platform is how your people learn to do any of this without supervision.
You do not have to adopt all four, and most organisations do not. Start with Spec Studio, because a good specification is useful even if you generate nothing from it automatically.
How you run it
Free on our cloud. Licensed on yours.
Spec Studio and the Learning Platform are available now in three forms. They are not priced alike, and the difference is worth understanding before your security review starts.
Run the SaaS community version and we operate it — free for government agencies and qualifying nonprofits, paid for everyone else. Run a sovereign instance in your own cloud, either through the Azure Marketplace or as a cloud-neutral image, and it is licensed and paid regardless of who you are. Azure purchases can draw on credits you already have.
The license is a nominal fee that covers the cost of supporting the software. We are a benefit company, not a software vendor with a margin target, and the license is priced to keep the thing maintained rather than to fund growth. Both sovereign images are also bring-your-own-model: you use your own provider credits for LLM usage and we take no upcharge on model consumption. The reason we bother with three options at all is that the buyers who most need specification discipline are frequently the ones who cannot send their requirements to somebody else's cloud, and telling them to get comfortable with it is not an answer.
Start with Spec Studio.
It is the part that pays for itself first, and it does not require you to change how you deploy anything.