Introduction

StackBlaze is a developer cloud that runs your applications on Kubernetes, without making you think about Kubernetes.

What is StackBlaze?

StackBlaze is a platform-as-a-service (PaaS) built on top of Kubernetes. It gives teams the simplicity of Heroku with the power and reliability of a modern container orchestrator. You connect a GitHub repository, configure a start command, and StackBlaze handles the rest: building a Docker image, pushing it to a private registry, scheduling it onto a cluster, wiring up a TLS-terminated URL, and keeping it running.

Every app on StackBlaze is a Kubernetes workload under the hood, but you interact with it through the dashboard — not YAML manifests. Automation uses the REST API, stackblaze.yaml, or MCP. There is no npm CLI on this control plane.

How it works

The deploy lifecycle looks like this:

This animated walkthrough shows a deploy from git push to a live URL: the deploy feed, build logs streaming live, then the app opening in a browser on its public URL.

1. Connect your repo. Authorize StackBlaze via GitHub OAuth. Select the repository and branch you want to deploy.
2. Auto-detect runtime. StackBlaze scans your repository for a Dockerfile, package.json, requirements.txt, and other markers to determine how to build and run your app.
3. Build. Your code is cloned into an ephemeral build container. Dependencies are installed, your build command runs, and the resulting image is pushed to StackBlaze's private registry.
4. Deploy. StackBlaze rolls out a new revision. New instances become healthy before old ones are terminated, so traffic does not drop.
5. Get a URL. Your app is live at https://your-app.stackblaze.app with a TLS certificate managed automatically.

Tip

Every push to your configured branch triggers an automatic redeploy. Add [skip ci] to your commit message to bypass it.

Apps and add-ons

A project (pipeline) has phases (environments) and apps (workloads). Apps share the same build pipeline and env vars. They differ in how they run and whether they are exposed to the internet. Databases and other data services are add-ons attached to an app or shared on the phase.

Kind	Description	Public URL
Web app	Runs a long-lived HTTP server. Receives public traffic.	Yes
Worker	Runs continuously, no inbound traffic. Typical for queue consumers.	No
Cron	Runs on a schedule (standard cron syntax). Each run is a fresh container.	No
Static site	Built and served from a CDN edge network. No server runtime.	Yes
Add-on	Managed data services such as Postgres (Cluster), Valkey, or MariaDB.	Internal only

Regions

You choose a region when you create a project. The default tenant region is us-east-1. Apps and add-ons in the same phase can reach each other on the private network without extra configuration.

Default region

Region	Location	Code
US East	Northern Virginia, USA	`us-east-1`

Ready to deploy?

Follow the Quick Start guide to go from a GitHub repository to a live URL. Or read Core Concepts if you want a deeper understanding of how projects, phases, and apps relate before you begin.