Kaisen: the agent factory that built PicoPaaS now builds apps on it
The pattern of Claude Code agents that built PicoPaaS is now Kaisen, an app running on PicoPaaS that builds, deploys and iterates on other apps; today it built three for about three cents.
We built PicoPaaS with a small team of Claude Code agents: backend, frontend, infra, QA, a security reviewer, and a single committer agent that scans every change for secrets. They worked from a written contract, a work ledger, and a question file for the one human in the loop (Chas). Today we pointed that same pattern at a new job: building apps that deploy onto PicoPaaS. The factory that built the platform now builds on it.
From a repo of habits to a product
We extracted the kit into its own public repo, github.com/seaburr/kaisen. Kaisen is also an ordinary PicoPaaS tenant app: 384 MB RAM cap, a MySQL database, nothing special. You deploy it, claim it with a one-time setup code from its logs, then use its Settings page to add an Anthropic API key, a PicoPaaS API key and, optionally, a GitHub repo and token. Output is a live preview on PicoPaaS, a tarball download, or a push to GitHub.
The loop
You give a project a short brief. Claude, through a direct Messages API tool loop with no shell in the container, writes the files. A deploy_preview tool deploys them to PicoPaaS, checks the URL and reads the app's logs so it can fix its own crashes. You try the live preview, type "Tell Kaisen what to change", and it rebuilds and redeploys to the same URL. Every call is metered, with per-run, per-day and per-project dollar caps and a pause switch.
There are no image builds in the loop. One public generic runtime image (kaisen-runtime, Python plus Node) downloads the project's files at boot from a single-use 256-bit capability URL, checks a sha256, installs dependencies and starts the app. A redeploy is just a new URL, about a minute or two, with no CI wait.
What it built today
Three apps from one-line-ish briefs, on Claude Haiku 5.5, for about $0.03 total: a checklist app, an Asteroids clone that runs live in the browser, and a stretch goal, a Python form that saves names to MySQL.
The MySQL one is the honest part. On the first pass, Kaisen reported that the preview had no database. So Kaisen previews gained MySQL support: the project declares it in kaisen.json and gets DB_* env vars with TLS. One line of feedback later, the app stored a name and showed it after a reload (we verified that by hand).
Dogfooding found a real platform bug
Tenant apps could not call any *.picopaas.xyz address: not the platform API, not other apps, not even themselves. In-cluster traffic to the load balancer IP is short-circuited to the ingress pods' private IPs, and the tenant egress policy blocks those. We fixed it with a narrow NetworkPolicy that allows only the ingress controller's web ports.
Because that touches tenant isolation, we pentested it afterwards. No isolation regression: other tenants, platform pods, the Kubernetes API, the metadata endpoint and other databases are all still blocked. The pentest did catch something else. The new access-log format was writing invite-link tokens. They are now redacted.
Also shipped today
- Timestamped logs with file:line and function, on the platform and in Kaisen.
- Projects are now visible to every user in the PicoPaaS nav.
- Test-app images moved out of the customer docs.
Coverage: PicoPaaS at 94% (1802 tests), Kaisen at 90% (130 tests).
What's next (not built yet)
Running the generated tests automatically, a security-review role on generated code, and deploying Kaisen's own previews into a dedicated project. None of that exists today. For now, the loop above is what works, and it is a satisfying thing to watch: a pattern that built a platform, building on that platform.