Every feature we've released, in order. Built for AI-assisted development.
Previously the clone job auto-minted a distinct `bb_sk_*` per function on the cloned app — any sibling-fn call that compared its bearer to its own `ctx.env.BUTTERBASE_API_KEY` 401d because every fn carried a different key. Clones now mint one key per app, fanned out to every function that needs `BUTTERBASE_API_KEY` / `BB_SUBSTRATE_KEY`. Existing already-cloned apps can be consolidated with `scripts/backfill-consolidate-clone-keys.ts`.
Learn more →App-scoped service keys can now assert "act on behalf of user X" via the `X-Butterbase-As-User` header — the runtime populates `ctx.user.id` before invoking. Per-function `allow_service_key_impersonation` (default `true`) lets admin-only and billing-webhook handlers opt out; the platform 403s any X-Butterbase-As-User on those endpoints at the edge. End-user JWTs and out-of-app service keys cannot impersonate. Surfaced through `deploy_function`, `manage_function action: "update_settings"`, the CLI (`bb functions deploy --no-allow-impersonation`), the SDK (`apiClient.updateFunctionSettings`), and a toggle on the dashboard function detail page.
Learn more →Every function invocation now surfaces `ctx.caller = { type, keyId, scope, userId }`. Type is one of `service_key`, `end_user_jwt`, `loopback`, or `anonymous`. The `keyId` is a non-secret api-key row id safe to log in audit trails; `userId` is the user the request is acting on behalf of (propagated through ctx.invoke chains and X-Butterbase-As-User impersonation). Stop parsing `req.headers.authorization` by hand.
Learn more →Call sibling functions on the same app with `ctx.invoke('fn-name', body)` — no bearer ceremony, no env vars. Authenticated with the per-app internal function key (never exposed to user code), `ctx.user.id` propagates automatically to the callee, and a depth-4 cycle guard throws synchronously on the 5th hop. Replaces the brittle pattern of having one fn call another over HTTP with `Bearer ctx.env.BUTTERBASE_API_KEY`. Same release: `ctx.app.substrateUserId` surfaces the linked substrate user id (or `null` when the app is not substrate-linked) so you can stop using `if (ctx.substrate)` as a proxy for "is this app linked?".
Learn more →A single function can now declare multiple triggers — an HTTP endpoint plus a daily cron, an S3 upload plus a webhook. New trigger types `s3_upload` and `webhook` join `http`, `cron`, and `websocket`. Dashboard editor supports add/remove per type.
Learn more →Mark any serverless function as `agent_tool: true` with a description, mode (`read_only` or `read_write`), and exposure (`developer_only` or `end_user`). Agents call it directly; read-write tools pause the run for human approval before mutating.
Learn more →Define multi-step LLM agents as a graph spec — LLM nodes, tool nodes, edges, limits — and run them with checkpointed state, SSE/WebSocket streaming, idempotency, human-in-the-loop approvals for write tools, and per-IP / per-user / per-app rate limits. Authored from the dashboard, CLI (`butterbase agents`), MCP, or REST.
Learn more →Mark any app public and let others clone it. Clones get your schema, RLS policies, function code, non-secret config, repo files, and seed-marked rows. Browse, clone, and configure clone webhooks from the dashboard, CLI (`butterbase clone`), or MCP.
Learn more →Per-app version-controlled file storage. Push your source with `butterbase repo push`, pull a fresh copy with `butterbase repo pull`, browse snapshot history. Powers app templates and gives every app a durable source-of-truth.
Learn more →Institutional-memory layer for your AI agents. Record entities, decisions, commitments, learnings, and principles to a per-account ledger with approve/reject gating, attention rules, real-time updates, and a dashboard browser. Surfaced via SDK, MCP, REST, and `bb substrate` CLI.
Learn more →Regional KV substrate with SDK, REST, CLI, and MCP surfaces. Sessions, locks, rate limiters, idempotency keys, and feature flags ship with copy-pasteable recipes.
Learn more →Push your source — Butterbase runs `npm install` and the framework build in a container. Skip the local `@cloudflare/next-on-pages` toolchain (especially useful on Windows).
Learn more →Inject encrypted config into Durable Objects with `butterbase do env set/list/unset`. Available as `env.KEY` inside any DO class for the app.
Learn more →Deploy server-rendered Next.js (App Router, Server Actions, RSC) and Remix apps directly to Cloudflare Workers. One CLI command, no Node.js host to run.
Learn more →Stateful per-key actors with built-in storage and WebSocket support. Build chat rooms, multiplayer games, rate limiters, and long-running AI agents — no infra to run.
Learn more →Discover and call partner APIs from the TypeScript SDK (`PartnersClient`), CLI (`butterbase partners list`, `partners curl`), and MCP (`list_partner_apis`).
Call third-party APIs from your app without exposing API keys. Butterbase manages key pools, rotation, and failover — your frontend just hits a single proxy route.
Public submission API for hackathons with async judging. Scores evaluate demo URLs and platform feature usage. Leaderboard and rescore endpoints included.
Learn more →Faster response times across authentication, quota enforcement, and API key validation — all with no changes required to your app.
Pass images alongside text in chat completion requests. The AI config API now accepts multimodal message content.
Learn more →Bring your own domain with automatic HTTPS, configured per app.
Learn more →Passwordless sign-in for your app's users. Drop into any auth flow.
Learn more →Per-function secrets and config, encrypted at rest, hot-reloaded on deploy.
Learn more →Stdout, stderr, and timing surfaced per invocation, viewable in the dashboard.
Learn more →Run custom logic after a user signs in — provision data, sync to external systems, send a welcome email.
Learn more →Declare ON DELETE and ON UPDATE behaviors directly in your schema.
Learn more →First-class connectors so your functions can call external services with managed auth.
Learn more →Ingest PDFs, DOCX, TXT, and more. Query with natural language in two API calls. Vector search built in.
Learn more →Free / Pro / Enterprise tiers with usage metering. Email alerts at 80% and at the hard limit.
Learn more →Unified, queryable activity log for every app event.
Health status, quota usage bars, weekly growth deltas, and recent activity in one place.
Learn more →Deploy a React, Next.js, or static frontend to a global URL with one tool call. SPA routing and HTTPS handled.
Learn more →WebSocket data-change notifications with RLS-aware filtering, presence tracking, and custom event triggers.
Learn more →Six AI-coding skills for Claude Code, installed via `claude plugin add @butterbase/skills`: build-app, schema-design, function-dev, debug-rls, deploy-frontend, contributing.
Learn more →Connect any AI assistant — Claude, Cursor, Windsurf — to Butterbase via MCP. Tools tuned for agents: predictable responses, structured errors, next-action hints.
Learn more →@butterbase/cli with init, integrations, and project-management commands.
Learn more →@butterbase/sdk with full API coverage and typed responses.
Learn more →Deploy TypeScript / JavaScript functions to a managed Deno runtime. HTTP triggers and cron schedules.
Learn more →One tool call to restrict rows so each signed-in user only accesses their own data.
Learn more →S3-compatible storage with presigned URLs. Per-app and per-user organization, configurable size and content-type limits, RLS-aware.
Learn more →Email/password, OAuth (any provider), password reset, email verification, and rate limiting — configurable per app.
Learn more →Every app gets its own Postgres database, identifier, and API base URL.
Learn more →Describe tables in JSON; the platform diffs and applies. Full CRUD over HTTP appears automatically — no code generation, no manual route setup.
Learn more →Control API, app provisioning, API key management, and the platform skeleton.
Want to see something here? Suggest a feature