Module 07 of 18 · Ship

Deploy and hosting

Going live where you already have an account: Vercel, Cloudflare or Fly.io, with Netlify, AWS, GCP and Azure in beta. Before anything ships it is scanned, and a secret key in the code stops the release and says where it is. Publishing is an outward step, so it always waits for your yes. Afterwards Neo watches the deploy status and the errors.

You say
“Put the bakery site live.”
Neo · Deploy and hosting
Getting it ready
0/3
Production build
Scanned for secret keys
Opened in a real browser

A recreated panel in the style of the app: how a turn in this module goes, built only from what the module really does.

What you can do with it

4 things you can do with it.

VercelCloudflareFly.ioNetlify (beta)AWS (beta)

Your hosting

Vercel, Cloudflare or Fly.io. Netlify, AWS, GCP and Azure are in beta.

Build
Secret scan
Browser check

A scan before every release

A secret key in the code stops the release and says where it is.

Publish to Vercel
Waits for your yes
Approve

Your yes, once

Publishing waits for you, and your approval is tied to that exact call.

Tell me if the site goes down.

Watched after launch

Deploy status and error monitoring, and a watcher that checks the site is up.

You say…

Plain words in the one chat.

“Put the bakery site live.”
“Deploy this to Netlify instead.”
“Check every 15 minutes that my sites are up.”

You never pick the module. Neo reads the request, picks Deploy and hosting, and says why.

What you get at the end

What you hold when it is done.

  • A live link on your own account
  • A release that passed the secret scan
  • Status and errors you can read

Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.