From a GitHub repository to a running app.

VIBSL builds your app, checks it on request, and runs it with rollback. This page covers each step.

VIBSL detects the framework from the repository.

Sign in with GitHub and pick a repository. Detection reads package manifests and repository contents to propose a framework and build settings you can adjust.

Access
Read-only access to the repositories you select.
Detection
Framework and build settings, before the first build.
Override
Your own Dockerfile takes precedence when present.
  • Next.js
  • Nuxt
  • Astro
  • Svelte
  • React
  • Django
  • FastAPI
  • Flask
  • Laravel
  • Ruby on Rails
  • Go
  • Rust
  • Spring Boot
  • .NET
  • Node.js
  • Bun
  • Deno
  • Elixir
  • PHP
  • Python
  • Kotlin
60+ frameworks across 16 ecosystems

Each build runs in a temporary container.

The workspace is destroyed after the build. Image, logs, and deploy record remain; your source tree does not.

A cache shared across branches keeps a small change from rebuilding everything.

How the checks work
The stages of a build and what each one leaves behind
Stage What happens What remains
Clone Read-only checkout into a temporary container. Nothing
Detect Framework and build settings confirmed. Build settings
Build Source becomes a container image. Image and logs
Security scan SBOM, vulnerability, and secrets scans, when enabled. Results
Record Workspace destroyed. Deploy record written. Deploy record

Containers stay on, with logs and rollback on every plan.

Every deploy gets a live URL on the VIBSL managed runtime. Containers stay on, so there are no cold starts.

Containers per plan
2 / 10 / 25 / custom Free, Pro, Team, Enterprise. PR previews count as containers.
Largest container
0.2 vCPU 256 MB to 2 vCPU 4 GB Custom sizes on Enterprise.
Static sites
3 on Free, unlimited from Pro Covered by the flat plan fee.
Dev Postgres
5 GB / 10 GB / 20 GB One database per plan, custom on Enterprise.
Custom domains
3 / 25 / 100 / unlimited A managed certificate on every domain.
Build minutes
500 / 5,000 / 25,000 a month Custom on Enterprise.

Domains and TLS

Every deploy gets a vibsl.app subdomain with TLS. Attach your own with one CNAME (subdomain) or a TXT and A record (apex).

Logs

Build and runtime logs stream live, scoped per environment.

Rollback

Roll back to the previous release from the dashboard, no rebuild.

Compare every plan limit

Two agents step in when something fails.

On a failed build, the Build agent reads the log, explains the likely cause, and can open a pull request with a fix. On a failed rollout, the SRE agent rolls back and writes up the incident. Nothing merges without your review.

  1. Build fails Build log

    Dependency installation did not complete.

  2. Diagnose Build agent

    Reads the log, names the likely cause.

  3. Propose Build agent

    Opens a pull request with the fix and reasoning.

  4. Review You

    Merge, edit, or close it.

Build agent

  • Diagnoses the failed build from the log
  • Opens a pull request with the fix and the reasoning
  • Handles dependency, runtime version, and container configuration issues it recognizes

SRE agent

  • Watches health checks and error rate after a release
  • Rolls back to the previous release on a failed check
  • Posts the incident to Slack and files the issue in Jira

Managed cloud on every plan. Your Azure subscription on Enterprise.

The managed runtime needs no cloud account. Enterprise deploys the same pipeline into your own Azure subscription, inside your boundary.

VIBSL managed cloud

Every plan

  • No cloud account to configure
  • Free plan needs no card
  • Push images to your own ACR from Team
Get started free

Your Azure subscription

Enterprise

  • Same pipeline and dashboard
  • Containers run in your subscription
  • Contract SLA and named support
Talk to us about Enterprise

Deploy your own repository.

Deploy on the free plan, or book a short call for a walkthrough.