Frequently asked questions
Deploy speed, the security checks on every build, and running on your own cloud. If your question is not here, come talk to us.
- What is VIBSL?
- VIBSL is the secure deployment platform for AI-built and modern apps. Connect a GitHub repo. We build, run supply-chain checks, ship a live URL, and keep rollback ready. Start on our cloud. Move to your own Azure account when compliance demands it.
- Does VIBSL use distroless container images?
- Yes. For production, we build on tiny base images with nothing extra in them, including no shell. That gives attackers less to work with and keeps security scans clean. We're adding this to more frameworks over time.
- What is supply-chain aware deployment?
- It means every scanned build gets checked for security problems before it goes live. We list what's inside your app, scan it for known vulnerabilities and leaked secrets, flag anything running on an outdated base, and ship on slim images. You get evidence you can export, without wiring scanners yourself.
- Can I deploy to my own cloud (BYOC)?
- Yes. Start on our shared cloud. When you need your own isolated setup or have compliance rules to meet, connect your own Azure account and run there instead. Support for AWS and Google Cloud is coming.
- How fast can I deploy with VIBSL?
- Most simple apps are live in about a minute after you connect a repo. We work out the framework, build it, check it when scans are enabled, and roll it out. You don't write any deploy scripts or pipelines.
- Does VIBSL store my source code?
- No. We pull a copy of your repo into a throwaway container, build and check it, then delete that workspace. We keep the results of the build, like the image, the security scan, and the logs. We don't hold onto your code.
- What are Build and SRE AI agents?
- They're the agents that step in when something goes wrong. If a build breaks, the Build agent explains why and opens a pull request with a fix. That's live today. The SRE agent watches the app after it goes live. It can roll back a bad release and post about incidents in your chat or ticket tool; those parts are still rolling out.
- What security checks can run on a build?
- When you turn scans on, three checks can run before an image promotes: a software bill of materials, a vulnerability scan across the OS and your dependencies, and a secrets scan. A critical finding or a past-end-of-life runtime can stop the release at the gate. Where the framework supports it, the final image is also slimmed down, with no shell in the production layer.
- How much does VIBSL cost?
- There are four plans, all flat monthly fees with no usage meter. Free is $0 with no card required and covers 5 projects, 2 always-on containers, and a 5 GB database. Pro is $29 a month (an early founding price locked in for life) with unlimited projects, 10 containers, and 25 custom domains. Team is $149 a month with 25 containers and 25,000 build minutes a month. Enterprise is custom and adds bring-your-own-cloud on Azure with a contract SLA.
- Why does supply-chain security matter?
- Because attackers now target the open-source packages your app depends on, not just your own code. A contents list of what actually shipped is what auditors ask for first. VIBSL can generate one when scans are on, so you can prove what ran in production.
Still have a question?
Send us a message or grab a short call. We are happy to walk through your setup.