Platform

StackBlaze is an all-in-one deployment platform. You compose services and databases on a project canvas, deploy from Git or a Docker image, and get private networking, TLS, volumes, and observability without operating a cluster.

You work in the dashboard (or MCP / the API). You do not write Kubernetes manifests or run kubectl.

How a deploy works

1. Add a service on the canvas from GitHub, a Docker image, a template, or an import.
2. Stage and deploy. The change sits on the canvas until you deploy.
3. Build. StackBlaze clones the commit (or pulls the image). A Dockerfile wins; otherwise Nixpacks detects the runtime.
4. Rollout. A new revision comes up behind a health check, then traffic moves over.
5. URL. Generate a *.stackblaze.app domain or attach a custom domain.

Every push to the connected branch can auto-deploy. Add [skip ci] to a commit message to skip.

Mental model

Piece	Role
Project	Canvas of services that share a private network per environment
Service	Git, image, cron, or database
Environment	Isolated copy of the canvas (production, custom, PR preview)
Variables	Config and secrets, including fromDatabase
Volume	Disk attached to one service

See The Basics.

Regions

A project is pinned to a region. Default tenant region is us-east-1. Services in the same environment talk over private DNS; they do not cross projects on that network.

Migrate and compare

Migrate from HerokuMove the app, config vars, and add-ons with minimal downtime.

Compare to RailwayCanvas, services, and environments — on Kubernetes with tenant isolation.

Compare to HerokuGit deploys without dyno sleep.

Compare to RenderOne service model instead of a catalog of product types.