A PocketBase-compatible backend on Cloudflare: PocketBase's API and admin panel on D1, R2 and Durable Objects, built on Void. An independent project, not affiliated with PocketBase.
Developer toolsTypeScript · JavaScriptGitHub @voidbase-cloudOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
PocketBase-compatible backend on Cloudflare Workers (D1, R2, Queues, Durable Objects) via Void, or a single Bun process
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
This repository is a Bun workspace. Every package it publishes carries the same version:
bunfig.toml pins linker = "hoisted". The CI and release scripts call binaries out of the root's
node_modules/.bin by path (wrangler, void, vp, commitlint, tsc), and several of those come from void
and vite-plus transitively; the isolated linker, which Bun switches to on its own once `packagRead the full README ↗This repository is a Bun workspace. Every package it publishes carries the same version:
| path | what |
|---|---|
packages/voidbase | @voidbase-cloud/voidbase, the core package, and the Void app this repository runs to test it. Its README is the project's. |
packages/plugin-* | the tier 1 plugins the core ships (auth, observability, realtime, hardening, backups, openapi, mail) and the tier 2 plugins installed from the marketplace (stripe, polar, lemonsqueezy, tax-flat, shipping-flat, commerce), each manifest.json beside main.js. The tier 3 plugins live in repositories of their own: ai, mcp, seo, translations, previews and domains, tested against @voidbase-cloud/voidbase/testing. |
scripts/ | this repository's CI and release tooling (ci.sh, release.sh, pipeline.ts and the rest). It is not published: consumers used to download it with every install. |
ci/ | the status Worker a build deploys (docs/ci.md). |
surface/ | the surface map, rendered by bun run surface. |
bun install # also installs the git hooks
bun run check # codegen and every typecheck pass: the package's two configs and the root's scripts config
bun test # the unit tests
bun run dev # the app in packages/voidbase
bun run ci # the whole CI flow, the way Cloudflare runs it
bunfig.toml pins linker = "hoisted". The CI and release scripts call binaries out of the root's
node_modules/.bin by path (wrangler, void, vp, commitlint, tsc), and several of those come from void
and vite-plus transitively; the isolated linker, which Bun switches to on its own once package.json names
workspaces, leaves the root with only its own declared devDependencies and none of those binaries.