Build a full-stack app on a canvas. Wire the pieces together. Export a real SST v4 or Vercel project and deploy it yourself. Every file is type-checked against the live docs. The generator makes zero AI calls. Nothing is hallucinated and nothing phones home.
Runs in your browser. Your cloud credentials never enter the picture.
Point Live Mode at an SST or Vercel repo. It reverse-engineers the code into the same map the builder draws. You get every resource, the data flow, a cost estimate, and a plain list of what it could not read. Secrets are redacted before parsing. It never reads your .env files. Nothing leaves your machine.
Already have a sstdream-scan.json? Open it in the builder.
# in any existing SST or Vercel repo. zero install, zero network
curl -sO https://raw.githubusercontent.com/SoloNerds/sstdream/main/scripts/sst-dream.mjs
node sst-dream.mjs scan .
# writes ARCHITECTURE.md + sstdream-scan.json. reads your code, sends nothingThe static map ships today. The read-only live metrics overlay is on the roadmap.
An infra generator that emits wrong config is worse than nothing. So correctness is the whole product.
No model guesses your infra. Every line maps to a real SST or Vercel API, recorded with the doc it came from. The whole export is type-checked in CI before you see it. If the docs change, the snapshots break, and we find out before you do.
A static data-flow trace runs in your browser. It answers one question. Does the app reach the bucket, the queue, the table? You see the gaps before you spend a cent. Nothing is deployed.
Export a full Next.js app. Config, server actions, routes, workers, env, README, AGENTS.md. Drop it in and run sst deploy or vercel. There is no diagram-to-code gap, because there is no diagram. It is code.
Files are built locally. Your cloud credentials are never read, because there is nothing to send them to. Share a design as a link if you want. Nothing is uploaded.
Drag resources onto the canvas and connect them. Pick AWS/SST or Vercel first.
The wiring turns green when it lines up. Read the cost estimate and the warnings.
Export a type-checked project and run it yourself. You deploy. We never do.
Two lanes, one shell. Adding a deploy target or a template is a small PR with docs to follow. Bring your own platform.