Advanced concepts
Most services run with Nixpacks (or a Dockerfile) and a single replica. These are the knobs you change when that is not enough.
Build and deploy
Section titled “Build and deploy”Open the service sheet → Settings.
Build
- If a
Dockerfileis in the service root, it wins. Otherwise Nixpacks detects the runtime. - Override install / build / start when detection is wrong.
- Monorepos set a root directory so one repo can back several services.
Deploy
- Replicas for more than one instance.
- Autoscaling from CPU or memory.
- Cron if the process should run on a schedule and exit.
- Health checks so traffic waits for a ready revision.
- Staged changes apply a batch of canvas edits at once.
There is no serverless sleep product on this control plane. Services stay up unless you scale them to zero or delete them.
Networking
Section titled “Networking”- Private — service name DNS inside the environment. See private networking.
- Public — generate a
*.stackblaze.appdomain or attach your own. See public networking. - TLS is issued after DNS checks out. See SSL.
Environments
Section titled “Environments”Production is created with the project. Add more environments for staging. Pull requests can get a preview environment that does not share production data.
Observability
Section titled “Observability”Logs, metrics, and traces are Coroot, opened from the service. Search logs from the dashboard or MCP (search_logs).
Config as code
Section titled “Config as code”stackblaze.yaml can describe the project. Plan and apply when IaC is enabled. See config as code.