Miso Stack.
PLATFORM / DEPLOYS

Git push. Get a URL. That is the whole job.

The deploy loop is the habit the whole category runs on, so it is the core of Miso, not a later add-on. Push your code and a live, shareable URL comes back in minutes.

build 1.8sregion us-eastscan passpreview per PRrollback 1 click
  1. 01

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

  2. 02

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

  3. 03

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

  4. 04

    Rollback. Every deploy is reversible. One click puts the last good build back in front of users.

terminal
$git push miso main
building proj/web ...
scan ok 0 critical
deployed web.misoapp.run
usage 0% of plan
> _
deploy.cfg
deploy time
0.0s
p95 build→live
previews.cfg
PR previews
0
live preview URLs
build.run
build progress

The scan runs off the hot path, so a deploy is never stuck waiting on it.

0%building
rollback.log
currentweb@a1b3
previousweb@9f2e
rollbackone click
historykept per service
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
> _
git push → livea preview URL on every PR
from your AI tool

Deploy without leaving the chat

An MCP server exposes the same loop, so the agent in your AI editor can deploy, attach a database, set a secret, read logs, and roll back, all from inside the tool you already build in.

mcp.server
› deploy_project
› create_database
› set_env_var
› get_logs
› rollback
> _