Skip to content
SaaS backend, hosted or self-hosted

Auth, billing, email and workflows. One SDK, one console.

Turn on sign-in methods, plans, emails and automations in the console, then call them from your React app with one npm package.

Free plan7-day free trial on paid plansNo credit card requiredWorks with Next.js, Vite, React Router / Remix, TanStack Start
console.buildbase.app/dashboard/admin9:00 AM

Dashboard

Acme

All users

12,483

+312 this week

All audience

9,120

+188 this week

Emails sent, 30 days

48,210

61% opened

Workspaces

1,906

41 on trial

Users vs Audience Growth

Day · Week · Month

Users Audience

Needs your attention

3

Payments failed overnight

A retry workflow is running. Two customers were emailed.

1

Sender domain needs a DKIM record

mail.acme.com, added yesterday.

Live events

View all
audience.member_created[email protected] signed up with Googlejust now
subscription.upgradedNorthwind moved to Pro4m ago
workspace.member_addedLena invited to Harbor Labs as Editor12m ago
form.submittedDemo request from beacon.co31m ago

Launch day. One console for the whole backend.

A demo workspace for a fictional company. Yours will look different. Open the real one

Production products built on BuildBase

All 6 are ours. We built the platform for them first, and every module on this page runs their sign-in, billing and email today.

Authentication

Turn it on in the console. It is in your app.

Sign-in methods are configuration, not code. Enable a provider and your hosted sign-in page has it, on your own domain, with sessions handled.

  • Email and password sign-in, with password resets and email verification
  • OAuth 2.0 with Google, LinkedIn, GitHub, Microsoft, Apple, Lovable and Vercel, and one OpenID Connect or OAuth 2.0 provider of your own
  • Magic links and email sign-in codes, without a password
  • Enterprise SSO (SAML and OIDC) and Directory Sync (SCIM), through your own WorkOS account
Everything in Authentication
Console · login methods
Your app · sign inlive

Sign in to Acme

Continue with Google
Billing

Trial to paid, without a webhook handler

Plans, trials, proration, invoices and quotas run in the module. Your app asks one question: can this workspace do this right now?

  • Subscription plans with versioning
  • Free trials with automatic conversion, offered once per person by default
  • Usage-based and seat-based billing, flat or in graduated or volume tiers
  • Add-ons: recurring, one-time, lifetime or consumable
Everything in Billing
Workspace · Northwindlive

Subscription

Day 12 of 14

Trialing
API calls this month3,100 / 10,000
bb.usage.record → ok, 6,900 left
Email Campaigns

Write it once. It sends itself to the right people.

Templates with merge tags, audiences that keep themselves current, and open and click tracking on every send.

  • HTML, Markdown, and plain text templates
  • Open and click tracking, with mail scanner clicks filtered out
  • Bounce and complaint handling for Mailgun and Amazon SES senders, pausing a campaign before it hurts your sender
  • Unsubscribe groups, preference centers, and one-click unsubscribe
Everything in Email Campaigns
Template · trial ending

Subject {{first_name}}, your trial ends in {{trial_ends_in}}

Hi {{first_name}}, your {{plan}} trial ends in {{trial_ends_in}}. Keep your workspace by adding a card.

Unsubscribe group · open and click tracking on

Sending to Priyalive

Priya, your trial ends in 3 days

Hi Priya, your Pro trial ends in 3 days. Keep your workspace by adding a card.

120

Sent

73

Opened

22

Clicked

Workflows

Every event in your product can start a workflow

A failed payment, a new signup, a form submission. Build the response once in the visual builder and it runs every time, with retries.

  • Visual drag-and-drop workflow editor
  • Event-based triggers across users, billing, email, forms and more
  • Conditional branching and A/B splits
  • Wait-for-event steps with timeout
Everything in Workflows
Workflow · failed payment recoverylive

Trigger

payment.failed

Action

Send email

Action

Slack #billing

Wait

3 days

Condition

Still unpaid?

run#20481 01 Cobalt: charge declined

Permissions

Permissions your UI can read

Define roles in the console, then wrap the button. The SDK resolves what this person may do in this workspace and renders or hides it.

  • Built-in admin, editor and viewer permission sets, and the workspace's creator always has everything
  • WhenPermission, WhenRoles and WhenWorkspaceRoles for gating UI
  • usePermissions() for checks in code
  • Your own app permissions next to the built-in ones
