Deploy the whole app.
Not just the frontend.
Your server, PostgreSQL database and persistent files run together in an isolated microVM. Push to GitHub, drop a folder, or ask your AI assistant to ship it.
project-notebook
Building- Branch
- main
- Commit
- 2a856c2 Add attachments
- Resources
- PostgreSQL · 1 GB /data
01 — Ship
Three ways in. One place to run it.
Start wherever your code is. Every path ends in the same project, with the same history, logs and rollback.
Push to GitHub
Pick a repository and a production branch. Every push builds the exact commit; read-only access to your code.
Upload a folder
No repository yet? Choose a project folder. Secrets, .env files and build output are left out automatically.
Ask your AI assistant
Connect Claude Code over MCP once. It can create projects, set variables and deploy — with your permission.
02 — Any stack
Bring your framework. We detect the rest.
localhost reads your project, picks the right build and runtime, and gives every framework the same database, files, logs and rollback.
03 — Run
Built for apps that remember things.
A real server process, not a function that forgets. Data lives next to your code and survives every deploy.
PostgreSQL, per project
A dedicated database and login for each project, connected through DATABASE_URL. Browse and edit records from the dashboard.
| id | title | attachment | updated |
|---|---|---|---|
| 1 | Launch checklist | plan.pdf | 2h ago |
| 2 | Interview notes | — | Oct 19 |
| 3 | Design review | board.png | Oct 18 |
Files that stay
A persistent disk mounted at /data. Uploads survive redeploys and restarts.
Secrets, scoped
Encrypted at rest. Choose whether each value is available at build time, runtime, or both.
Logs and metrics
Build output, runtime logs, CPU, memory and response errors for every project.
Rollback
Restore any earlier successful deployment, with the settings it was built with.
04 — Trust
A broken build never takes you down.
Every build and every app runs inside its own Firecracker microVM — the open-source virtualization technology AWS built for Lambda.
Exact source
The commit or upload is recorded before anything runs.
Isolated build
Its own VM. Network limited to the npm registry.
Checked output
Paths, links and size are verified before use.
Health check
The new version must answer before it gets traffic.
Live over HTTPS
Traffic switches only after every step passes.
Traffic moves to the new version. The previous one stays available for rollback.
Production keeps serving the current version. You get the log and the reason.
05 — Agents
Your AI assistant can deploy, too.
localhost speaks MCP. Your assistant works through the same projects and permissions you see in the dashboard — nothing hidden, nothing extra.
- Sign in with OAuth. No tokens pasted into prompts.
- Scoped to your account. It can only reach your own projects.
- Same safety rules. Isolated builds, health checks, rollback.
Done — it’s live at notebook.dev.localhost.tr. Build took 1m 12s.
Private preview
Ship your next app on localhost.
We are onboarding developers in small groups while we expand runtimes and regions.