What We Built

A million lines of code.
Most of it thrown away.

Six months. The three of us....Sam, Peter and Claude. We built, broke, and rebuilt until only the terrific survived. The moat isn't the code. The moat is the scar tissue.

01

The Platform

We built our own operating system. 85,000 lines of code. It manages our pipeline, builds software autonomously, handles our expenses, files our taxes with HMRC, and runs our billing. We watched it evolve from an idea on a whiteboard into something that genuinely runs our business.

It started with 34 microservices. They broke before they scaled....we could see it coming, to be honest. So we rebuilt everything into something that actually works. Large codebases became light skills. Rigid frameworks became self-healing fabrics. We dropped half a dozen standalone products by building one thing that replaced them all.

85,000

lines of code

70+

commits

11

database migrations

02

The Factory

We built a system that builds systems. It monitors code, checks quality, and writes software autonomously. Then it checks its own work. The factory that builds things has its own watchdog. We remember thinking....that's either mad or genius. Turns out it was both, several times over.

We found every single way to make a brittle autobuild system. Version after version. Each one got closer but revealed new failure modes. Not the building....the knowing-when-it's-broken part. The recovery. The self-awareness. We almost lost count of the versions, but we didn't....we just kept going.

The proof:

The factory's first customer was us. It built an 85,000-line security platform from scratch. Then hardened it through 19 security-focused commits....race condition fixes, cryptographic hardening, GDPR compliance, PII encryption, CSRF protection.

287 source files. 7 services. 5 packages. Built by the factory, for Darkhouse.

03

The Pressure

The dev community has a meme: “vibecode is shit.” Yes. That's the point. That's the starting material. The question is what you do with it.

Most people stop at the meme. They point at the shit and feel clever for noticing. We took it and put it under pressure. Again and again. A million lines of pressure. And what came out the other side is a diamond....not because we're smarter, but because we paid the cost of compression that nobody else has been willing to pay.

Anyone else starting this process has nearly 2 million lines of code to throw away before they match where we are today. We build every day, so by the time the market starts to try AI properly, it will take 4 million lines of code to catch up with us.

We don't burn wasted tokens. We form hard experience. And we are not afraid to iterate entire codebases....because in a traditional dev team it would take years to get where we do in weeks.

04

What We've Proven We Can Build

Compliance & Governance

  • Automated compliance evidence collection....continuous, not annual
  • Platforms for financial services regulation and UK energy sector NIS compliance
  • Machine-readable controls mapped across ISO 27001, SOC 2, and ISO 42001

Secure Infrastructure

  • Zero human access to production. AI proposes, humans approve with hardware keys
  • Every action logged immutably. Built by our factory, hardened through 19 security commits
  • Infrastructure discovery across cloud and on-premise in under 30 minutes

Legal Tech

  • 100+ UK Acts of Parliament encoded as machine-readable data
  • Four legal domains: civil, criminal, intellectual property, tax
  • Trademark clearance search. Working tax calculators referenced to legislation

Data & Documents

  • AI-powered bid automation: 40+ hours reduced to 2
  • Document ingestion, extraction, enrichment, and secure storage
  • HMRC tax filing....CT600, VAT returns....through code we wrote

Recruitment

  • Bias-blind assessment. CV counts for 10%. The interview counts for 60%
  • Voice AI interviews. Personality profiling. Skills graph matching
  • Analytics dashboard for hirers: team composition, capability gaps

Quality & Security

  • Automated code quality pipeline....scanning, fixing, enforcing
  • Container security scanning. E2E testing. Penetration testing toolkit
  • Deployed and running in our own development workflow