BTST composes client and backend plugins inside the application; the app shell, ejected views, database, deployment, and external services remain yours.
\n\n## Quickstart: Blog in an existing Next.js app\n\nThis local evaluation uses the public stable releases with Node.js 22, an existing Next.js 15+ App Router application, and Radix-based shadcn/ui with CSS variables. If shadcn/ui is not configured yet, initialize that verified base and add the components Blog needs:\n\n```bash\npnpm dlx shadcn@4.19.1 init --base radix --preset nova --css-variables\npnpm dlx shadcn@4.19.1 add button dropdown-menu sonner --yes\n```\n\nRender the generated `The same generated Blog route after deterministic sample content is added.
\n\n### The registration that produces the route\n\nThe stable-v3 seam is deliberately small: the backend plugin supplies Blog's server behavior and data model; the client plugin supplies its routes and UI. The generator provides the surrounding adapter, API/site runtime, QueryClient, catch-all routes, and provider wiring.\n\n```ts\nimport { createBackendStack } from \"@btst/stack/api\"\nimport { createMemoryAdapter } from \"@btst/adapter-memory\"\nimport { blogBackendPlugin } from \"@btst/stack/plugins/blog/api\"\n\ncreateBackendStack({\n basePath: \"/api/data\",\n adapter: (db) => createMemoryAdapter(db)({}),\n plugins: { blog: blogBackendPlugin() },\n})\n```\n\n```tsx\nimport { createClientStack } from \"@btst/stack/client\"\nimport { blogClientPlugin } from \"@btst/stack/plugins/blog/client\"\nimport type { QueryClient } from \"@tanstack/react-query\"\n\nfunction createAppClientStack(queryClient: QueryClient, origin: string) {\n return createClientStack({\n api: { baseURL: origin, basePath: \"/api/data\" },\n site: { baseURL: origin, basePath: \"/pages\" },\n queryClient,\n plugins: { blog: blogClientPlugin() },\n })\n}\n```\n\n\n\nBlog adds publishing routes, API operations, its data model, hooks, SSR-aware pages, editor UI, published-page metadata, and sitemap entries. Other plugins have different boundaries: one-sided and companion plugins are labeled instead of being forced into a full-stack claim.\n\n## Released capabilities\n\nEvery capability below is installable from the released CLI. Follow its documentation for the actual payload, services, storage, auth, and adapter prerequisites.\n\n| Capability | Topology | Outcome |\n| --- | --- | --- |\n| [Blog](https://www.better-stack.ai/docs/plugins/blog) | Full-stack | Publishing workflow, routes, API, data model, editor, metadata, and sitemap entries |\n| [AI Chat](https://www.better-stack.ai/docs/plugins/ai-chat) | Full-stack | Streaming conversations, model integration, history, routes, and chat UI |\n| [CMS](https://www.better-stack.ai/docs/plugins/cms) | Full-stack | Typed content models, APIs, generated forms, and editorial UI |\n| [Form Builder](https://www.better-stack.ai/docs/plugins/form-builder) | Full-stack | Form authoring, validation, rendering, and submissions |\n| [Kanban](https://www.better-stack.ai/docs/plugins/kanban) | Full-stack | Boards, columns, tasks, assignment, and drag-and-drop UI |\n| [Comments](https://www.better-stack.ai/docs/plugins/comments) | Full-stack | Threads, replies, reactions, moderation, and embeddable UI |\n| [Media](https://www.better-stack.ai/docs/plugins/media) | Full-stack | Media storage, library routes, uploads, folders, and picker UI |\n| [UI Builder](https://www.better-stack.ai/docs/plugins/ui-builder) | Client-only · requires CMS | Visual page authoring and public rendering over CMS content |\n| [OpenAPI](https://www.better-stack.ai/docs/plugins/open-api) | Backend-only | Generated OpenAPI document and interactive API reference endpoint |\n| [Route Docs](https://www.better-stack.ai/docs/plugins/route-docs) | Client-only | Generated route reference and navigation UI |\n| [Better Auth UI](https://www.better-stack.ai/docs/plugins/better-auth-ui) | Companion · requires Better Auth | Auth and account pages for an existing Better Auth backend |\n\n[Explore the released catalog](https://www.better-stack.ai/docs/plugins) or compare complete generated setups in the [interactive playground](https://www.better-stack.ai/playground?plugins=blog,ai-chat,comments&framework=nextjs&view=preview).\n\n## Compatibility and prerequisites\n\nThe maintained and tested v3 integration paths are:\n\n| Framework | Maintained integration |\n| --- | --- |\n| Next.js 15+ App Router | Route handlers, request-aware and static pages, metadata, and sitemap factories |\n| React Router v7 | Framework routes, SSR loaders, navigation, metadata, and sitemap response helpers |\n| TanStack Start | File routes, SSR loaders, navigation, metadata, and sitemap response helpers |\n\nOther React integrations may be possible through custom adapters, but they are not part of that maintained matrix.\n\nVersioned adapters are published for Prisma, Drizzle, Kysely, and MongoDB. Support is not blanket-equivalent: plugins that need isolated transactions have stricter persistent-adapter requirements, and the generated Form Builder and Media configurations reject MongoDB. The memory adapter is local and single-process only. Check [compatibility and prerequisites](https://www.better-stack.ai/docs/installation#compatibility-and-prerequisites) and the [adapter guide](https://www.better-stack.ai/docs/databases/adapters) for current versions and limits.\n\n## Keep the view code, too\n\nBTST's packaged runtime keeps data fetching and behavior upgradeable. When a plugin offers a shadcn v4 registry block, it copies the view layer into your application. Edit that code freely, then pass pages back through the plugin's component overrides where available or render copied components directly; hooks and API behavior can remain package dependencies.\n\n[Read the ejection guide](https://www.better-stack.ai/docs/shadcn-registry)\n\n## Go deeper\n\n- [Installation and production setup](https://www.better-stack.ai/docs/installation) — frameworks, providers, auth, origins, adapters, and migrations\n- [How BTST works](https://www.better-stack.ai/docs/how-it-works) — backend/client composition and ownership boundaries\n- [CLI reference](https://www.better-stack.ai/docs/cli) — initialize, generate schemas, migrate, and seed\n- [Build a plugin](https://www.better-stack.ai/docs/plugins/development) — create a backend-only, client-only, or full-stack capability\n- [API reference](https://www.better-stack.ai/docs/api-reference) — stack factories, runtime services, and framework adapters\n- [Stable-v3 migration guide](https://www.better-stack.ai/docs/breaking-changes) — migrate older integrations to the released contract\n\n### Optional AI-agent guidance\n\nAfter you understand the human installation path, you can give a coding agent the repository's BTST integration skill:\n\n```bash\nnpx skills@latest add better-stack-ai/better-stack/.agents/skills/btst-integration\n```\n\n## Contributing and license\n\nBug reports, plugin contributions, and documentation improvements are welcome. Read [CONTRIBUTING.md](./CONTRIBUTING.md) for the development workflow, tests, and submission checklist; public-facing copy follows the [BTST message and claims contract](./docs/positioning.md).\n\nBTST is released under the [MIT License](./LICENSE.md).\n\nIf BTST is useful to you, a star helps other React developers find it.\n","readmeFilename":"README.md"}