BWEZE Docs

Deploy from Git

Push a repo, get a live URL on bweze.app - public repos in one paste, private repos in one connect.

BWEZE deploys your app straight from a Git repository - frontend, full-stack, or API - and serves it on a public bweze.app URL. It's your app, your repo, your workspace: every workspace connects its own GitHub and deploys its own code.

Deploy a public repo

No setup, no connection needed.

  1. In the dashboard, open Deploy.
  2. Paste a public GitHub URL (e.g. https://github.com/you/app).
  3. Pick a build pack:
    • Nixpacks - auto-detects the framework (Next, Node, Python, Go, …) and builds it.
    • Static - a plain SPA / static site.
  4. Click Deploy. In a minute your app is live at https://<name>-<id>.bweze.app.

Choose a service type

On the Configure step, pick what the repo runs as. The type is fixed once the service exists; to change it, create a new service from the same repo.

TypeWhat it isReached at
Web serviceAn HTTP server, public over HTTPS.https://<name>-<id>.bweze.app and your custom domains
Private serviceAn HTTP server only your workspace's other services can reach: an internal API, a cache front.http://app-<name>-<id> from those services
Background workerA process that runs all the time and listens on no port: a queue consumer, a bot.Nowhere: it reaches out, nothing reaches in
Cron jobA command run on a schedule. Nothing runs between runs.Nowhere

Web and private services listen on the port in PORT (3000 unless you set another). Only web services get PR previews and custom domains.

Commands

Every service can set:

  • Start command: replaces the image's own command (CMD), for example node dist/worker.js. A cron job's command is what each run executes.
  • Pre-deploy command: runs once on each new release before it goes live, for example npm run migrate. If it fails, the deploy fails and the release that was live stays live. It is stopped after 30 minutes, and a rollback does not run it again.

Commands run as /bin/sh -c "<command>" after the image's ENTRYPOINT, with the service's environment variables, so the image needs a shell. Change them under the service's Settings; they apply from the next deploy.

Jobs and cron jobs

From a service's Jobs panel you can run a command once on its live release (a database backfill, a one-time script): it gets a new instance with the same image and environment variables, is stopped after an hour, and keeps its logs. Up to three jobs run at once per service.

A cron job's schedule has five fields in UTC (minute hour day-of-month month day-of-week), for example 0 2 * * * for 02:00 UTC (04:00 in Kigali) every day. A run is stopped at its time limit (one hour unless you set another, twelve at most), and a run never overlaps the previous one: if it is still going when the next is due, that one is skipped and listed as skipped.

Jobs, cron runs and pre-deploy commands are billed like the service while they run, for their memory and CPU.

From the CLI and the API

bweze services list <projectId>
bweze services set <serviceId> --pre-deploy-command "npm run migrate"
bweze services set <serviceId> --schedule "0 2 * * *" --time-limit 30m   # a cron job

# Runs on the live release and prints its output; the CLI exits with the command's code.
bweze jobs run <serviceId> -- npm run backfill --since 2026-11-01
bweze jobs list <serviceId>
bweze jobs logs <serviceId> <jobId> --follow
bweze jobs cancel <serviceId> <jobId>

The same through the API: GET /v1/projects/{id}/services, GET and PATCH /v1/services/{id}, and /v1/services/{id}/jobs (spec: https://api.bweze.com/v1/openapi.json). Changing settings needs deployment:update; running or stopping a job needs terminal:exec, since it runs a command with the service's secrets.

Environment variables

Apps usually need config - a database URL, an API key. On the Deploy form, add them under Environment variables, one KEY=VALUE per line:

DATABASE_URL=postgres://…
API_KEY=…

They're available at both build and runtime. To change them later, update and Redeploy.

Deploy a private repo

Private repos deploy through BWEZE's GitHub app - a one-time connection per workspace.

  1. Open Settings → Connect GitHub and install the BWEZE app on your account or org. Grant it the repositories you want to deploy.
  2. Back on Deploy, switch to Private repo and pick a repo from the dropdown.
  3. Click Deploy.

BWEZE only ever uses a short-lived, single-repo token to clone your code - it never stores your GitHub password, and one workspace can never see another's repositories or deployments.

Redeploy, logs, and teardown

Each app in the Deploy list has:

  • Redeploy - rebuild and ship the latest commit.
  • logs - the build output, live while a build runs (so a failed build tells you why).
  • Remove - tear the app down completely.

Auto-deploy on push

Once a private repo is connected, every push to its deployed branch automatically rebuilds and ships the app - no manual redeploy needed.

On this page