Frequently asked questions about VIBSL
Learn how deployments work, which security checks you can enable, and when to use your own cloud. Browse answers by topic below.
Platform
- What is VIBSL?
- A secure deployment platform for AI-built and modern apps. Connect a GitHub repository and VIBSL builds it, runs supply chain checks when enabled, ships a live URL, and keeps the previous release ready for rollback. Enterprise can move from the managed cloud to your own Azure subscription when compliance requires it.
- How fast can I deploy with VIBSL?
- Most simple apps are live about a minute after you connect a repository. VIBSL detects the framework, builds the image, runs the checks you enabled, and rolls out, with no deploy scripts or pipelines to write.
Security
- Does VIBSL use distroless container images?
- Yes, where the framework supports it. The production layer uses a slim base image, no shell or package manager, so an attacker has less to work with and scan results match what ships. More frameworks are being added over time.
- What is supply chain aware deployment?
- Each build is checked before it goes live, when you turn the checks on. VIBSL lists the image contents as a software bill of materials, scans for known vulnerabilities and leaked secrets, flags a runtime past end of life, and ships a slim image where the framework supports one. Results stay with the release as exportable evidence, no scanners to wire.
- Does VIBSL store my source code?
- No. The repository is cloned into a temporary build container, built and checked, then the workspace is destroyed. Image, check results, and logs are kept; the source tree is not.
- What security checks can run on a build?
- With scans on, three run before an image promotes: a software bill of materials, a vulnerability scan across OS packages and your dependencies, and a secrets scan. A runtime check also flags a language runtime past end of life; that or a critical finding can hold the release at the gate. Where the framework supports it, the image ships slim, with no shell in the production layer.
- Why does supply chain security matter?
- Because attackers now target the open source packages your app depends on, not just your code. Auditors ask first for a contents list of what shipped; VIBSL can generate one per build when scans are on, so you can show what ran in production.
Cloud and pricing
- Can I deploy to my own cloud (BYOC)?
- Yes, on Enterprise. Start on the managed cloud; when you need your own boundary or have compliance rules to meet, connect your Azure subscription and the same pipeline and dashboard deploy there.
- How much does VIBSL cost?
- Four flat monthly plans, no usage meter: Free $0, Pro $29, Team $149, Enterprise custom. Free needs no card and covers 5 projects, 2 containers that stay on, and a 5 GB database; Pro, an early founding price locked in for life when you subscribe, has unlimited projects, 10 containers, and 25 custom domains. Team has 25 containers and 25,000 build minutes a month; Enterprise adds BYOC on Azure with a contract SLA.
Agents
- What are Build and SRE AI agents?
- They step in when something goes wrong. The Build agent explains a broken build and can open a pull request with a proposed fix for your review. The SRE agent watches the running app, rolls back a bad release, and posts the incident to Slack or files it in Jira.
Ask a question not covered here
Send us a message or book a short call and we will walk through your setup.