Software we build in the open
The firm's engineering practice, proven in code anyone can read: open source products, built and maintained as commercial-grade software.
Advice is easy to give and hard to verify. Our software practice is the verification: the same engineering discipline we recommend to clients, applied to products we build, document, test and support in public.
lazysite
A Markdown-driven website engine and lightweight CMS: drop a file in and the page is live, served as cached static HTML. AI agents publish through the same rules people do - scoped accounts, audit trail, versioned saves. MIT licensed, engineered to be inspected, and running this site.
lazysite.io - the product, the engineering evidence, and how to adopt it.
ctrl-exec
A remote script-execution framework built on mutual TLS: controlled, auditable execution of operational tasks across a fleet, with a plugin model where every plugin ships with its own tests and test report.
On GitHub - source, documentation and the contribution contract.
Quality and compliance-ready software
Everything we ship is built under our Software Design Practices framework, in which compliance and quality are build outputs, not paperwork: every claim about a system - its dependencies, its test coverage, its release identity, its regulatory posture - is produced mechanically by the process that builds it, and checked by gates that refuse to ship when the claim would be false. The framework is aligned to the regulation that applies to software in the EU, the UK and internationally, built for AI-assisted development under accountable human review, and applied daily to its own development.
The products carry test suites, threat models, SBOMs and release discipline in public, and evidence - per-release SBOMs, test and coverage records, versioned change history - is available to any customer or assessor on request. The same discipline feeds directly into the advisory work: answers demonstrated rather than asserted.