A web-app factory under your architectural control, with proof.
Public roadmap, public ADRs, public proof page. Every build is gated by a functional POST + GET smoke against the live server. Source-available on GitHub.
What matters to ctos
- ✓Public Architecture Decision Records show how we made every technical trade-off
- ✓Linux bridge runs verified web builds today; Windows bridge + a self-host-in-VPC story are roadmap
- ✓Multi-model gateway with BYOK support — switch providers per request without rebuilding
- ✓Every passing build produces a structured proof pack: prompt, manifest, compile attempts, smoke result, AI cost
- ✓Honest comparison vs Devin / Replit / Lovable / v0 / Bolt, with cited evidence
Objections ctos raise — and our answers
We don’t pretend these don’t come up. Here’s how we respond.
Per-entity generation with relationship context produces clean, idiomatic code. Read ADR 0003 on why one-prompt-per-entity beats one-prompt-per-app. The Recipe Manager Web case study at /factory/case-studies/recipe-manager-web is the first verified end-to-end prod pass with real numbers — replace any case study we mark "illustrative draft" with this one until more land.
Source-available on GitHub. The generated workspaces are plain Next.js + libSQL — no proprietary runtime, no factory dependencies post-download. A first-party docker-compose / Terraform self-host story is on the roadmap, not shipping today. For now, you can host the generated apps anywhere Next.js runs.
Multi-model gateway routes around it automatically. 12 models across 4 providers. You see the failover in the build log. ADR 0002 explains why we built our own gateway instead of relying on OpenRouter.