the platform · since 3 September 2026
A platform designed from the ground up for AI agents
My own platform for building and hosting products: Claude Code agents build them from specs — WHEN/THEN scenarios, agent roles, checks, batched releases. I designed the system and run it.
- products 5
- repositories 29
- commits 3,600+
- merge requests 950+
- tests 4,800+
- updated
How this is counted
A snapshot taken at site build time. Commits are counted on the main branches of the product and platform repositories, merge requests across the products, and tests by counting test declarations in product code rather than from a runner report. Rounded down.
How a product moves through the pipeline
Five steps from the first conversation with a client to a working demo.
-
Requestconversation → WHEN/THEN requirements
The brief is prepared in advance — industry research and a sample brief, then an interview with the client on a prepared set of questions. The conversation becomes a draft change request with WHEN/THEN scenarios.
-
Specopenspec, tasks with file ownership
Wherever the answer shapes the product — law, payments, 3D, search — research comes first. The architect splits the request into tasks: who owns which files and in what order they merge.
-
AgentsClaude Code in defined roles
The OpenAPI contract is generated from code. API, web and UI-kit engineers work in parallel, each in the files it owns. Destructive commands are blocked for agents at the tooling level.
-
Reviewreviewer, security, tests, screenshots
A reviewer and a security agent go over the core: money, bookings, permissions. Mutation testing hardens the tests, and a screenshot agent checks layouts at three widths, in every language and theme.
-
Live demobatched release at 12:00 and 17:00 UTC
A task is done when it’s merged. Releases go out in batches twice a day through GitOps, followed by a smoke test of the demo. The product handbook and the action log are updated the same day.
What it’s made of
Products on top, hardware at the bottom. Everything is declared as code and applied from git.
By the numbers
- ≈12 minto set up a new product with one command
- ≤ 1 dayfrom brief to a live demo
- 9cluster admission policies
- 34alerting rules
- Products client product demos
- SSO single sign-on and a gate in front of every demo
- GitOps Flux applies everything from git
- Kubernetes 3 Talos Linux nodes, admission policies
- Proxmox virtualisation, segmented network
Around the cluster: own GitLab and CI · registry with signed images · secrets · backups with restore drills · metrics, logs, alerts · mesh VPN
Agent roles
11 roles per product. An agent works only within its role and the files it owns.
- Architect
- Contracts
- API engineer
- Web engineer
- UI kit
- Reviewer
- Security
- Test hardener
- Screenshots
- Handbook
- Journal
What each role does
- ArchitectSplits a request into tasks: file ownership and merge order.
- ContractsOpenAPI from code, a mock for the frontend, compatibility checks.
- API engineerRust services: domains, migrations, permissions.
- Web engineerNext.js and FSD, against the mock and the full product locally.
- UI kitTokens, components, Storybook, axe checks.
- ReviewerA fresh look at the core: spec conformance and correctness.
- SecurityStatic analysis, dependencies, tenant isolation.
- Test hardenerMutation testing and property-based tests.
- ScreenshotsLayouts at 360, 390 and 1280 px, Lighthouse.
- HandbookProduct docs: features, business rules, decisions.
- JournalThe day’s actions, problems and practices.
- ArchitectSplits a request into tasks: file ownership and merge order.
- ContractsOpenAPI from code, a mock for the frontend, compatibility checks.
- API engineerRust services: domains, migrations, permissions.
- Web engineerNext.js and FSD, against the mock and the full product locally.
- UI kitTokens, components, Storybook, axe checks.
- ReviewerA fresh look at the core: spec conformance and correctness.
- SecurityStatic analysis, dependencies, tenant isolation.
- Test hardenerMutation testing and property-based tests.
- ScreenshotsLayouts at 360, 390 and 1280 px, Lighthouse.
- HandbookProduct docs: features, business rules, decisions.
- JournalThe day’s actions, problems and practices.
House rules
- Everything is declared as code
OpenTofu, Ansible and Kubernetes manifests. If it isn’t in git, it won’t survive a rebuild.
- Every requirement has a check
The platform itself is 58 requirements and 94 scenarios; each requirement has an automated check or a drill.
- Products are portable
Each product carries its own database setup, backups and monitoring in its repositories and can move to the client.
Timeline · 2026
- first platform commit
- pilot product with 7 services
- flooring catalogue and installer platform
- designer rewards programme
- hostel websites and booking
- Ultramarin, the 3D gallery
Questions from clients
Who is responsible for the result?
I am. Agents carry out tasks from the spec; I own the requirements, the architecture decisions, acceptance and releases.
How soon is there something to look at?
Usually within a day from brief to a working demo. After that the product grows through change requests.
Where will the product live?
The platform only hosts development and demos. The product is self-contained — it brings its own database setup, backups and monitoring and can move to your servers.
What do you need from the client?
Answers to the brief. I prepare the interview in advance with industry research and a sample brief, so there’s something concrete to react to.
Can I see the products?
Yes. The demos sit behind a login: message me on Telegram or by email and I’ll send login details after a short conversation.
Need a similar product? Let’s start with a brief
Tell me about the problem. I’ll come to the conversation with industry research and a sample brief.