Miso Stack.
MISO STACKデプロイ / deploy

Your $5 app shouldn’t be able to cost you $5,000.

Push your app to a live URL that is sandboxed, secret-safe, and observable by default, on a flat monthly bill that never grows on its own. No Kubernetes. No Terraform. No 2 a.m. surprise.

see the console ↓
build .... ok
scan . no leak
live .. 1.8s
> _
MISO STACKPRODUCTION GRADE DEPLOY
01

The console

deploys 1,284build 1.8sregion us-eastscan passusage 68%queue 0
uptime.sys
uptime
0.0%
0.3%
deploy.cfg
deploy time
0.0s
p95 build→live
previews.cfg
PR previews
0
live preview URLs
req.log
requests / 24h
0.00M
16%
build.run
build progress

On track to finish three steps early. Scan running off the hot path.

↗ 30% vs last
0%building
res.mon
resource usage
cpu 0.6 / 1.0 vcpu66%
health.chk
control planehealthy
build queue0 waiting
pre-deploy scanpassing
usage limit68% · alerts on
live.log
12:47:02 push main@a1b3
12:47:03 build ok 1.8s
12:47:05 scan ok 0 critical
12:47:06 live web.misoapp.run
> _
Deploy in secondsgit push → build → live
02

How it goes wrong

Three stories every vibe coder eventually hears. The platform’s defaults decide how they end.

03:14 AM

The loop that bills all night

A retry loop hammers a paid API until sunrise. Pay as you go means every call lands on your card. You find out when the invoice does.

PUSH 14:02

The key that shipped to the browser

Your AI tool pastes a secret key into client code and the deploy goes live. Now anyone who opens devtools can spend on your account.

DAY 3

The database that answered everyone

The demo ships with open access rules. Real user data, readable by anyone who finds the URL.

Nobody in these stories did anything unusual. They shipped with the defaults. Miso makes the safe thing the default thing.

03

Primitives

Everything you love about one click deploy, plus the two things it never gave you: a bill that can’t surprise you, and security on by default.

/01

Git-push deploy

Push to your repo. We build, ship, and hand back a live URL, with a preview URL for every PR.

/02

A bill that can't grow on its own

The plan price is what you pay. Extra usage exists only if you switch it on and give it a limit, and the platform cannot bill past the limits you set.

/03

Pre-deploy scan

Secret and access-control checks on every deploy. Blocks only on critical. Off the hot path.

/04

Managed Postgres

One command. The connection string is stored as a secret and wired into your service. Automated backups included.

/05

Logs & rollback

Per-service logs, metrics, an audit trail, and one-click rollback. Production-grade from day one.

/06

Real regions

Place workloads close to your users. Real placement, honest region codes, no marketing math.

MISO STACK / 味噌

A cold machined instrument with one warm core.

Miso is the stack that has been simmering. Depth over flash. You ship in seconds; the boring, hard, safe parts are already done.

MISO STACK · EST. 2026

04

git push → live

  1. 01

    push. Connect a repo or push an image. No Dockerfile gymnastics, no YAML cliffs.

  2. 02

    build + scan. We build, then scan for leaked keys and open data. It blocks only on critical.

  3. 03

    live. An HTTPS URL on *.misoapp.run, sandboxed from the first request, on a bill that never grows on its own.

terminal
$git push miso main
building proj/web ...
scan ok 0 critical
deployed web.misoapp.run
usage 0% of plan
> _
05

Data & backend

today

Postgres is the easy part

One command gives you a managed Postgres. The connection string is stored as a secret and wired straight into your service. Automated backups run on a schedule, and a restore lands in a fresh instance, proven by an actual restore, not a promise.

terminal
$miso db create --attach web
next

The whole backend, next

Once the deploy core is solid, your database grows a backend: an API, auth for your app's users, and the rest, all from the same console. Shipped in order, never promised before it is ready.

  • Auto REST API from your schema
  • Built-in auth for your app's users
  • Row-level security
  • Realtime row changes
  • Object storage + buckets
  • Scheduled jobs + cron
  • Edge functions
06

Regions

We open in us-east and add regions as real demand shows up. Every code on this list is either live or honestly marked as planned, never invented to pad a map.

region
us-east
north america
launch region · 01/06
07

Pricing

BUILDER
$5/mo

$5 a month, flat. A monthly usage allowance sized for a real small app, a live usage bar, and alerts you set during onboarding. Idle apps sleep, so a parked project barely touches it. The bill never grows on its own: extra usage exists only if you turn it on and give it a limit.

  • 1 project, deploy from git or an image
  • 1 managed Postgres, automated backups
  • git push deploy + a preview URL per PR
  • pre-deploy security scan
  • secrets, HTTPS, logs, one click rollback
  • live usage bar + alerts from onboarding
pro.cfg
PRO
$29/mo

For when your app gets real. $29 a month, flat, with a much bigger allowance. Always-on workloads, more services per project, and priority support. Same rule: the bill never grows on its own.

  • everything in Builder
  • a bigger monthly allowance
  • always-on workloads, no idle sleep
  • more services per project
  • priority support
switch.cmpcategories, not names
one click hostsbig cloudsmiso
your maximum billgrows with usagegrows with usage, alerts onlyflat. grows only by your say-so
secret + access scan before deploybring your ownbring your ownbuilt in, on by default
first deployone click, minutesIAM, VPC, YAML. hours, sometimes daysgit push, minutes
who babysits the infrasharedyou dowe do

The bill never grows on its own. Hit your allowance and each service follows the action you chose: web services stop, databases never do, and with extra usage on, everything keeps running up to the limit you set. Running something bigger than Pro? Talk to us.

08

FAQ

What happens if I hit my plan's usage limit?

You decide, per service. Without extra usage, web services stop and come back when the month resets or you upgrade; databases are never stopped by a limit, because stopping a database is how you lose data. With extra usage on, everything keeps running until the extra limit you set. You see the usage bar from day one and set alerts during onboarding, so the limit is never a surprise.

What can I deploy?

Anything that runs in a container: backends and APIs in Node, Python, Go, Ruby, or PHP, plus static front ends. Connect a git repo or push an image; we build it and hand back an HTTPS URL on *.misoapp.run.

Is a database included?

Yes. Builder includes one managed Postgres with automated backups. The connection string is stored as a secret and wired straight into your service.

What does the pre-deploy scan check?

Leaked keys and obviously open access, the two failures that actually burn AI-built apps. It runs off the hot path and blocks a deploy only on high-confidence critical findings. A pass is not a full security audit.

When do I get access?

We are in private beta, onboarding the first 100 builders from the waitlist in order. Claim a spot and we email you when yours opens.

Do I pay anything today?

No. Joining the waitlist is free. Your plan price starts only when you onboard and deploy.

Why should I believe the $5 number?

Because the bill cannot grow on its own. $5 is the price; the only ways to ever pay more are picking a bigger plan or switching on extra usage with a limit you set yourself. Idle apps sleep, so a parked project barely touches its allowance.

How does extra usage work?

Like the extra usage on your AI coding plan. It is off by default. Switch it on, set a monthly limit in dollars, and past your plan's allowance the metered rates printed in the console apply, never beyond your limit. Your bill cannot grow without you having set that limit yourself.

What if I need more than the Pro plan?

Tell us what you are running and we will size a plan with you. Every plan keeps the same rule: the bill never grows on its own, and the limits stay yours to see and set.

Can I use my own domain?

Yes. Add a custom domain and the TLS certificate is issued automatically. The default *.misoapp.run URL keeps working alongside it.

Test it with us. You pick the ceiling.

Onboarding the first 100 builders. Tell us what you’d deploy.