Kaisen moves in: build an app from a brief, right inside PicoPaaS (Preview)
Kaisen is now part of PicoPaaS as a Preview feature: write a brief, and it builds and deploys an ordinary app into your project, with your own Anthropic key and spend caps.
Yesterday we wrote about Kaisen, the agent factory that built PicoPaaS and now builds apps on it. At that point Kaisen was a separate tenant app sitting next to the platform. Today it moved in. Kaisen is now part of PicoPaaS itself, marked Preview.
What you see
Log in and there is a "Kaisen" entry in the nav. "New app" now offers two doors: "Deploy an image" or "Build with Kaisen (Preview)". A build lives in a PicoPaaS project, personal or a team project. When it deploys, the app lands in that same project as an ordinary app: it shows in the apps list with a "Built with Kaisen · Preview" pill, has the usual health and settings pages, and counts against the project's app limit. No PicoPaaS API key to paste anymore; the platform deploys as you, into your project.
You still own the config
Each project has its own Kaisen settings: your Anthropic API key, model, effort, and spend caps (per run, per day, per build), plus an optional GitHub token the project's builds can reuse. Each build has its own output settings too: download only, or push to its own GitHub repo using the project's token or one just for that build, pushing on finish or opening a pull request.
Creating a build starts it. Kaisen asks questions inline when it needs to, and "Tell Kaisen what to change" starts the next run, which redeploys the same app.
The conversation is yours
The download now includes CONVERSATION.md: your brief, feedback and answers, plus Kaisen's replies, questions and summaries for every run. Agent internals (system prompt, tool calls) are left out, and saved keys are redacted. "Take offline" deletes the app but keeps the build, its files and its conversation; "Deploy again" brings it back at a new address. If the app had a database, its data goes with it, so mind that one.
How it is put together
The API, data and UI live in the platform. The agent loop runs in a separate kaisen-worker pod: same image, no Kubernetes permissions, a heartbeat liveness check, so a long build can't slow the platform API. Previews use one public runtime image that downloads the build's files at boot from a single-use capability link, and the platform pins its digest the way it does for the backup image.
First live build
On production we built a weather app that shows current conditions for a random far-off place. It took under a minute and cost under one US cent on Claude Haiku 5.5, and it deployed into a team project. Small, silly, and exactly the kind of throwaway PicoPaaS is for.
Security, and one accepted low
Two code reviews before shipping found no high-severity issues. Fixes included keeping a moved app from being reachable through its old build, stopping a deleted build from being re-created by an in-flight model reply, hiding the bundle link as an app secret and keeping only the latest one, preserving your env vars on redeploy, and giving the worker only the secrets it needs. One accepted low: team members can push with the project's GitHub token, so the docs say to use a fine-grained token limited to the repos you mean.
Using it also turned up polish: the Kaisen settings page now matches the width of the other settings pages, stale deploy-failure notices clear themselves when a later deploy goes through, and dismissing a notice is saved for the whole team.
Not built yet
To be plain, these are next, not shipped: web access for the builder (Anthropic's web fetch and search behind a per-project toggle, off by default), app logs in the builder's deploy check, running generated tests, and a reviewer step. It's Preview for a reason. Try it, and tell us where it falls over.