Skip to main content

Draft the config

Local, about two seconds. Writes a draft supersonic.json and then names what it could not determine. Treat those lines as the work: they are the questions no file in your repository answers.

Check it

Resolves the file exactly as a deploy would and prints the command each phase runs. Non-zero exit on any problem. No cloud touched.

Ship it

A URL immediately, the build streamed. Without --wait the command returns and the build carries on behind the URL.

​
What you never have to write

A Dockerfile

The build is planned from your manifests. You may still supply one — dockerfile in the service — and Bay will use it instead.

A database URL

Import the driver. The dependency is the declaration; the credentials are injected under every name your stack is likely to read.

A port

Bind to $PORT. Everything in front of it — TLS, the load balancer, the router — is already there.

A CI pipeline

Connect the repository and a push is a build. See Shipping from GitHub.

​
Monorepos

One app, one hostname, services split by path:
Same origin means no CORS, and no API base URL to bake into a frontend bundle at build time.