Skip to main content

vibeD v0.6.0: Fewer Moving Parts, Fewer Sharp Edges

· 7 min read
vibeD Team
vibeD Team
Core Maintainers

v0.6.0 is a consolidation release. The legacy orchestrator is gone, the API lives entirely under /v1, the hot paths got a performance pass, and we fixed eight reported vulnerabilities. It is also the release where we stopped and asked an uncomfortable question: when a deploy fails, does vibeD actually tell you why?

It did not. That turned out to be the most useful thing we fixed.

A governed home for your citizen developers' AI apps

· 5 min read
Max
Max
vibeD Creator

Something is happening in every company right now: people who aren't professional developers are using AI to vibe-code small tools. A dashboard for their team. A form that writes to a spreadsheet. A scraper that watches a supplier's price page. The tool works and then it lives on a laptop, or gets pasted into some third-party host with a company API key baked into it.

That's the classic shadow-IT problem, except now it happens at AI speed and in far greater volume. The instinct is to lock it down. But telling a motivated employee "no" just pushes the tool somewhere you can't see. The better answer is to give that app a place to land, self-hosted, isolated, governed spot that's so fast and easy it beats the laptop.

That's the problem vibeD exists to solve.

vibeD v0.4.x a Governance, a Build-Free Core and Extension Points

· 5 min read
vibeD Team
vibeD Team
Core Maintainers

v0.3.1 was about speed, to bring an AI-generated app to a live URL in seconds, never building a container on the deploy path. The whole v0.4 line has been about everything around that hot path: making vibeD defensible, lean and extensible, without ever slowing the "the model wrote it, it's live" loop.

Here's what actually landed across v0.4.0 → v0.4.3.

vibeD v0.3.1: A Two-Lane microVM Rewrite

· 5 min read
vibeD Team
vibeD Team
Core Maintainers

v0.3.1 has some larger architectural changes and let me rethink the approach. I had to rebuilt the engine. The old build-and-deploy model (build a container image with Buildah, hand it to Knative) is gone, replaced by an architecture designed around a single goal: get an AI-generated app to a live URL in seconds, with hardware-grade isolation, and never build a container on the deploy path.

The idea for vibeD

· 5 min read
Max
Max
vibeD Creator

AI is taking its place: in work, in private life, and everywhere in between. With this comes a couple of challenges: many are already in sight, others we can't yet imagine.

For corporates and businesses, an AI-enabled employee gains the capability to create artifacts like websites, apps, and more. Right now, these creations are either running within the context of the provider tool (a desktop app, a browser tab) or are clumsy to deploy, requiring support from an IT expert who understands containers, Kubernetes, and CI/CD pipelines.

vibeD enters the stage.

The idea of vibeD is to provide an endpoint for any GenAI tool to deploy artifacts under your own conditions, in a controllable environment. No deployment competencies needed for your non-IT personnel. Extensible, secure, and built on standards.