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 service on StackBlaze is a Kubernetes workload under the hood, but you interact with it through a clean dashboard and CLI, not YAML manifests or kubectl commands.

How it works

The deploy lifecycle looks like this:

Diagram: GitHub push flows through build, Kubernetes deploy, and live URL — From git push to a live TLS-terminated URL, StackBlaze handles each step automatically.

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 to Kubernetes. StackBlaze creates or updates a Kubernetes Deployment, Service, and Ingress. A rolling update ensures zero downtime, new pods become healthy before old ones are terminated.
5. Get a URL. Your service is live at https://your-app.stackblaze.app with a free TLS certificate managed automatically via cert-manager.

Tip

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

Service types

StackBlaze supports five kinds of services. All share the same build pipeline and environment variable system, they differ in how they run and how (or whether) they're exposed to the internet.

Type	Description	Public URL
Web Service	Runs a long-lived HTTP server. Receives public traffic via an Ingress.	Yes
Background Worker	Runs continuously, no inbound traffic. Perfect for queue consumers.	No
Cron Job	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
Database	Managed PostgreSQL, MySQL, Redis, or MongoDB with automated backups.	Internal only

Regions

StackBlaze clusters are available in multiple regions. When you create a service, you choose a region. All services within a project in the same region can communicate over private networking (ClusterIP DNS) without any additional configuration.

Available regions

Region	Location	Code
US East	Northern Virginia, USA	`us-east-1`
US West	Oregon, USA	`us-west-2`
EU West	Frankfurt, Germany	`eu-west-1`
Asia Pacific	Singapore	`ap-southeast-1`

Ready to deploy?

Follow the Quick Start guide to go from a GitHub repository to a live URL in under two minutes. Or read Core Concepts if you want a deeper understanding of how StackBlaze is structured before you begin.