Everything in Permissions
Your app · signed in as

Full access to settings, billing, members, and data

View reportsreports:read
Edit projectprojects:update
Manage billingbilling:manage
Invite membersmembers:invite

<WhenPermission permission={…}> the button </WhenPermission>

Webhooks

Everything that happens, delivered to your endpoint

Subscribe to the events you care about. Each delivery is signed, retried on failure and kept in a delivery log.

  • 239 events across users, workspaces, billing, credits, workflows, audience, email and enterprise SSO
  • Subscribe an endpoint to specific events, or to all of them
  • HMAC-SHA256 signatures, verified and parsed in one call with parseWebhookEvent()
  • Standard Webhooks headers (webhook-id, webhook-timestamp, webhook-signature) on every delivery
Everything in Webhooks
POST https://api.acme.com/hookslive
audience.member_created[email protected] 200
subscription.trial_will_endHarbor Labs, 3 days 200
form.submittedDemo request, beacon.co 200
payment.failedCobalt, retry scheduled 200

x-buildbase-signature · signed, retried with backoff, every delivery logged

The 13-vendor stack you don't have to assemble

Every SaaS needs the same backend. The usual way to get it is a subscription per capability, a webhook contract per vendor, and glue code you own forever.

AuthenticationAuth0 / Clerk / Kinde
Subscription billingChargebee / Outseta / Memberstack
Email campaignsMailchimp / Loops / Constant Contact
Workflow automationZapier / Make / n8n
Feature flagsLaunchDarkly / Flagsmith / Unleash
Web pushOneSignal
Role-based permissionsCustom RBAC code
Credit and usage meteringCustom credit and usage code
FormsTypeform / Tally / Jotform
Webhook deliverySvix / Hookdeck / Convoy
Short linksBitly / Dub
Image uploadsCustom S3 upload code
Blog and site contentWordPress / Ghost

Auth alone typically takes 3-6 weeks to build well, and every vendor on the list is another monthly bill - we published the math. BuildBase ships the same list as 20 integrated modules behind one SDK, so the first thing you build is your product.

Environments

Development and staging, without touching production

Every module runs in each environment you add, as a tenant of its own. Build and test there, then promote the configuration that works. Environments are rolling out to organizations: yours has them once the console shows Environments under Settings > General.

  • Its own database: users, sessions, workspaces, audience, lists, tags, email history, workflow runs and files
  • Google and GitHub sign-in with no OAuth app of your own
  • Users, records, history, secrets, keys and webhook endpoints are never copied
  • Never billed: an environment's users, usage and storage do not count toward your plan's quotas or monthly active users
How environments work
terminalBash
npx @buildbase/sdk init --dev        # wire to Development
npx @buildbase/sdk env create Staging
npx @buildbase/sdk env diff Staging  # what would change
npx @buildbase/sdk env push Staging  # promote it

These terminal commands need @buildbase/sdk 1.0.0 or later. You can also add environments and promote changes from the console.

Ready for big customers and AI agents

The things that usually come up after launch, already built.

Sell to companies that need single sign-on

Their IT team connects Okta, Microsoft Entra, Google Workspace or any SAML or OIDC provider from a setup link, and their people sign in the way the company requires. Directory Sync adds people when they join the company and blocks them when they leave. It all runs through your own WorkOS account.

See enterprise

Let AI assistants use your app, as your users

Claude, ChatGPT or Cursor can connect to your app through MCP, the standard way AI assistants call apps. Your user approves the connection, can remove it any time, and the assistant can only do what that user could.

See Agent-ready apps

Run it on your own servers

Some customers need their data to stay in-house. Run the whole platform with Docker Compose on your own infrastructure, with the same console as the cloud.

See self-hosting

Works in your AI tools

Two different things, each with its own page: BuildBase itself in your AI tools, and the app you build being ready for your users' agents.

BuildBase in your AI tools

Connect Claude, ChatGPT, Claude Code, Codex and Cursor or another AI tool to BuildBase's own MCP server. Sign in as yourself and manage your organization from the chat, read only until an owner allows more.

See BuildBase in your AI tools

Agent-ready apps

Add an MCP server to the app you build with the SDK, so your users can connect the same tools to your app and act as themselves in it.

