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).
VIBSL builds your app, checks it on request, and runs it with rollback. This page covers each step.
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.
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| 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 |
Every deploy gets a live URL on the VIBSL managed runtime. Containers stay on, so there are no cold starts.
Every deploy gets a vibsl.app subdomain with TLS. Attach your own with one CNAME (subdomain) or a TXT and A record (apex).
Build and runtime logs stream live, scoped per environment.
Roll back to the previous release from the dashboard, no rebuild.
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.
Dependency installation did not complete.
Reads the log, names the likely cause.
Opens a pull request with the fix and reasoning.
Merge, edit, or close it.
The managed runtime needs no cloud account. Enterprise deploys the same pipeline into your own Azure subscription, inside your boundary.
Every plan
Enterprise
Deploy on the free plan, or book a short call for a walkthrough.