Skip to content
Log inLaunch your app
VIBR DeployEarly access

Repository to production.

Connect a GitHub repository, pick a branch and a node. VIBR builds the image, starts it next to the running release, checks its health, issues HTTPS and only then moves traffic.

Private beta supports public repositories directly and private GitHub repositories through a connected account.

Launch your app Read the deploy guide
The pipeline

Every deploy follows the same steps.

You see each step in the control panel. If a step fails, VIBR tells you which one and why.

  1. Preparing node — Complete
    The deploy job is picked up by the VIBR Agent on your node.
  2. Delivering source — Complete
    VIBR streams the selected GitHub branch through the control plane to your node. Private GitHub credentials never need to live on the node.
  3. Building image — Complete
    Your Dockerfile, or a generated one for Node.js apps.
  4. Starting container — Complete
    The new release starts beside the current one.
  5. Health check — Complete
    The new release must answer before anything else changes.
  6. HTTPS — Complete
    VIBR configures routing, then certificate state is verified separately before the dashboard marks HTTPS healthy.
  7. Live — Complete
    Traffic switches. The previous release is retired.

Built so a bad release can’t take you down.

Health-gated traffic switch

A release that fails its health check is removed. Your current release keeps serving.

Environment variables, kept secret

Secret values are write-only in the UI. Changing one replaces it — it is never shown again.

Your domain, with HTTPS

Use a VIBR subdomain or connect a domain you already own.

Release history

Rollback: soon

Every deploy records its release and the one before it.

Ship your next release on your own server.

Launch your appSee pricing