Getting Started
Connect a GitHub repository
Connecting a GitHub repository is the first thing you do when adding a service to StackBlaze. Under the hood, StackBlaze registers a webhook on your repo, then provisions a Kubernetes Deployment and Service in your project namespace. Every push after that flows through the build pipeline and ends with a rolling update that replaces pods one by one, no downtime.
You never write a Kubernetes manifest. StackBlaze synthesises one from the settings you configure in the dashboard, keeping your infrastructure version-controlled on its side.
What StackBlaze detects
› Cloning github.com/acme/api-service
› Detected Node.js 20 (package.json)
› Detected TypeScript project
› Build command → npm run build
› Start command → node dist/index.js
› Port → 3000 (from PORT env var)
› ✓ Webhook registered on acme/api-service
› ✓ First build queued
Deploy pipeline
Under the hood
When you deploy a web service from GitHub, StackBlaze creates three Kubernetes resources in your project namespace:
- Deployment: manages the pod replicas running your container image. Rolling updates replace pods one by one so traffic never drops.
- Service: exposes the Deployment on a stable internal DNS name so other services in your project can call it over the private network without going through the public internet.
- Ingress: routes HTTPS traffic from your public URL (and any custom domain you attach) to the Service, with TLS termination handled automatically.
Step by step
Connect your GitHub account
Click "Add Service" in the dashboard and choose GitHub. You'll be redirected to GitHub's OAuth page where you authorise StackBlaze to read your repositories. StackBlaze requests the minimum required scopes: read access to code and the ability to install webhooks.
Select a repository
After authorisation you'll see a list of all repositories you own or have been granted access to. Pick the repo you want to deploy. StackBlaze immediately clones a shallow copy and analyses the project structure to detect the framework and runtime.
Review auto-detected settings
StackBlaze inspects your package.json, Dockerfile, or Procfile and suggests a build command, start command, and runtime. For a typical Node.js project it detects "npm run build" and "node dist/index.js" automatically. You can override any field before proceeding.
Click Deploy
Hit Deploy and StackBlaze triggers the first build. A webhook is registered on your repository so every future push to the default branch (or any branch you configure) triggers an automatic rebuild and deploy with zero downtime rolling update.