Skip to content
StackBlazeDocs

Quick start

StackBlaze is a deployment platform. You provision infrastructure on a project canvas, develop against that infrastructure, and deploy from Git, a Docker image, the CLI, or a template.

This guide covers two ways to get going:

  1. Deploying your project — bring your code.
  2. Deploying a template — pre-wired software from the catalog.

Deploying your project — from GitHub

Section titled “Deploying your project — from GitHub”
  1. Open the dashboard → New project.
  2. Choose Git repository. Link GitHub if prompted, then pick the repo and branch.
  3. The service is staged on the canvas. Review the changeset and click Deploy (or deploy immediately if the flow offers it).

You land on the project canvas. StackBlaze clones the commit, builds with Nixpacks (or your Dockerfile), and rolls the service out. When the deployment is healthy, generate a *.stackblaze.app domain from the service.

If the build fails, open Logs on the service and scroll the full build log — the useful error is often not the last line.

Deploying your project — with the CLI

Section titled “Deploying your project — with the CLI”

Install, then from your app directory:

Terminal window
curl -fsSL https://stackblaze.com/install.sh | sh
stackblaze login
stackblaze init
stackblaze up

init creates a project (or links this folder to one). up uploads the repo and starts a git build. Then:

Terminal window
stackblaze open

That prints the canvas URL. CI: stackblaze up --ci streams NDJSON and exits when the build finishes. See CLI.

Deploying your project — from a Docker image

Section titled “Deploying your project — from a Docker image”
  1. New project (empty canvas).
  2. + Service → Docker images.
  3. Paste an image such as ghcr.io/org/app:tag (Docker Hub, GHCR, GitLab, and Quay work). Use the full URL for anything that is not Docker Hub.
  4. Deploy.

The process must listen on PORT. Private registries need credentials on the service.

The canvas

Section titled “The canvas”

GitHub, CLI, Docker, and templates all end on the same project canvas. This is mission control: services, databases, environments, variables, and staged changes.

Click a tile for source, variables, networking, volumes, metrics, and logs. + Service adds Git, Docker, templates, databases, or an import (Compose / render.yaml / fly.toml).

Deploying a template

Section titled “Deploying a template”
  1. New project → Templates, or + Service → Templates on an existing canvas.
  2. Search the catalog.
  3. Fill in any prompted values.
  4. Deploy.

The canvas provisions every service and database the template defines.

What to explore next

Section titled “What to explore next”