VoidZero open-sources Void so companies can host vibe-coded apps on Cloudflare

What VoidZero released

VoidZero announced Void in a Cloudflare blog post on 15 October 2026 by Christoph Nakazawa and Michael Dong. The company makes Vite, Vitest, Rolldown and Oxc, which it bundles as the Vite+ toolchain. The post says those tools “have made frontend development faster, but building full-stack applications requires more than just a tooling stack,” and introduces three open-source products to cover the rest.

Void SDK is a composable JavaScript SDK for building full-stack apps with Vite. Void CLI provisions resources and deploys Vite apps to Cloudflare. Void Platform is a shared deployment environment that a company hosts for its teams. All three ship as a single package and Vite plugin, installed with npm install void.

The code is in the voidzero-dev/void repository under the MIT license, with Cloudflare as copyright holder. The npm package's latest version when AI Lookout checked was 1.1.11, published about an hour before the blog post. VoidZero says it has used the SDK, CLI and platform “in production at VoidZero for the past several months.”

The problem Void is aimed at

VoidZero says it first planned Void as a single private platform for all users. After the team joined Cloudflare, it changed course and open-sourced the platform so anyone can install it, because it saw a growing need: “companies want to encourage vibe-coded internal apps, but are concerned about security and do not want to give cloud access to every employee.”

That is a real tension inside many companies now. Coding agents let a designer, an analyst or an operations lead build a working dashboard in an afternoon, but turning it into something colleagues can open usually means a cloud account, credentials and an engineer to set them up. Void's answer is a platform the IT or platform team installs once, with approved users connecting to it from the CLI.

Google is attacking a consumer version of the same problem: Google Play now runs private vibe-coded Android apps built in AI Studio without a developer account. Void targets the workplace and the web, where the question is less about app stores and more about who controls the servers and data.

How the Void SDK works

The SDK is added as a Vite plugin. According to the post, it ships adapters for UI frameworks such as React and Vue, and the README adds Svelte and Solid. It provides file-based API routes, pre-rendering, caching, islands and end-to-end type safety, so the type of a database query carries through to the page component that displays it. Every feature is optional, and Void can sit alongside Vinext, React Router, SvelteKit, Nuxt, TanStack Start and Astro, using Hono for resource APIs and Better Auth for authentication.

The more unusual part is inferred infrastructure. Importing void/db gives the app a local database in development, and void deploy provisions a Cloudflare D1 database in production. Importing void/ai wires the app to models through Cloudflare's AI Gateway. Developers, or their agents, write code; Void works out which bindings the app needs and creates the databases, queues or AI resources during deployment.

The blog's AI example is a yes-or-no endpoint that calls Cloudflare's Clef decision model and returns a probability. The post also highlights a React router built for transitions and Suspense, so navigation stays responsive on slow networks. Apps that do not need the team platform can deploy straight to the developer's own Cloudflare account.

The CLI and coding agents

The CLI is described as “the main interface for Void.” It is built on Cloudflare's new cf CLI and, in the post's words, “works well with agents.” On first run, void deploy asks the user to log into Cloudflare; after that it builds the app with Vite, applies database migrations, provisions resources and deploys, printing the live URL. The same tool reads logs, inspects deployments and rolls back, which is what lets an agent handle an app's whole lifecycle.

Void's coding-agent guide shows how deliberate that is. Running void init adds a minimal AGENTS.md to new projects and asks before editing an existing one. The complete Markdown documentation ships inside the package, and Void provides two agent skills: one for app development and one for migrating apps from Cloudflare's existing Vite plugin. They are linked automatically for agents it detects, such as Claude Code and Codex, and point to the docs for the installed version so guidance does not drift.

What it takes to run a Void Platform

A company that wants the shared platform installs it in its own Cloudflare account. The self-hosting guide and blog list the requirements: a Cloudflare account with Workers for Platforms and R2 enabled, a PostgreSQL database, an account with a login provider and a domain for the apps. Users then run void connect with the platform's address and deploy as normal.

Admins control who can deploy, set resource limits, and inspect deployments and usage through the CLI or an admin dashboard. The core installation supports GitHub, Google, generic OIDC and Cloudflare Access sign-in, CLI deploys, D1, KV, R2, Queues, cron jobs, Workers AI, WebSockets, logs and rollback, and includes managed sandboxes and an email gateway. Sandboxes need a paid Workers plan.

Some features are not in the core install: the user dashboard, GitHub builds and webhooks, build containers and custom domains for individual apps. VoidZero says the platform can be forked, adapted to company systems or made “to work on other deployment platforms,” but the shipped version is built on Cloudflare's multi-tenant Workers for Platforms product.

Where Void fits in Cloudflare's plans

Cloudflare announced on 4 June 2026 that VoidZero was joining Cloudflare, promising that Vite, Vitest, Rolldown, Oxc and Vite+ would stay open source, vendor-agnostic and community-driven, and that Vite apps would keep running anywhere. Void is different by design: it is openly licensed, but its job is to make deploying a Vite app to Cloudflare as short as one command.

It fits a pattern of Cloudflare buying developer communities and pointing them at its runtime. Astro joined earlier in the year, and in October Deno's team joined Cloudflare to make Workers and Durable Objects self-hostable. Together they suggest Cloudflare wants the tools developers and their agents reach for first to end in a Workers deployment.

Limits and open questions

Void is new. The repository had about 20 GitHub stars when AI Lookout checked on launch day, and the post gives no adoption figures beyond VoidZero's own use. It does not discuss pricing, which depends on the Cloudflare services an installation uses. A platform also governs where vibe-coded apps run, not whether their code is safe; it does not review what an agent wrote. Teams still need the sandboxing, review and data rules they would apply to any internal tool.

Portability is the other caution. Void's SDK features map to Cloudflare products such as D1, R2, Queues and AI Gateway, so an app that leans on them is not trivially moved elsewhere, whatever the license. VoidZero asks for feedback through Discord and GitHub. Teams interested in it should start with a direct deploy to a test account before installing a shared platform, and decide who may connect to it.