bknd

Apache-2.0
Platform
Docker Self-hosted
Licence
Apache-2.0 Open source
Website
bknd.io
bknd

bknd is an open-source backend you run yourself, either as a standalone server or mounted inside your own app. It bundles the parts most projects end up rebuilding: a data layer with visual schema editing, authentication, media storage, an automation engine and an admin interface, all over a database you choose.

It is built on Web Standards rather than a vendor platform, so the same code runs on Node.js, Bun, Deno, Cloudflare Workers, Vercel, Netlify or AWS Lambda and writes to SQLite or Postgres without a rewrite. Every module is opt-in: take the whole backend, or mount just the data API next to an existing frontend.

Key Features

  • Visual admin UI: create entities, fields and relations, browse and edit records, upload media and configure auth from a browser
  • Data API: REST endpoints plus a type-safe TypeScript SDK derived from the schema, with filtering, pagination and relations
  • Authentication: password and OAuth strategies, users, roles and row-level security for multi-tenant data
  • Media and storage: uploads to S3-compatible services, Cloudflare R2, Cloudinary or the local filesystem
  • Flows: event-driven automation that reacts to record changes and calls out to other services
  • MCP server: exposes data, auth and media tools to AI agents over the Model Context Protocol
  • Embeddable: React hooks, prebuilt elements such as upload dropzones and login forms, and an admin route you can mount in Next.js, React Router, Astro or Vite
  • Portable storage: SQLite through libSQL, D1, node:sqlite or Bun, or Postgres, self-hosted or managed

Requirements

Node.js 22.13 or newer for the npm route, because the bundled SQLite driver needs node:sqlite; Bun 1.0 and Deno are also supported. The quickest start is npx bknd run, which serves the API and the admin UI on one port. A Docker deployment and adapters for Cloudflare Workers, Vercel, Netlify and AWS Lambda are documented. The admin UI runs in any modern browser.

Typical Uses

  • Internal tools and admin panels over an existing SQLite or Postgres database
  • Backend for a content-led site when a full CMS is more than you need
  • MVPs and prototypes that want auth, uploads and a CRUD API without standing up three separate services
  • Multi-tenant apps that need per-customer data isolation without writing their own permission layer

Good to know

bknd is pre-1.0: the README states that full backward compatibility is not guaranteed until v1.0.0, so pin the version you deploy and read the release notes before upgrading. Querying is available over REST or the SDK, and an SQL driver sits underneath if you need to reach the database directly.

Related tools

  • PocketBase — one binary with SQLite, auth and an admin dashboard
  • NocoBase — data-model driven no-code platform for business apps
  • Directus — headless data platform over an existing SQL database
  • Supabase — Postgres platform with auth, storage and realtime APIs

Explore More Categories

Sign In

Register

Reset Password

Please enter your username or email address, you will receive a link to create a new password via email.