Auth
AuthProvides auth@1, mounting password, OAuth2, OTP, MFA and passkey sign-in and answering who a request is
Each plugin listed here is a repository, or a directory of one, at a commit a maintainer approved: audited, and recorded under /registry/v1/ the way the registry protocol says, which any marketplace can serve and any instance can read. The marketplace builds nothing and hosts nothing of a plugin: an instance installs one with voidbase plugins add <name>, fetches that commit, pins its files by hash in the project's voidbase.lock and assembles it as it is. A listing without a release is a registration.
Provides auth@1, mounting password, OAuth2, OTP, MFA and passkey sign-in and answering who a request is
The archive routes, two archive kinds, verified after the write and restorable
Provides hardening@1, the body limit, the rate limit, the response policy and GET /api/csrf
Provides mail@1, the instance's own domain through Cloudflare Email Service
Provides observability@1, the sampled request path and the summary behind the superuser
The instance's own OpenAPI document and the reference that renders it
Provides realtime@1, the hub client for a request's bindings
The stripe plugin of voidbase. Taking money through Stripe: provides payments@1 with Stripe's REST API, its signed webhooks and the shared payment rows
The polar plugin of voidbase. Taking money through Polar: provides payments@1 with Polar's REST API, its Standard Webhooks and the shared payment rows
The lemonsqueezy plugin of voidbase. Taking money through Lemon Squeezy: provides payments@1 with its JSON:API, its signed webhooks and the shared payment rows
The flat-rate tax plugin of voidbase: provides tax@1, one percentage on the order's subtotal
The flat-rate shipping plugin of voidbase: provides shipping@1, one rate from two knobs, free over a threshold
A shop that requires payments@1, tax@1 and shipping@1 rather than particular plugins
Answers questions about the instance's own data: a chat endpoint, conversations kept as records, and the instance's MCP tools to read and write rows
Makes the instance an MCP server whose tools come from its own OpenAPI document: the collections that exist, with the fields the caller may read
What a crawler and a link preview need, written from the records: meta tags for a page, a sitemap of opted-in collections, and a share card per record
A field is declared translatable once and the records API answers in the locale the request asks for
What an instance knows about being a preview: which of the two shapes it is in, which branches have rows on it, and the route that removes their rows
Reports where an instance answers: VOIDBASE_DOMAINS, the hostnames a deploy attached, and VOIDBASE_CANONICAL_DOMAIN, where the others redirect