See Agent-ready apps

One price for the whole backend

Start on Free, with paid plans from $19/mo. The plans differ in how much you can run and in some of the features they include, and the full comparison lists every one.

  • The 6 core modules on every plan, with higher limits and more features as you move up.
  • A Free plan at $0 that stops at its allowance and never bills.
  • Paid plans start with a 7-day free trial, no credit card.
  • Users, emails and webhook deliveries are allowances, not meters. Going over does not produce a bill.
  • Three things bill over on the paid plans: workflow runs at $0.25, $0.15 or $0.10 per 1,000 runs on Launch, Grow and Scale, web analytics events at $2 per 100,000 events, and storage at $0.10 per GB-month.
  • Pay yearly and get twelve months for the price of ten.

Prices in USD. Verified 31 October 2026.

AllowancesFree$0/moLaunch$19/moGrowPopular$49/moScale$99/mo
Monthly active users10k25k100k500k
Workspaces501k25k100k
Storage1 GB10 GB50 GB200 GB
Console team members23850
Changelog

Shipping every week

The most recent release. Every week we ship is written up.

Dispute fee consent and the scoped CLI name, in SDK 1.5.0

SDK 1.5.0 lets a seller accept the app owner's debit terms inside your app, closes an open redirect after sign-in, and names the CLI npx @buildbase/sdk.

  • SDKWith @buildbase/sdk 1.5.0, a seller can accept your account debit terms inside your app. The new DebitTermsConsent component shows your terms as a link with their version and an Accept button, and SellerHome shows it to sellers. When you publish a new version of the terms, sellers are asked again.
  • SDKFor a screen of your own, useSelling() now returns acceptDebitTerms. Only an acceptance of the version in force counts.
  • SDKOn a lost marketplace dispute, the seller's sale page can now say what became of Stripe's dispute fee: taken from the seller, refused and owed, or kept by your app. It shows when the platform reports it; otherwise the page is unchanged.
  • SDKThe SDK's README, its AGENTS.md and the hints the CLI prints now say npx @buildbase/sdk for a command run before the SDK is installed. The unscoped buildbase package on npm is not ours. In a project that already has the SDK installed, npx buildbase still works.
Guides

Pick your framework

Each guide adds BuildBase to an app you already have: install, sign-in, reading the session on the server, then teams and billing.

The server SDK runs on Node.js, Bun, Deno and Cloudflare Workers. All build guides

Start from working code

Clone a starter that is already wired to BuildBase, or install the Claude skill and let Claude do the integration in your own app.

Integrate the SDK with Claude

buildbase@buildbase-skills

Takes a Next.js app from npm install to a working sign-in, then covers workspaces, billing, feature flags, quotas, credits, notifications, webhooks and calling BuildBase from a non-Node backend.

In Claude Code:

Any agent (Cursor, Codex, Copilot and others), from a shell:

Then ask Claude: “Add BuildBase auth to my Next.js app.”

Other ways to install, including claude.ai

Frequently Asked Questions

Common questions about BuildBase.

Do I have to use every feature?

No. Turn on only what you need - auth and billing now, email or workflows later. Some modules build on others: billing and credits belong to workspaces, forms store into collections, and workflows send email through the email module.

How long does integration take?

Install the SDK, wrap your app in a provider, and call hooks. Sign-in runs on a hosted, white-label auth portal, and pre-built screens cover workspace settings, so the first screens need no UI of your own.

How is data secured?

AES-256 encryption at rest, TLS 1.2+ in transit, role-based access control, and per-tenant data isolation. Built for GDPR and CCPA readiness.

Can I migrate away later?

Partly. Audience contacts export as CSV and each workflow exports as JSON from the console, and subscriptions and payments sit in your own Stripe account. Passwords, passkeys and workspaces do not export, and moving off means replacing the SDK hooks and components in your code.

What frameworks does BuildBase support?

The React SDK works with Next.js, Vite, React Router / Remix, TanStack Start and any other React web app. The Server SDK and REST APIs are framework-agnostic - Express, NestJS, Fastify, Hono, Astro, or anything else.

Build your product, not its plumbing

Sign-in, billing, email and workflows are waiting in the console. Start on the Free plan, or try a paid plan free for 7 days, no credit card.

Free plan7-day free trial on paid plansNo credit card required