# BuildBase changelog

What shipped, newest first. Source: https://www.buildbase.app/changelog

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

9 November 2026. 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.

### Added

- **SDK:** With @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.
- **SDK:** For a screen of your own, useSelling() now returns acceptDebitTerms. Only an acceptance of the version in force counts.
- **SDK:** On 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.

### Improved

- **SDK:** The 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.

### Fixed

- **Security:** The redirect after sign-in now refuses a target that contains a control character, such as a tab or a line break. One like that could send a person who had just signed in to another site.
- **SDK:** About 50 API methods, among them createWorkspace and addUser, now report errors the same way as the rest of the client. When one is refused for a plan limit, the app refreshes what the plan allows and stops offering the action.
- **SDK:** The credit methods no longer report every refusal for payment as INSUFFICIENT_CREDITS. A refusal such as PLAN_REQUIRED now keeps its own code.

Source: https://www.buildbase.app/changelog/sdk-1-5-0-dispute-fee-consent-and-the-scoped-cli-name

## Selling docs: marketplace and storefront, on Stripe Connect

8 November 2026. New docs and a new website page show how the people in your app sell through it on Stripe Connect, as a marketplace or a storefront, up to a first sale.

### Added

- **Docs:** Let your users sell, at docs.buildbase.app/billing/selling, explains the two shapes. In a marketplace the buyer pays your app, and Stripe sends each seller their share less your fee. In a storefront the buyer pays the seller's own Stripe account, and your fee comes to you.
- **Docs:** Two guides, Zero to first sale for a marketplace and for a storefront, go from saving your Stripe keys to a seller paid out.
- **Docs:** A page for each part of a sale: item types and items, checkout and orders, coupons, bundles, item options, booking calendars, affiliates and shipping.
- **Website:** A new page, buildbase.app/commerce, shows both shapes and what a sale needs, with screens from the SDK.

Source: https://www.buildbase.app/changelog/selling-docs-marketplace-and-storefront

## Agent setup and co-seller screens, in SDK 1.4.0

7 November 2026. SDK 1.4.0 adds one command that connects an MCP server to the AI tools on a machine, screens for co-sellers, and workspace delete for its creator only.

### Added

- **Agents:** npx @buildbase/sdk agent setup adds an MCP server to the AI tools it finds on your machine: Claude Code, Cursor, VS Code, Codex, Windsurf, Gemini CLI and Zed, and an install link for Goose. Use --url for your own app's MCP server, or --console for BuildBase's. It shows what it will change and writes nothing without a yes.
- **Agents:** npx @buildbase/sdk agent-ready check runs the isitagentready.com checks against any URL, localhost included, so you know the score before you deploy.
- **SDK:** CoSellerInvitations shows a seller the co-seller invitations they received, with the item, who invited them and their share of each sale, and lets them accept or decline.
- **SDK:** ItemCoSellers shows who is paid from an item's sales. A seller can invite a co-seller with a percent share, or withdraw an invitation, when your selling settings let sellers invite. Splitting an item's sales between sellers is not available yet, so the platform refuses a new invitation and its accept until it is.

### Fixed

- **Workspaces:** Only the person who created a workspace now sees Delete, which matches what the server allows. Before, a role that listed the permission showed the button, and the server then refused.
- **SDK:** In Arabic and Hindi, the time estimate in StartSelling now uses the same digits as the rest of the dialog.

Source: https://www.buildbase.app/changelog/sdk-1-4-0-agent-setup-and-co-seller-screens

## Manage BuildBase from your AI tools

6 November 2026. Connect Claude, ChatGPT, Cursor or another AI tool to BuildBase, sign in as yourself, and work in your organization from the chat, within your role.

### Added

- **Agents:** You can now work in your BuildBase organization from Claude, ChatGPT, Cursor, VS Code and other AI tools. Add https://api.console.buildbase.app/mcp to the tool as a remote MCP server. MCP is the standard way AI tools connect to other services.
- **Agents:** The first time it connects, the tool opens BuildBase's sign-in page and a consent screen, and you approve it. The agent then acts as you, with your role. It never sees API keys, sign-in settings or payment credentials.
- **Console:** Security, in your account menu, has a new AI agents card. Copy the address there, or use Add to Cursor, Add to VS Code, or the ready-made Claude Code and Codex commands. Get started has an optional Connect your AI step that opens it.
- **Agents:** The server offers 19 tools. An agent can read what the console shows you, create and change things, and export your audience. It can also search the BuildBase docs and list the environment variables an app needs (get_env_template).
- **Blueprints:** Owners and admins can have an agent write a blueprint, one file that describes an organization's setup. The agent shows what applying it would change before it applies it. Agents can read your plans, add-ons and credit packs but never change them, so a blueprint that would is refused up front.
- **Agents:** An agent can create an organization for you with create_org, once you approve its name. You own it, and it starts on the same plan as one you create in the console.
- **Agents:** A CI job or script with nobody to sign in can connect with one of your organization's API keys instead. The key works only in its own organization, and the AI agents setting still applies to it.
- **Security:** Every agent starts read only, with the console:read scope, a named permission you grant. When a task needs more, BuildBase tells your AI tool which scope is missing. You then approve just that one: console:write, console:export or console:destructive.
- **Security:** Risky changes go through their own tool, console_destructive_change, and need the console:destructive scope. They include deletes, changes to members, roles or webhooks, sends to an audience, moving money and running a workflow for real. An AI tool that can ask you directly shows you each one, and your approval works once, within five minutes.
- **Console:** On the same card, owners and admins choose what agents may do in the organization: Off, Read only or Read and change. Read only is the default. A change reaches every connected agent at once.
- **Console:** Security lists the agents connected to the organization, and Block stops one at once. Owners and admins see and block every member's agents. In the audit log, an agent's change is marked AI agent, with the AI tool's name and the member it acted for.
- **Website:** A new page, buildbase.app/mcp, shows how it works, with a setup page for each AI tool. The menu now tells BuildBase in your AI tools apart from Agent-ready apps, where your own users connect AI tools to your app.
- **Documentation:** The docs have a page for each of 16 AI tools. Each says where to add the server, which plan the tool needs and what signing in looks like there.
- **Website:** AI agents can find the server by themselves. The website lists it in llms.txt and its API catalog. Both buildbase.app and docs.buildbase.app describe it and its sign-in under /.well-known/.
- **Website:** The website and the docs offer read-only WebMCP tools, which a web page gives to an AI agent in the browser. With them an agent searches either site and reads a page as Markdown. The home page also has a Markdown version, buildbase.app/index.md.

Source: https://www.buildbase.app/changelog/manage-buildbase-from-your-ai-tools

## Start an app with no BuildBase account, with SDK 1.3.0

6 November 2026. SDK 1.3.0, or an AI coding agent, can start your app on a temporary BuildBase organization before you sign up. Claim it, or it is deleted after 72 hours.

### Added

- **SDK:** Start building before you sign up. With @buildbase/sdk 1.3.0, npx @buildbase/sdk init --claim creates a temporary organization and sets your app up on it, with email and password and magic-link sign-in turned on. It prints a claim link and code, and keeps the key and secrets in .env.local.
- **SDK:** Keyless development does the same with no command. Wrap your Next.js config in withBuildBaseKeyless, from @buildbase/sdk/keyless. Then next dev creates the organization on its first start and reuses it after. Express apps use applyKeyless, and neither runs outside development.
- **SDK:** A KeylessPrompt card says your app runs on a temporary organization, when that is deleted and how to claim it. Run npx @buildbase/sdk claim-code for a fresh claim code whenever you need one.
- **Agents:** An AI coding agent can start the same way with one request, following buildbase.app/auth.md. It gets an API key, a claim link and a claim code that lasts 15 minutes. It can ask for a new code with the claim_link tool.
- **Console:** To keep the organization, open the claim link, sign in or sign up, and type the code. You become its owner, the temporary key stops working, and the limits below are lifted.
- **Console:** After the claim, the page tells you if your users cannot sign up yet for want of an email sender. Add an email sender takes you to the console to connect one.
- **Organizations:** Until it is claimed, an organization holds at most 50 end users and takes Stripe test keys only. It gets no custom domains, no invitations and no extra environments.
- **Email:** Until the claim, it sends only sign-in and verification mail, at most 100 a day. That mail names it a BuildBase test app, never the name or logo the agent chose.
- **Sign-in:** Every hosted sign-in page of an unclaimed organization says it is a test app that nobody has claimed yet, so it cannot pass for another company's sign-in.
- **Organizations:** An unclaimed organization is deleted with its data 72 hours after it was made. The address the agent gave gets one reminder about a day before.

Source: https://www.buildbase.app/changelog/start-an-app-with-no-account-sdk-1-3-0

## Agent-ready apps in one command, and safer built-in agent tools

6 November 2026. One command readies your app for AI agents to sign in, agents can ask a person for access by email, and AI tools ask first before risky built-in actions.

### Added

- **SDK:** With @buildbase/sdk 1.3.0, npx @buildbase/sdk init --agent makes a Next.js app agent-ready. It writes the app's own MCP server at /api/mcp and the discovery files agents look for. It also writes the routes agents sign in through.
- **Agents:** Agents can sign in to that app only once a person turns it on. With --claim as well, the claim page offers Let AI agents sign in to your app, unticked. Otherwise, turn it on under Authentication > Agent readiness.
- **Agents:** Agents can now ask for access with just a person's email. Turn on Let agents register with a person's email under Authentication > Agent readiness. The person signs in on your sign-in page as that address and confirms a code. No account is created.
- **Agents:** This is the email registration that the auth.md standard describes and agent-readiness scanners check. Agents call POST /api/v1/auth/oauth2/agent/identity?org=. The tokens go to one of your agent clients with the device code grant on.
- **Documentation:** A new guide, Make your app agent ready, lists what agent-readiness scanners check and what answers each check. A page for each of 12 AI tools shows how your users connect them to your app.

### Improved

- **Agents:** Agents that register themselves and then go unused are now removed for you, so they no longer fill your limit of self-registered agents. Each removal is in your auth log as client_deleted.
- **SDK:** From @buildbase/sdk 1.0.2, four built-in MCP tools are marked destructive, so AI tools ask before running them. They are update_workspace_user_role, invite_workspace_user, purchase_add_on and send_notification.
- **SDK:** Also from 1.0.2, every built-in tool's answer ends with a note that it is data, never instructions. It guards against prompt injection: text someone planted in a name or description to steer the agent.
- **SDK:** From 1.3.0, your app's MCP server says so when a token needs no scope. So npx @buildbase/sdk agent doctor no longer warns about scopes on a newly set up app.

### Fixed

- **Agents:** Agent sign-in set up with init --claim --agent now offers the organization's password and magic-link sign-in. Before, the person an agent asked saw a page saying the app had no sign-in methods.

Source: https://www.buildbase.app/changelog/agent-ready-apps-in-one-command-and-safer-agent-tools

## Clearer refusals for agent tokens, console sign-in and uploads

6 November 2026. Agent tokens your app declines, refused console sign-ins and oversized files now say why. A notification email can also leave its unsubscribe group.

### Added

- **Email:** A notification email template can now leave its unsubscribe group. It is then sent as transactional mail: no opt-out stops it, and it carries no one-click unsubscribe header.
- **API:** To do it, send unsubscribeGroupId as null to PATCH /api/emails/templates/:id. System templates and templates of other categories keep their group.

### Improved

- **Agents:** When your app server declines to issue a token to an AI agent or another app, they now learn why. The token endpoint answers 400 invalid_grant, with your message as error_description, up to 300 characters.
- **Agents:** Before, every refusal read as 503 temporarily_unavailable, which said to try again later. An app server that cannot be reached still answers 503.
- **Console:** The console's sign-up page is now a real Create your account screen, built from the sign-in card. Before, it sent you straight on to sign in.
- **Console:** A refused console sign-in now says why and what to do next. For example, it asks you to verify your email address first, or offers Contact support for a blocked account.
- **Console:** While the console's sign-in options load, one placeholder shows, so buttons no longer appear one after another. If they fail to load, Try again fetches them in place.

### Fixed

- **Assets:** Three more size refusals now state their limit in exact bytes and carry maxBytes. They cover a file sent inline as a data: URI over 16,384 bytes (INLINE_FILE_TOO_LARGE), a collection record's file over its field's limit, and a file over your plan's per-file limit. Their status codes and error codes are unchanged.

Source: https://www.buildbase.app/changelog/clearer-refusals-for-agent-tokens-console-sign-in-and-uploads

## Content and links stored as typed, and clearer upload refusals

6 November 2026. Docs, testimonials, titles and short links keep exactly what you typed, every too-large upload gets the same answer, and the workspace's creator now holds workspace:delete.

### Added

- **Blueprints:** A blueprint can carry your organization's time zone as app.timezone. Applying it checks the zone the same way Settings > General does.
- **Docs:** A new guide, Keep your existing sign-in, says what works when your app already signs people in with Supabase, Clerk, Auth0, Firebase or its own code, and what does not.

### Improved

- **Console:** The console's markdown editor shows HTML inside a post, doc or content block as inert, so a script in it cannot run while you edit.

### Fixed

- **Content:** Docs, content blocks, testimonials, blog titles and FAQ questions are stored exactly as typed. A & or < no longer comes back as &amp; or &lt;, and a title such as Q&A: <Button> gets a readable slug. Entries saved before keep their old encoding until they are saved again.
- **Links:** A short link sends visitors to exactly the address you gave it, query string included, and its name reads back as typed. An address with a raw < in it is refused.
- **Assets:** Every upload over a size limit is refused the same way: 413 with UPLOAD_TOO_LARGE, the limit in bytes, and a message that states the limit exactly. Other refused uploads now carry INVALID_UPLOAD.
- **Permissions:** The workspace's creator now gets workspace:delete from the permissions endpoint, and nobody else does, so a delete button gated on it shows for the one person allowed to delete.
- **Collections:** Records saved from the console's record editor are checked and stored by their field's type, so a phone number in a text field stays text, and the Edit dialog opens with the record's values.

Source: https://www.buildbase.app/changelog/content-and-links-stored-as-typed-and-clearer-upload-refusals

## Sign in with Lovable or Vercel

5 November 2026. Your app can now offer Sign in with Lovable and Sign in with Vercel, for people who build with Lovable, Vercel or v0, and SDK 1.3.0 lets companies allow them.

### Added

- **Sign-in:** Sign in with Lovable and Sign in with Vercel are new built-in sign-in methods. They suit people who build with Lovable, Vercel or v0. Add one on the Settings tab of Authentication, with a client ID and secret from Lovable or Vercel.
- **Sign-in:** Each puts a button on your hosted sign-in page. The person approves your app on Lovable's or Vercel's own consent page. Both count toward your plan's limit of social sign-in providers, and the docs have a setup guide for each.
- **Sign-in:** An email address from either counts as proven only when Lovable or Vercel says it is verified. Google, LinkedIn and Apple work the same way.
- **SDK:** With @buildbase/sdk 1.3.0, a company's Sign-in methods without single sign-on setting in your app lists Lovable and Vercel too. Code that switches over EnterpriseSignInChoice with no default branch needs the two new cases.

Source: https://www.buildbase.app/changelog/sign-in-with-lovable-or-vercel

## Stronger sign-in for accounts, agents and the console

5 November 2026. An unverified address no longer reaches your app, a login token works once, and agents and OAuth apps follow tighter rules on accounts, tokens and sign-out.

### Added

- **Authentication:** Connecting Google or another provider can now be tied to the session that started it. Start it with a PKCE challenge (a check that ties both steps to one browser), then finish with POST /api/v1/public/accounts/complete and the verifier. Behaviour change: from a start without a challenge, as every @buildbase/sdk version sends today, a guest who connects a provider stays a guest, with reason link_unbound. Create the account first, then connect. A signed-in person still connects as before.

### Improved

- **Authentication:** Behaviour change: imported password hashes must now stay within set costs. That means bcrypt cost 14 at most, and argon2 up to 256 MiB, 10 passes and 16 lanes, with memory times passes at most 256 MiB. PBKDF2 takes 1,000 to 2,000,000 rounds with a 32-byte hash, and Firebase scrypt a memory cost up to 15 and 8 rounds. A hash beyond these fails its import row. Someone imported earlier with one resets their password to sign in.
- **Authentication:** A custom OpenID Connect provider, a sign-in service you add by its address, now gets 10 seconds and 256 KB for each answer. That covers discovery, its signing keys, the token exchange and user info. A discovery that fails is not tried again for 60 seconds, so sign-in with it can fail for up to a minute after it recovers.

### Fixed

- **Authentication:** An account whose email address was never verified now goes to the person who proves they hold that inbox. Their first sign-in by email code, magic link, SSO or a provider that vouches for the address takes the account back. That ends its sessions and removes its passkeys, two-step factors and provider or wallet links. It also replaces the password and clears the phone number and username. Behaviour change: someone who signed up with a password and never verified loses it at their first code or link sign-in. Forgot password sets it again.
- **Authentication:** Behaviour change: an account whose email address was never verified no longer gets into your app. Until the code from the email is entered, POST /api/v1/auth/redirect, the last step of every sign-in, answers 403 with reason email_verification_required. The hosted sign-in page opens its verify screen, and a sign-in screen of your own must do the same. Guests and agents are not asked.
- **Authentication:** Behaviour change: a login token, which a sign-in holds before it becomes a session, now works once. Sent to POST /api/v1/auth/redirect again, it answers 401 with reason login_token_used. A used token cannot add or remove a passkey either, so offer one before that step, as the hosted page does. Signing out everywhere now also stops any sign-in still in progress.
- **Authentication:** Only the sign-in clients your team made now count as your app's own addresses. A redirect address an AI agent registered for itself is no longer accepted for magic links, social, enterprise or wallet sign-in, or for connecting an account. Those requests answer 400 with Invalid origin or Invalid redirect url. An agent's own OAuth sign-in still checks its addresses as before.
- **Agents:** A person can no longer be signed in to an account an AI agent created with their email address. A sign-in to it by email code, magic link, a provider or SSO answers 403 with reason agent_address, and the page says why. Agent accounts get no welcome, sign-in or password emails and no reset code. They stay out of your audience, and domain join and Directory Sync skip them. The agent's own password sign-in is unchanged.
- **Agents:** An agent that registers itself gets device code sign-in only when the client it is made from has Device code sign-in turned on. Client names an agent chooses lose invisible and direction-changing characters. The device approval page now says where the request came from, by IP address and program.
- **Agents:** Behaviour change: when an OAuth app or agent refreshes its token, the session behind its previous access token ends. That older access token then gets 401 from BuildBase, so use the new one. A refresh refused with invalid_target, for a resource the grant does not cover, now leaves the refresh token usable.
- **Agents:** Deleting an OAuth client in the console now signs out everyone connected through it. Their consents and refresh tokens are revoked, and the app is told with client_deleted at its revoke address. Before, sessions the app had opened kept working for up to 30 days.
- **Console:** Signing in to the console with Google now finishes only in the browser tab that started it. So nobody can sign you in to an account that is not yours with a link (login CSRF, a forged sign-in). The console no longer reads a sign-in token from the query string.
- **Console:** Switching organization in the console no longer sends the sign-in of the organization you are leaving to a self-hosted organization's server. The switch sends only the token made for it.
- **Enterprise:** When a company narrows its allowed sign-in methods, Sign them out now also ends sessions begun with an email code, a phone code or a wallet. Before, those sessions were neither counted as outside the list nor ended.
- **Enterprise:** Behaviour change: a company admin can widen a workload credential only when their company roles reach every scope it carries. Otherwise, changing what it trusts, turning it back on or lengthening its tokens answers 400 workload_credential_invalid with detail scope_beyond_you. Turning it off, renaming, narrowing and deleting it stay open. Your team in the console is not affected.

Source: https://www.buildbase.app/changelog/stronger-sign-in-for-accounts-agents-and-the-console

## Tighter access, masked secrets and firm request limits

5 November 2026. Roles and members can no longer reach past their own access, more secrets stay masked, and requests, lists, uploads and webhook replies get firm limits.

### Improved

- **Analytics:** Your web analytics allowance now counts only events from sites you track. Events from a site waiting for review cost nothing, and one IP address counts at most 10,000 events a day. Only your own hostnames and their subdomains are tracked at once now. A sibling such as www.acme.com beside app.acme.com, or a neighbour on a shared host, waits for you to Track or Block it. Automatic tracking also stops at 100 sites.
- **Platform:** Behaviour change: asking a console API list for every row with pagination=false now returns at most 500 rows. The answer's hasNextPage says when there are more, and $page reads the next page. The console reads every page itself. The SDK's FAQ read gets up to 500 questions of a collection.
- **Platform:** Behaviour change: one request may now carry at most 20,000 values, counting keys and list items, or 50,000 for workflows and email templates. It may also hold at most 1,000 values with HTML in them, and 20,000 tags in all. Past any of these it answers 413, too large. A 503 asks you to retry when the server is busy checking HTML.
- **Assets:** Behaviour change: an SVG upload can now be 1 MB at most, down from 5 MB, and hold up to 10,000 elements. A larger file answers 413 with UPLOAD_TOO_LARGE. An SVG too complex to clean in time is refused with a message saying so. SVGs are now cleaned apart from the rest of the server, so a hard one no longer holds up other requests.
- **Webhooks:** A webhook endpoint now has 15 seconds in all to answer, from connecting to the last byte. Before, the 15 seconds counted only silence. BuildBase reads at most 64 KB of the reply, and the status code still decides whether the delivery worked. A workflow's HTTP Webhook step timeout is now a whole-request deadline too.

### Fixed

- **Billing:** Behaviour change: only an owner or admin can now change your Stripe keys on Billing > Credentials. That covers saving, replacing or deleting them, and setting up the Stripe webhook. The secret key spends your money, and the signing secret decides which Stripe events are trusted. A custom role with the credentials permission now gets 401 there, though it can still read the masked keys.
- **Access control:** A member can no longer change or delete a role that holds a permission they lack. The request answers 403 and names those permissions, and the Roles screen shows that role read-only, with the reason. A change to a role now reaches the API keys it limits at once, instead of up to five minutes later.
- **Webhooks:** Behaviour change: rotating a webhook's signing secret now needs permission to update webhook endpoints, not to create them. Rotating a company log stream's secret likewise needs permission to update enterprises. A role that may only add endpoints can no longer rotate one, and an editor who sees the button can now use it.
- **Security:** Saving organization settings now answers a member who is not an owner or admin with only the fields they can read. Before, the answer carried the whole row, Slack webhook URL included.
- **Workspaces:** Workspace members can no longer remove someone who holds more access than they do, and get a 403 that says so. Leaving a workspace yourself is unchanged. With Can invite members set to Admin only, only admins can now revoke an invitation. Resending an invitation now checks its role as sending does. So a member who cannot invite an admin cannot resend an admin invitation either.
- **Email:** Behaviour change: only its maker, an admin or the organization's owner can now open, rename, copy or delete an email template. Anyone else gets 404. A system template can still be read and copied by anyone who may read templates, and only an admin can change it. A template id that does not exist now answers 404, not 200 with null.
- **Workflows:** An HTTP Webhook step's header values are now masked wherever a workflow is read. They show as bullets, plus the last four characters of a long value. Runs and logs keep only the masked form, while the step still sends the real value. Content-Type and similar headers, and values made only of merge tags, stay readable. Saving a step with its mask unchanged keeps the stored value. Behaviour change: an exported workflow carries the masked values, so set them again after importing it.
- **Security:** Reading your SMTP settings back now shows none of the password, only whether one is set. Saving the form unchanged keeps it. Client secrets, social sign-in secrets, the Apple sign-in private key and deploy hook secrets now stay masked on every read. That holds whatever fields a request asks for.
- **Content:** Behaviour change: an API key that reads content now gets each item's creator as a person's id, never a name or email, and no sync hashes. A post's suggested posts now include only published ones, so a draft's title never reaches your live site.
- **Users:** An attribute with Allow public view off now never reaches the person. The SDK's attribute read, both attribute writes and a profile update leave it out, past your tenth attribute too. The console's user editor now stores every attribute by its type, and refuses a value of the wrong type with 400.
- **Workflows:** A value merged into a step's JSON now arrives as data. That covers Update Audience Member's attributes, an HTTP Webhook body or headers, and Send Email's variables. Text a person typed, such as their name, can no longer change the JSON around it. Transform Data no longer reads merge tags inside a value a second time. Behaviour change: attributes that are not valid JSON now fail the step with a clear message, instead of finishing with nothing written.
- **Content:** Behaviour change: a testimonial's company website and a tracking script's privacy link must now be an http or https address. Anything else answers 400. A value saved earlier that is not one is left out of what readers get.
- **Links:** A link destination BuildBase has blocked now stays blocked with any query string, and with or without a trailing slash. Creating a link to a blocked destination, or pointing one at it, answers 400 with the reason. Tracked email links follow the same rule.
- **Email:** Behaviour change: subscribing from a newsletter's archive page now asks for a captcha, a check that a person, not a script, is signing up. It uses your organization's captcha setting, which works with no setup. A form of your own calling the subscribe route must send captcha too, or it gets 400. For the built-in check, fetch one from GET /api/public/newsletters/:orgId/:slug/challenge. The confirmation email now opens with Hello, without the name typed. A burst of sign-ups for one address sends one email.

Source: https://www.buildbase.app/changelog/tighter-access-masked-secrets-and-firm-request-limits

## Purchases confirmed inside your app, with SDK 1.2.0

5 November 2026. With SDK 1.2.0, a buyer back from Stripe sees if their purchase is ready. Buy buttons wait while it is confirmed, and a new app builds before its keys are set.

### Added

- **SDK:** With @buildbase/sdk 1.2.0, a buyer back from Stripe's checkout page sees a dialog that checks the purchase with BuildBase. It says whether the plan, add-on, credit pack or saved card is ready. Or it says the purchase is still processing, or waiting on a bank payment.
- **SDK:** Once the purchase is done, the dialog opens the settings screen for it, or calls your own ui.behavior.onCheckoutComplete. When confirming takes long, it says so, and Check again asks once more.
- **SDK:** Set ui.behavior.checkoutReturn to 'screen' to keep the billing screens with no dialog. Set it to 'off' to show the result yourself, with <CheckoutStatus> or useCheckoutStatus.
- **Agents:** Your server can ask the same question with bb.checkout.status(sessionId). Your app's MCP server has a read-only get_checkout_status tool, so an agent can ask too.

### Improved

- **Billing:** Plan & Billing, personal Billing, Add-ons, Credits and the auto top-up card show that same answer instead of guessing. While a purchase is being confirmed, their buy buttons give way to a notice, so nobody starts a second purchase by mistake.
- **Tracking:** Behaviour change: the purchase and addon_purchased events fire once the purchase is complete, not when the buyer is back. A bank payment still clearing reports nothing from the browser. Set checkoutReturn to 'off' for the old timing.
- **SDK:** Behaviour change: SDK components no longer set margin: 0 on their root. They take the spacing your layout gives them.

### Fixed

- **Billing:** Credits no longer says the credits were bought before they are added. The top-up card no longer says the card is saved before it is.
- **SDK:** An app set up with npx @buildbase/sdk init now builds before its keys are filled in. A missing org ID or API token is reported at the first call to BuildBase, naming the variable to set.
- **SDK:** For Vite, npx @buildbase/sdk init now sends the sign-in code to /api/auth/token, the route the Next.js setup and the docs use. Apps set up before keep their own route.
- **SDK:** Screen readers now hear the names of the invite form's fields on the Members screen. The passkey name box and its buttons on the Security screen are named too.

Source: https://www.buildbase.app/changelog/purchases-confirmed-in-your-app-sdk-1-2-0

## Choose where buyers land after checkout

5 November 2026. A checkout your app starts without a return address now brings the buyer back to your app. Choose the page under Settings > General, card After checkout.

### Added

- **Billing:** A new After checkout card under Settings > General sets the page buyers come back to when your app sends no return address. A line under it says where such a checkout lands today, and why.
- **Billing:** With no return address and no page set, the buyer returns to the app they were signed in to. Failing that, they return to your oldest app with a public https address.
- **API:** successUrl and cancelUrl are now optional when buying a credit pack or an add-on, upgrading an add-on, or saving a card for auto top-up. Every checkout answer names where the buyer lands, in landingUrl.
- **Environments:** In a development or staging environment, an app's http://localhost address counts as a landing page, so a test checkout comes back to your own machine.

### Fixed

- **Billing:** A checkout with no return address used to bring the buyer back to a page that does not exist. When BuildBase still finds no app address, the answer now says so with the warning RETURN_URL_DEFAULTED.

Source: https://www.buildbase.app/changelog/choose-where-buyers-land-after-checkout

## Setup guides with screenshots, linked to the console

5 November 2026. New guides walk the console step by step, with a screenshot for each step. The console opens the guide for the screen you are on, and AI app builders get pages.

### Added

- **Documentation:** New step-by-step guides walk through the console, with a screenshot for each step that marks the control it names. The docs now hold more than 800 screenshots.
- **Documentation:** Start with From sign-up to a running app, at docs.buildbase.app/quick-start/first-app. Billing has its own guides, from Connect Stripe to your first test subscription, starting at /billing-setup/overview.
- **Documentation:** Other new guides cover credit packs, plan versions, revenue, your first workflow, email senders and campaigns, push campaigns, webhooks, forms, FAQs, short links and user flags.
- **Documentation:** New sign-in guides show how to put the sign-in page on your own domain, see who changed your sign-in setup, and choose how long sign-ins last.
- **Documentation:** Six guides cover the companies you sell to: single sign-on, directory sync, admins, roles and groups, access policy, activity and log streams, and API keys and service accounts.
- **Console:** Docs for this page, in the avatar menu and the command palette (Ctrl+K or Cmd+K), opens the guide for the screen you are on. Every console screen has one, and it opens in a new tab.
- **Documentation:** A guide now links straight to the console screen it describes, which opens in a new tab.
- **Documentation:** A new AI app builders section has short pages for apps made in Lovable, Bolt, v0 and Replit. Each does one job, such as usage credits, paid plans, teams or the payment-failed email, with one prompt to paste.
- **Documentation:** Lovable and Replit pages have an Open in link that starts a project with the prompt filled in. Bolt and v0 offer no such link, so you copy the prompt. Start at /ai-builders/overview.

### Improved

- **Documentation:** Diagrams on the docs site now draw as pictures, where three pages showed their source as code. Code samples show their title, such as a file name, in a bar above the code.

### Fixed

- **Documentation:** The Markdown copy of each docs page, its address with .md added, now keeps code samples whole. A sample that passed a component as a prop came out as fallbackComponent={}, with the component gone.
- **Website:** Sixteen guides on buildbase.app, and the code samples on the homepage and module pages, now use the SDK's own names. That means the /api/auth/token route that buildbase init writes, the bb-session-id cookie and BUILDBASE_WEBHOOK_SECRET.
- **Website:** On the pricing page, tabbing to a plan card that is partly out of view now scrolls the whole card in, on phones and tablets.
- **Website:** The theme switch on the docs site no longer shows the wrong icon for a moment in dark mode. The Product Hunt badge on buildbase.app and the docs now has a name screen readers announce in dark mode.

Source: https://www.buildbase.app/changelog/setup-guides-with-screenshots-linked-to-the-console

## Docs pages corrected to say what the product does

5 November 2026. We checked the docs against the product, step by step, and fixed pages that said something else. These are the corrections most likely to have tripped you up.

### Fixed

- **Enterprise:** The Enterprise SSO guide now turns Sign-in on in the Enterprise tab before adding the Enterprise SSO method. In the old order, adding the method was refused with 409 enterprise_not_enabled.
- **Feature flags:** The flag pages now say a new flag starts switched off, and a flag that is off turns on for nobody. Switch it on with Enable on a user flag or Enabled on a workspace flag.
- **Permissions:** Examples that showed content to roles={['owner', 'admin']} now use ['admin']. owner is not a workspace role, so it never matched. To find the workspace's creator, read usePermissions().isOwner.
- **Users:** The users page now says bb.users.invite adds someone who already has an account, and answers 404 for an address with none. Invite a new address with bb.invitations.create.
- **Email:** A campaign needs a working sender, not a verified domain. Only a Mailgun sender needs a verified sending domain; SMTP, Google and Amazon SES senders do not.
- **Email:** Emails sent from your backend have their own limits: a daily number set by your plan, and 30 to one address an hour. Both answer 429 SEND_LIMIT_REACHED, where the page said 402.
- **Audience:** The audience pages now say the console cannot delete a contact. Your backend can, with bb.subscribers.delete. To stop mail to someone who asked, unsubscribe them instead.
- **Billing:** The billing overview now lists what a plan needs first: billing currencies, a product category and a product. A plan's price lives on its version, in the Base plan price card.
- **Workflows:** The workflow pages no longer describe a test button, which the builder does not have. To run a draft without a real event, call POST /api/workflows/:id/test.

Source: https://www.buildbase.app/changelog/docs-pages-corrected-to-say-what-the-product-does

## Workflow and webhook fixes found while writing the guides

5 November 2026. Writing the guides turned up bugs. A failed run no longer locks a contact out, webhook retries pass a 5-minute check, and limits let through their full number.

### Improved

- **API:** Behaviour change: a list request whose filter is sent as JSON text, instead of filter[field]=value, is now read as a filter. Before, it was ignored and the answer held every row. A filter that is not a JSON object is refused with 400.

### Fixed

- **Workflows:** A workflow set to Once only now lets a contact in again after their run failed, as the docs say. A lock taken on their first event refused them for a year.
- **Workflows:** A workflow with a Max concurrent limit no longer fills up with skipped runs. Each skipped repeat event kept a place, until the workflow refused every new run with concurrency_limit.
- **Webhooks:** Every webhook attempt, retries included, is now signed when it is sent, with the endpoint's current address and secret. A retry no longer fails your receiver's 5-minute timestamp check, and one after you rotate the secret uses the new one. The event id and body stay the same.
- **Forms:** A public form now takes exactly its limit: by default 20 submissions an hour from one address and 5,000 a day for your organization. The last one allowed was refused before.
- **Platform:** Beta and newsletter sign-ups, visitor uploads, the per-minute email sending limits and the 240 webhook deliveries a minute per organization had the same miscount. They now let their full number through too.
- **Enterprise:** When a company replaces its directory, the new one no longer blocks the people of the old one. Anyone the new directory had not sent yet was blocked and signed out, even people who sign in only by single sign-on.
- **Notifications:** Sending a notification for an event you switched off now answers channels, with email and push false, and notifiedCount 0, beside sent: false. Code that read result.channels.email threw before.
- **Notifications:** Deleting a custom notification event now deletes the email template made for it, as the dialog says. A new event with the same slug, its short id, could pick up the old template.
- **Content:** FAQ questions now come back in the order their collection keeps, through the API and the SDK's faqs.questions(). They came back newest first. Set the order with Move up and Move down on the collection's page.
- **Content:** A top-level blog or docs folder now has its address, so the post editor's folder picker shows it, where it showed empty brackets.
- **Email:** The email editor no longer warns about {{name}} and {{email}} in a campaign to your audience. Both are filled in for every recipient.
- **Email:** The email history now shows each subject with its merge tags filled in, where it showed the raw tags. Sign-in codes and links read [hidden], there and in the inbox title of a workflow's email.

Source: https://www.buildbase.app/changelog/workflow-and-webhook-fixes-found-while-writing-the-guides

## Console fixes found while taking the screenshots

5 November 2026. Push campaigns get an icon, user flags can target audience tags, and a webhook can use an http:// address outside production. Labels and lists are fixed too.

### Added

- **Push notifications:** A push campaign now has an Icon field. Pick an image from your assets or upload one; without one, your organization's icon is used. Before, only the API could set it.
- **Feature flags:** A user flag can now target audience tags, meaning people whose audience contact carries one of the tags. Use the flag's new Tagged audience card, or the routes under /api/features/:id/audience-tags.

### Fixed

- **Webhooks:** In a development or staging environment, a webhook's Endpoint URL now takes an http:// or tunnel address, as the server always did. Production still needs https.
- **Tracking:** Connect your app, under Settings > Tracking & tags, now installs the current SDK. Its first step names 1.0.0 as the oldest release that does everything the screen sets up. It printed @buildbase/sdk@^0.0.68, which kept apps on 0.0.68.
- **Workflows:** Version history now shows the message each version was published with. A step's panel shows the defaults it runs with, so a new Send Email step no longer shows its Email Mode as empty and required.
- **Console:** Organization invitations under Settings > Users now say Member or Admin, as the members table does. An invitation sent as Member read user.
- **Users:** The by-country lists on the Users, Audience, list and workspace pages show only countries with someone in them. They listed every country, most at 0.
- **Content:** A draft post or doc now reads Draft in the Status column, and an unpublished testimonial Unpublished, where the cell was empty. Searching an FAQ collection's questions now matches the question, where any search emptied the list.
- **Console:** Fields and switches that screen readers announced with no name now say what they are. That covers workflow settings and steps, campaign and push forms, Slack event switches and the workspace permission matrix.
- **Console:** Clicking a field's label focuses the field again, in Create workflow, the email template library and user attributes, among others.

Source: https://www.buildbase.app/changelog/console-fixes-found-while-taking-the-screenshots

## Checkout links, your organization's time zone, and form answers kept as typed

5 November 2026. Send a workspace a Stripe checkout link from the console, choose the time zone your reports count days in, and keep form answers in their field's type.

### Added

- **Billing:** A workspace's subscription Actions menu has Checkout link: choose a plan, version, currency and interval, and copy a Stripe checkout link to send to the customer. BuildBase does not email it.
- **Analytics:** Set your organization's time zone under Settings > General. Charts, day counts, the sign-up heatmap, web analytics and revenue then count days in that zone instead of UTC.

### Fixed

- **Billing:** A checkout link can no longer sell a plan you archived to a workspace that never had it, as Change plan and Comp already refuse.
- **Forms:** A public form answer is checked against its field's type and stored by it: a phone number in a text field stays text, wrong types and required fields left blank are refused with every error at once, and keys the form does not have are dropped.

Source: https://www.buildbase.app/changelog/checkout-links-your-time-zone-and-form-answers-by-type

## Purchases are confirmed when buyers return from checkout

5 November 2026. BuildBase can now tell your app whether a purchase a buyer just made on Stripe's checkout page is done, and finishes it itself if Stripe's notification never arrives.

### Added

- **Billing:** A buyer back from Stripe's checkout page can be told whether their plan, add-on, credit pack or saved card is ready, still processing, waiting on a bank payment, or needs a look from support. The SDK's purchase confirmation uses this in its next release.
- **Stripe:** When Stripe's notification of a completed checkout is late or lost, the purchase is finished anyway once the buyer is back: BuildBase reads the checkout from Stripe and applies it the way the notification would have, exactly once.
- **Billing:** An add-on paid by a delayed bank payment now reaches your server-side conversion tracking when the payment clears, as plans and credit packs already did.

Source: https://www.buildbase.app/changelog/purchases-are-confirmed-when-buyers-return-from-checkout

## Plan onboarding inside your app, with SDK 1.1.0

4 November 2026. SDK 1.1.0 brings the New workspaces setting into your app: a plan picker that stays open until a plan is chosen, free plans picked in code, and agent tools.

### Added

- **SDK:** With @buildbase/sdk 1.1.0, your app opens its plan picker by itself for a workspace that must choose a plan, and keeps it open until one is chosen, for anyone who may manage that workspace's billing. Set ui.behavior.planRequiredGate to false to show your own plans instead.
- **SDK:** useSelectFreePlan, and selectFreePlan on the server client, put a workspace or a person on your free plan with no checkout. isPlanRequiredError and onboardingModeOf tell your code which setting applies.
- **Agents:** An agent on your app's MCP server can put a workspace on your free plan itself with select_free_plan. A tool refused because no plan is chosen says plan_required and names the tools that end it. The built-in tools are now 60.

### Improved

- **Billing:** The trial banner, in the console and in apps on SDK 1.1.0, says which plan a trial with no card moves to when it ends, instead of saying it converts to a paid plan.

### Fixed

- **Billing:** A blueprint that starts new workspaces on a trial now says when it plans that Stripe must be connected and the plan's trial must not require a card, instead of being refused partway through the apply.

Source: https://www.buildbase.app/changelog/plan-onboarding-in-your-app-sdk-1-1-0

## New workspaces can start on a free trial

3 November 2026. The New workspaces setting can now give every new workspace a trial of a paid plan, with no card and no checkout page, and move it to your free plan if the trial ends unpaid.

### Added

- **Billing:** Settings > Organization > New workspaces can start every new workspace on a trial of one of your paid plans, with no card. Choose a plan whose trial does not require a card; each workspace gets the version on sale and its trial length.
- **Stripe:** Each trial is a real Stripe subscription in trial, started by the server for the workspace's own Stripe customer. It is set to cancel rather than charge when it ends without a card, so nothing is billed unless someone adds one.
- **Billing:** A trial that ends unpaid moves the workspace to your free plan, under your cancellation settings. One trial per person still applies: someone who already had a trial gets the free plan for their next workspace instead.

Source: https://www.buildbase.app/changelog/new-workspaces-can-start-on-a-free-trial

## New workspaces can start on your free plan

3 November 2026. One setting in the console starts every new workspace on your free plan, with no card and no checkout, wherever the workspace is created: in your app, by an AI agent or through the API.

### Added

- **Billing:** Settings > Organization > New workspaces can start every new workspace on your free plan, with no card and no checkout. It applies wherever the workspace is created: your app's create button, the first workspace made at sign-up, an AI agent or a direct API call. A workspace that never had a plan starts on it the next time it is opened.
- **Billing:** You choose the free plan, not a version of it. Each new workspace gets the version on sale at that moment, so publishing a new version of your free plan needs no change to the setting. With one free plan, it is chosen for you.
- **Stripe:** When Stripe is connected, each workspace started on the free plan gets its Stripe customer in the background, so a later upgrade, the billing portal and a saved card all use it.
- **SDK:** Your app can read whether new workspaces start on the free plan from the public settings it already loads (billing.onboarding.mode).

### Fixed

- **Billing:** The workspace onboarding setting in a blueprint said new workspaces start on its plan, but nothing applied it. Its free plan mode now works. Its trial mode is accepted but starts no trial yet, and the reference says so.

Source: https://www.buildbase.app/changelog/new-workspaces-start-on-your-free-plan

## Every organization gets its own free sign-in address

2 November 2026. Your users now sign in on an address that is yours alone, where every tag you attach loads. Pick a custom domain for one app, or make it the default.

### Added

- **Sign-in page:** Every organization now has its own sign-in address, free on every plan: your organization ID followed by .auth.buildbase.app. Apps with no custom domain sign in there, and an environment's address adds its key after the ID.
- **Tracking:** Only your own users sign in on that address, so every tag you attach loads there, Google Tag Manager and your own scripts included. On the shared sign-in address, only vendors' fixed tags load.
- **Console:** Authentication > Domains opens with a Sign-in addresses card. It shows your included address, the default for your apps, and where each app signs in and why.
- **Console:** Each app can sign in on an address of its own. Pick it in the app's Sign-in address field under Authentication > Settings. Several apps can share one address.

### Improved

- **Passkeys:** Passkeys made on the shared sign-in address keep working on your new address, so nobody has to set one up again.
- **Custom domains:** Adding or verifying a custom domain no longer moves anyone's sign-in. A domain is used once you choose Use as default on its row, or pick it for one app. An organization already signing in on its custom domain keeps it.
- **Custom domains:** Picking a custom domain, as the default or for one app, needs a plan that includes custom domains, as adding one already did. Otherwise the pick is refused with 402.
- **Console:** Before you change the default address, the console names the apps that will move. Each change is kept in the security audit log as sign_in_address.changed or sign_in_address.default_changed.
- **Google One Tap:** Google shows One Tap only on addresses listed on your Google client. The Google sign-in settings now list every address your apps sign in on, default first, each with a Copy button.
- **Google One Tap:** Moving an app, or the default, to another address now reminds you to add it under Authorized JavaScript origins on your Google client.

### Fixed

- **Security:** A sign-in link opened on another organization's sign-in address is now refused, and the page says to go back to the app and start again. Before, the page took its organization from the link alone. The API answers 403 SIGN_IN_ADDRESS_MISMATCH.
- **Custom domains:** BuildBase's own domain, buildbase.app and every address under it, can no longer be added as a custom domain. It is refused with 400 PLATFORM_DOMAIN, and nothing is reserved.
- **Tracking:** A second verified custom domain now loads every tag your app attaches, as the first one already did.

Source: https://www.buildbase.app/changelog/every-organization-gets-its-own-free-sign-in-address

## A compact sign-in page, styled from one Branding page

2 November 2026. The hosted sign-in page is shorter, with three layout settings you can combine. A new Branding page in the console holds every part of its look.

### Added

- **Console:** A new Branding page, under User management > Access beside Authentication, holds every setting for the sign-in page's look. It replaces Authentication's Sign-in page tab, and old links to that tab forward there.
- **Branding:** Three layout settings combine: Frame (Card or Frameless), Brand panel (None, Left or Right) and Sign-in flow. Left and right swap in right-to-left languages.
- **Branding:** Sign-in flow is Automatic, All on one screen or Email first. With password sign-in on, Automatic asks for the email first once SSO is on or more than three other ways in are.
- **Branding:** Email first's second step looks the same for every address, so the page never says whether an account exists.
- **Branding:** The live preview draws the page by the hosted page's own rules. It says whether the page fits a 1280 x 720 laptop or a 360 x 740 phone.
- **Branding:** One app's own name, logos, tab icon and brand colour move from the app's Edit sheet to Branding, under One app's own look. The Edit sheet shows a summary and links there.
- **Sign-in page:** Custom CSS can reach the new parts of the page: bb-topbar for the top bar, bb-other-ways for the other ways in, and data-bb-frame and data-bb-flow on the page.
- **API:** A sign-in screen of your own can read the new layout settings. GET /api/v1/auth/config carries them under branding.layout: frame, flow, languagePicker and visibleMethods.

### Improved

- **Sign-in page:** The hosted sign-in page is shorter. With password, emailed link, passkey, Google and GitHub on, it now fits a 1280 x 720 laptop screen.
- **Sign-in page:** The logo sits inside the card. The language picker moves to a bar above it, and the badge and your links to a bar below.
- **Sign-in page:** Behaviour change: an organization that never saved a layout setting gets the new look, because the defaults changed. Settings you saved are kept.
- **Sign-in page:** With more than three other ways in, such as passkey, SSO or wallet, two show under the form. They are passkey and SSO unless you pick others, and the rest open from Other ways to sign in.
- **Sign-in page:** With five or more social providers, the buttons become one row of icons. Each icon keeps its provider's name for screen readers.
- **Sign-in page:** Help shows up when it helps. A passkey's explanation appears after an attempt fails, and Forgot password? sits on the Password label's row.
- **Sign-in page:** Sign-up ends with Already have an account? Sign in. Forgot and reset password, two-step sign-in, the age question and email verification get a quiet Back to sign in link.
- **Accessibility:** Links on every hosted screen share one style: muted and underlined, in your brand colour on hover. Before, a light brand colour could make links hard to read.

Source: https://www.buildbase.app/changelog/a-compact-sign-in-page-styled-from-one-branding-page

## Require a plan before a workspace is used

2 November 2026. The same New workspaces setting can now require every workspace to choose a plan, free or paid, before it records usage or spends credits, and it tells your app and AI agents how to choose one.

### Added

- **Billing:** Settings > Organization > New workspaces has a third choice: require a plan before a workspace is used. Until a plan is chosen, recording usage and spending credits are refused with the code PLAN_REQUIRED. Reading, members, settings and billing stay open, so a plan can always be chosen. It applies to workspaces that have no plan today too.
- **API:** The refusal names the routes that end it: the one that lists the plans, the one that selects a free plan and the one that starts a checkout. A workspace's subscription read says planRequired before anything is refused.
- **SDK:** With the next SDK release, your app opens its plan picker by itself for a workspace with no plan and keeps it open until a plan is chosen, for anyone who may manage that workspace's billing. An app that shows its own plans can turn this off.
- **AI agents:** With the next SDK release, an agent on your app's MCP server is told it needs a plan, and which tools choose one, and can put the workspace on your free plan itself with select_free_plan. A paid plan still goes to a person for the card.

Source: https://www.buildbase.app/changelog/require-a-plan-before-a-workspace-is-used

## BuildBase has a Free plan, and paid plans from $19 a month

1 November 2026. BuildBase's own plans now start with Free, at $0 with no card. Paid plans start at $19 a month, each after a 7-day trial that needs no card.

### Added

- **Pricing:** BuildBase now has a Free plan beside Launch, Grow and Scale. It costs nothing, needs no card and has no trial. Paid plans start at $19 a month or $190 a year, after a 7-day trial that needs no card.

### Improved

- **Pricing:** Free stops at its allowances and is never billed for overage, the usage past an allowance. On paid plans, workflow runs, web analytics events and storage are billed past the allowance. Every other allowance is a hard limit.
- **Console:** The console's plan picker for a new organization now offers Free beside the paid plans. Its panel reads Start on Free, or try a paid plan free for 7 days.
- **Website:** The homepage, the pricing page and the FAQ now describe the Free plan. Sign-up buttons read Start free instead of Start free trial.
- **Website:** On the pricing page, the plan cards sit in one row. On screens narrower than 1024 pixels, the row scrolls sideways instead of stacking.
- **Website:** The pricing and self-hosting pages now say self-hosting is priced per installation and arranged by talking to us.

Source: https://www.buildbase.app/changelog/buildbase-has-a-free-plan

## Console tabs follow your environment, and environment fixes

1 November 2026. A console tab now follows a switch made in another tab, and a closed environment answers 401. The environment menu shows how many your plan allows.

### Improved

- **Environments:** The console's environment menu now shows how many environments your plan allows besides production. It reads, for example, 1 of 2 environments besides production. At the limit, it offers Upgrade for more environments. Before, a number showed only once an add was refused.
- **Console:** A downgrade can leave you over your plan's limit on team members, open invitations or environments. Adding one more then says how many to remove. For example, with 4 environments on a plan that includes 2, it says to remove 3.

### Fixed

- **Console:** A console tab now follows an organization or environment switch made in another tab of the same browser. Before, it kept showing where it was while its requests went where the other tab went. It now moves there without reloading the page, and a message says where it is.
- **Environments:** A request signed in to an archived environment now answers 401 with ENVIRONMENT_NOT_FOUND, instead of a 500 server error. A console tab inside that environment moves to the organization's production by itself, and says That environment no longer exists.
- **Console:** In a development or staging environment, the dialog showing a new client secret now gives the organization ID your app needs. An Environment row sits beside it. Copy all four puts both in your env variables, as NEXT_PUBLIC_BUILDBASE_ORG_ID and NEXT_PUBLIC_BUILDBASE_ENVIRONMENT. Before, the ID it gave was refused by the SDK at start-up.
- **Console:** In a development or staging environment, Test OAuth2 flow now uses that environment. So do the Connect your app steps under Settings > Tracking & tags. Before, they pointed at production, which refused them.
- **Console:** A setup welcome you dismiss, and the plan usage meters, now keep to the organization and environment you are in. Before, a dismissed welcome stayed hidden in every other environment, and a meter could briefly show the previous environment's count.
- **Security:** A read-only support session that BuildBase staff open for a development or staging environment now stays there. Before, the console opened it in production instead.

Source: https://www.buildbase.app/changelog/console-tabs-follow-your-environment

## Workspace owner and invite rules, and plan allowance fixes

31 October 2026. A workspace owner's role stays fixed, and Admin only invitations hold in the API. A workflow's marketing email now stops at your monthly allowance.

### Fixed

- **Workspaces:** A workspace owner's role can no longer be changed through the members API, by an admin or by the owner. The owner holds every permission whatever the role says. A change only made the member list, the role-change email and workspace.member_role_changed show the wrong role. The request now answers 409 WORKSPACE_OWNER_ROLE_FIXED.
- **Workspaces:** Setting Can invite members to Admin only now holds in the API, not only in the SDK's screens. Only the workspace's owner and its admins can invite, resend an invitation or add a member. Anyone else gets a 403, even when their role includes inviting. For them, GET /api/v1/public/workspaces/:workspaceId/permissions/me now leaves out workspace:members:invite.
- **Billing:** Your app's plan pickers no longer offer a plan you archived, except to a workspace or person already on it. Before, an archived plan left in a current pricing group could still be picked. Checkout then failed with Plan version not found. The fix is on the server, so it needs no SDK update.
- **Workflows:** A workflow's Send Email step set to Marketing now checks your plan's monthly marketing email allowance first. Campaigns and one-off sends already did. Once the month's allowance is used up, the step is skipped with the reason quota_exhausted. Before, it sent anyway. Transactional steps are never counted or capped, and an environment uses its own allowance.
- **Webhooks:** You can now add as many webhook endpoints as your plan includes. A platform cap stopped every organization at 10, below what some plans include, with a platform message. That cap is now 100, so your plan's own limit is what you reach first.
- **Authentication:** When several people sign up at once, such as a burst of guests, each new user now counts once against your plan's end-user limit. Before, one could be counted twice, so someone could be turned away while there was still room.

Source: https://www.buildbase.app/changelog/workspace-owner-and-invite-rules-and-plan-allowance-fixes

## Workspace role limits, usage bounds and safer sign-in page tags

31 October 2026. Workspace members can no longer grant more access than they hold, usage reports are whole numbers up to 1,000,000, and the shared sign-in page loads fewer tags.

### Improved

- **Sign-in page:** Behaviour change: BuildBase's shared sign-in address now loads only tags a vendor publishes and you set up with an ID. Those are GA4, Google Ads, Meta, X, LinkedIn, TikTok, Reddit, Microsoft Advertising, Plausible and Ahrefs. Google Tag Manager containers, custom scripts and session recorders (Clarity, Hotjar, PostHog) no longer load there. Every organization's users sign in on that one address, so it runs no code a single organization controls. On your own verified sign-in domain, every tag still loads.
- **Billing:** Behaviour change: each usage report must now be a whole number from 1 to 1,000,000. A fraction or a larger amount answers 400, and nothing is recorded or billed. Send a larger amount as several reports. This holds for single and batch reports, from the SDK, the server SDK or the console API. Before, any amount of 1 or more was taken, and 1.5 was billed as 2.

### Fixed

- **Workspaces:** Workspace members can no longer give anyone more access than they hold. Only the workspace's creator and its admins can make someone an admin. Anyone else cannot change their own role, act on a member who holds more than they do, or grant a permission they lack. This covers changing a member's role, editing the workspace's role permissions, adding a member and inviting one. A refusal is a 403 with a sentence that says why.
- **Workspaces:** Behaviour change: an admin who did not create the workspace can no longer change their own role, and gets a 403. The SDK's member list already keeps that choice switched off. Workspaces on the default roles see no other difference, since only admins hold these permissions there.
- **Email:** In a workflow's Send Email step with Custom Content, merged values now arrive in the HTML as plain text. A name or form answer typed as a link or an image shows as those characters, never as a working link or image. Your own markup around the merge tag is sent as you wrote it. Behaviour change: a step output you merged in as HTML now shows as text.

Source: https://www.buildbase.app/changelog/workspace-role-limits-usage-bounds-and-sign-in-page-tags

## An AI agents page, 11 new docs pages and SDK 1.0.0 in the docs

31 October 2026. A new website page shows how AI agents reach the app you build, and the docs gain 11 pages. Docs that said the next SDK release now name 1.0.0.

### Added

- **Website:** A new AI agents page, at /ai-agents, shows how your users connect Claude, ChatGPT or Cursor to your app. They connect through MCP, the protocol AI agents use to reach an app.
- **Documentation:** The docs gain 11 pages. Billing and credits cover managing subscriptions from the console, seat-based pricing, and spend caps with usage alerts. Email covers scheduling and A/B testing campaigns, deliverability, and unsubscribes with double opt-in.
- **Documentation:** Other new pages cover your console team and its roles, environments in the console and the buildbase CLI. Workflow versions and history, and workspace mode and limits, get pages too.

### Improved

- **Website:** The homepage and the features page now name enterprise sign-in, AI agents and self-hosting, each linked to its page. The billing and credits pages list every capability those modules ship.
- **Documentation:** Docs pages that said a feature needs the next, unpublished SDK release now say @buildbase/sdk 1.0.0 or later.
- **Website:** The cookie policy now lists the cookies BuildBase's own analytics sets on buildbase.app. They are bb_vid and bb_sid for visits, and bb_attr for ad clicks. Each is written only after you accept that kind of cookie.

Source: https://www.buildbase.app/changelog/ai-agents-page-and-11-new-docs-pages

## Everything new in October, one line per feature

30 October 2026. Every feature shipped in October, one line each, with the details in the entries that follow. They cover enterprise identity, new ways to sign in, plans for people, add-ons, coupons, Stripe Tax, checkout inside your app, credits, plan versions, environments, web analytics, agents and email.

### Added

- **Enterprise:** The companies you sell to get single sign-on and directory sync, through your own WorkOS account. Their people sign in with the company's own identity provider, and their accounts follow the company's directory. Companies also get admins, roles and groups (groups inside groups, group managers), and an audit trail with log streams and WorkOS audit logs. A company can verify its domains and let people join by domain. It can also set an access policy, sign its people out, have several identity providers and set stricter rules for one workspace.
- **Enterprise:** A company's own tools can call your app too, with company API keys, or through service accounts that use workload identity, so an automated job needs no stored key. AI agents can be approved by the company's identity provider. The entries of 12 and 19 October have the details.
- **Sign-in:** Your users have new ways to sign in: email and phone sign-in codes, Sign in with Apple, your own OpenID Connect provider, and Ethereum and Solana wallets. Two-step sign-in, bot protection, sign-up allowlists and a waitlist are new too. The hosted sign-in page speaks eight languages and carries your own branding.
- **Sign-in:** People can use those sign-in methods in new ways: with a username, or as a guest account that keeps its data. Device code sign-in works for a command-line tool (CLI) or a TV, and Google One Tap is now an option.
- **Billing:** You can sell a plan to a person, not only to a workspace. Someone else can pay for a workspace on their own card. A workspace plan can also give its owner or members something of their own, for family and group plans.
- **Billing:** You can cap overage, the usage past a plan's allowance, and set usage alerts. Allowances can be per member with a shared pool, and you can name billing contacts. Plans can set counted limits on devices, owned workspaces and connected agents. Every stored file is shown against your storage allowance.
- **Add-ons:** You can sell add-ons on top of a plan, in four shapes. They are a one-time unlock for a set number of days, a lifetime unlock, a consumable pack, and recurring units billed with the plan. The entitlement checks that decide what a customer may use read add-ons too. They can be refunded from the console, have versions like plans, and can be upgraded for the difference.
- **Coupons:** You can offer coupons and promotion codes, under Billing > Subscriptions > Coupons. Customers can use them from a ?promo= link, the plan picker, a plan change or a credit pack. Codes are checked before anyone pays, and you can limit one to chosen plans.
- **Stripe:** Customers can check out, add cards, pass 3-D Secure (the bank's extra check on a card) and pay held invoices without leaving your app. Stripe Tax works on your own Stripe account. Overage and seats can use graduated and volume tiers, reported through Billing Meters (Stripe's usage meters). Billing writes take an Idempotency-Key, so a request sent twice is applied once. Billing health shows where a subscription and Stripe disagree, and Sync with Stripe covers plans published before you connected it. Test clocks (Stripe's simulated time) work with test keys.
- **Credits:** Credit holds reserve credits before a job runs, then settle at the job's real cost. Credits can top up automatically on a saved card. A person can have their own credit wallet, and credit packs have versions.
- **Plan versions:** You can publish a new version of a plan, add-on or credit pack and choose who moves to it, with a preview first. Gains apply at once, and losses only after 7 to 365 days' notice.
- **Billing:** A trial can be offered once per person. Customers who cancel are asked why, and you can make them an offer to stay or offer a pause. If you allow it, they can end a subscription now, with a credit or a refund. Every subscription checkout shows the renewal terms beside it.
- **Entitlements:** Your app can check what a plan allows, add-ons included, whether the plan belongs to a workspace or to the signed-in person. In code, useEntitlement, useLimit and WhenEntitled do the reading.
- **Environments:** You can have development and staging environments, now rolling out to organizations. Each is its own tenant, fully separate, with its own database, users, keys, webhooks, senders and monthly allowances. Environments are never billed, and you can promote templates, workflows and plans from them to production.
- **Tracking:** The console has web analytics that show the revenue each source brings. Counting waits for the visitor's consent, and so do session recorders. X Pixel conversions now reach X in a form it can count.
- **Agents:** MCP servers, which let AI agents use your app, run on protocol version 2026-07-28 and publish a server card that describes them. A consent screen lists everything an agent gets, and a terminal can sign in with a device code. The npx @buildbase/sdk agent commands check a server, make install links and draft a listing.
- **Email:** Campaigns can be scheduled, and their subject lines A/B tested. A warm-up sends big lists a 5% sample first, and sending health pauses a campaign when bounces or complaints climb. Amazon SES works as a sender. A server API covers transactional email, the one-to-one mail your app sends, and subscribers. Mail goes out only through your own provider, and there is a public newsletter archive. Each sending domain gets Gmail Postmaster Tools. Marketing mail needs an unsubscribe link and your postal address.
- **Console:** You can set up an organization from one file. Your team gets an Actions menu on subscriptions and a Revenue page. Your console login can use two-step sign-in, and you can sign in as a user. You can import users from Clerk, Auth0, Firebase or Supabase. There are admin and app-server API keys, and plans and credit packs can be archived.
- **Authentication:** Hosted sign-up can ask for a minimum age, from 13 to 21. The check is optional, and a date of birth is never stored.
- **SDK:** @buildbase/sdk 1.0.0 brings all of this to your app. From 1.0.0 on, one npm update takes every 1.x release.

Source: https://www.buildbase.app/changelog/october-2026-feature-by-feature

## Change your prices without changing what customers bought

30 October 2026. Plans, add-ons and credit packs have versions, and you choose who moves to a new one, with a preview first: gains apply at once, losses only after notice. Buyers of a one-time or lifetime add-on keep what they bought or upgrade for the difference.

### Added

- **Billing:** When you publish a new version of a plan, you decide whether its customers move. You can keep them where they are, move the customers who only gain, or move everyone. Anything taken away comes with 7 to 365 days' notice (30 by default). The console shows who moves, when and at what price before you confirm. A gain applies at once, while a loss is emailed first and applies at the customer's renewal. A move started with an API key or a blueprint (your setup file) waits for a confirmation in the console.
- **Billing:** Add-ons and credit packs have versions too, with a history and a draft editor in the console. Customers with a recurring add-on, and auto top-ups, can be moved to a newer version. A buyer of a one-time or lifetime add-on keeps the version they bought, and can upgrade to the one on sale for the difference. A lifetime add-on can also include every later version at no charge.
- **Webhooks:** Your app hears about each version move through webhook events: subscription.version_move_scheduled, subscription.version_moved, subscription.version_move_withdrawn, version_move.completed and version_move.cancelled. For an upgraded add-on, addon.purchased carries the cause upgrade. When you read a subscription, it includes scheduledVersionChange. Blueprints now cover add-ons, coupons, versioned credit packs and a plan's move setting.
- **Console:** You can see billing that went wrong in one place: Billing > Billing health. It lists where a subscription and Stripe disagree, billing operations left part way, plan credits that could not be granted and version moves delayed past their window. In settings, a Billing versioning card lets you turn each part of versioning off for one organization.

### Improved

- **Billing:** Behaviour change: to change what a published plan version, pricing group version or add-on sells, publish a new version. Editing it now answers 409 VERSION_REQUIRED, where it answered 400. A published version's trial can no longer be edited, so that needs a new version too. Changing a catalog item or feature that customers hold answers 409 CATALOG_ITEM_SOLD. Deleting a credit pack in use answers 409 CREDIT_PACKAGE_IN_USE instead of 400.

Source: https://www.buildbase.app/changelog/versions-for-plans-add-ons-and-credit-packs

## Ending a subscription now, refunds, and paying inside your app

30 October 2026. You choose whether customers can end a subscription now and what they get back, and you set more billing rules yourself. Customers can add a card, complete their bank's 3-D Secure check and pay a held invoice inside your app.

### Added

- **Billing:** You choose whether customers can end a subscription now, and what they get back, under Settings > Organization > Cancellation. They can get nothing, a prorated credit or a prorated refund (for the unused part of the period). You can also give nothing once the period's allowance is used. The same page decides whether customers may switch billing interval themselves. It also decides whether a plan's lapse policy (what happens to an unpaid plan) still applies after Stripe ends the subscription for failed payments. Your team can end any subscription now from the console.
- **Billing:** You can set more billing rules yourself. Choose what a paid plan change does to top-up plan credits: keep them, end them, or keep them only on upgrades. Set how many seats a trial holds, and whether customers may turn on automatic credit top-ups and how many a month. And decide whether people who unsubscribed from billing mail still get notices of a price rise, a failed payment or a plan ended unpaid.
- **Console:** You can archive and unarchive plans, credit packs and product categories. An archived plan leaves pricing pages and new checkouts, but its subscribers keep it. An archived credit pack goes off sale, and credits already bought stay.
- **Billing:** You can make the same choices in your setup file, a blueprint. Its billing.customerBilling field takes cancel, refundOnCancelNow, intervalSwitch and afterFailedPayments.

### Improved

- **Billing:** Customers can add a card, make it the default, complete 3-D Secure (their bank's extra check on a card) and pay a held invoice without leaving your app. This needs @buildbase/sdk 1.0.0, with Stripe.js passed to the provider. End trial and pay now shows the charge and the card first. Previews of a plan change list what the customer gains and loses, and so do previews of buying, reducing or cancelling an add-on.
- **Console:** You can build a pricing group for people entirely in the console, because the product dialog can now make an item sold to a person.

Source: https://www.buildbase.app/changelog/cancel-now-refunds-and-paying-in-your-app

## Age check at sign-up, renewal terms, recording only with consent

30 October 2026. Hosted sign-up can ask for a minimum age, and every subscription checkout states its renewal terms. Session recorders wait for consent, marketing email needs your postal address, and the sign-in page's fonts no longer come from Google.

### Added

- **Authentication:** Hosted sign-up can now check that people are old enough. The check is off until you turn it on in the Sign-up tab, and you set a minimum age from 13 to 21. People answer "I am N or older" or give a date of birth, which is never stored. Existing accounts answer it at their next sign-in, and an account that is refused has its sessions ended.
- **Billing:** Buyers see that a subscription renews automatically before they pay. Every subscription checkout shows the auto-renewal terms above Stripe's Subscribe button. They appear in the buyer's language when your app passes one of the SDK's eight locales. You can add your own cancellation or renewal policy after them, under Settings > Organization > Your policy at checkout.

### Improved

- **Email:** Behaviour change: a marketing email with no postal address is now refused, where before you got a warning. A scheduled campaign is checked again when it sends. Workflow Send Email steps, Compose email and one-off sends gain an Email type. Marketing mail sent from them needs an unsubscribe link and your address, as campaigns do.
- **Tracking:** Session recorders now wait for the visitor's consent. From @buildbase/sdk 1.0.0, Microsoft Clarity, Hotjar and PostHog load only after the visitor agrees to analytics, never on a regional default. You can mark any other external script Records sessions in Settings > Tracking & tags, so it waits the same way.
- **Sign-in page:** Visitors' browsers no longer contact Google Fonts on your hosted sign-in page, because BuildBase now serves the twelve font families the page offers.

Source: https://www.buildbase.app/changelog/age-check-renewal-terms-and-consent

## Members can leave a workspace, plus key, email and Stripe fixes

30 October 2026. Any member can now leave a workspace, and an organization API key stays inside its organization. A campaign sent from several servers goes out once, a repeated Stripe event is processed once, and a Redis timeout answers a 503 your app can retry.

### Added

- **Workspaces:** Any member can now leave a workspace, with Leave workspace in the SDK's settings from 1.0.0. The workspace's creator cannot leave, and neither can the person whose card pays for it: they get 409 WORKSPACE_OWNER_CANNOT_LEAVE or PAYER_STILL_PAYS. Separately, deleting an account is no longer refused when the person uses a Free workspace alone.

### Improved

- **Authentication:** You can now choose how long people stay signed in. Set refresh token lifetimes on the Security tab: an app's from 1 to 365 days, with an optional idle limit, and an agent's idle limit and maximum. A switch on the WorkOS provider card keeps people blocked by a company's directory out of your end-user count.
- **Console:** Theme and Contact support move into the avatar menu, and tables keep their rows while they refresh. Emptying the organization domain field now clears it. Old console addresses forward to the new ones, with their query and fragment.
- **Billing:** Only marketing email counts toward your plan's email quota, not sign-in or other transactional mail.

### Fixed

- **Security:** An organization API key now acts only on its own organization. It is refused on its creator's personal routes, such as the Security page and switching organization.
- **Security:** The member list returns only the fields the console shows, and a subscriber's name can no longer add a hidden recipient to an email.
- **Email:** A campaign sent from several servers now goes out once. Before, it could reach some people twice, or be marked sent while some batches never went out. Each batch is now sent and counted once.
- **Billing:** A Stripe event sent again is no longer processed twice, and a change to your Stripe keys reaches every server at once. When Stripe reports the payment before the checkout, a period's plan credits are now granted once.
- **Billing:** A person's Free plan now sends subscription.created, and a promotion code given at checkout sends subscription.discount_applied once. A Stripe endpoint made before 23 October needs two events added: customer.discount.created and invoice.voided.
- **Platform:** If Redis (a data store BuildBase runs on) times out, sign-in and billing requests now answer a 503 your app can retry. Before, they answered a 500, or a 400 carrying the raw error. A cached public answer is now always a success, so an error is no longer replayed as a 200 for the cache's lifetime.
- **Platform:** A file uploaded under an unknown field name is now refused with a 400, instead of hanging.
- **Workspaces:** An invitation sent with no landing address now lands on the app it was sent from. It used to land on the auth client's first redirect URL, such as localhost:3000.

Source: https://www.buildbase.app/changelog/leave-a-workspace-and-fixes

## Web analytics that shows the revenue each source brings

29 October 2026. The console now has web analytics: visitors, sources, pages, goals and campaigns, with the revenue and customers each source brought. You can follow each visitor's journey, counting respects consent, and no raw IP address is kept.

### Added

- **Tracking:** The console has new Analytics pages, with the revenue and customers each source brought. They show visitors, page views, bounce rate, visit length, sources, pages, locations, devices, goals and campaigns. There is a journey for each visitor, and an Acquisition card on every user and workspace page. Apps on @buildbase/sdk 1.0.0 count visits through SaaSOSProvider or BuildBaseTracking, unless you pass analytics: false. Goals come from trackGoal or a data-bb-goal attribute, and no raw IP address is kept.
- **Tracking:** You can turn web analytics on or off, and choose which sites count. Settings > Analytics has a Collect web analytics switch for each organization and environment, and lists the sites sending your organization ID. Your own domains count at once, and any other site waits until you Track or Block it. In the EEA, the UK and Switzerland, a visit is counted with no ID or cookie until the visitor agrees.

Source: https://www.buildbase.app/changelog/web-analytics-with-revenue-by-source

## Billing fixes, and checks that catch a wrong price or Stripe key

29 October 2026. A downgrade on another billing interval now credits unused time already paid for, and bursts of usage are billed in full, once. A price can no longer be set twice in one currency, and a test Stripe key cannot be paired with a live one.

### Added

- **Billing:** Your pricing page can now tell which plan a subscriber is on without comparing names. Each plan in GET /api/v1/public/:orgId/plans/:groupSlug names its plan, with _id and slug, so you can match on planVersion.plan._id instead of the name.
- **Billing:** The Usage screen in @buildbase/sdk 1.0.0 now prices overage (usage past the allowance) in the currency the subscription bills in. GET /api/v1/public/workspaces/:id/subscription answers subscription.currency, the lower-case code it bills in (null on a Free row).

### Improved

- **Billing:** A price can no longer be set twice in one currency. A plan version, credit pack or add-on that prices one currency twice is refused with 400 ("USD is priced twice: send one price per currency."). Before, it was saved, and the price shown could differ from the one charged.
- **Billing:** Billing > Credentials no longer accepts a test key beside a live one. A publishable key and a secret key from different Stripe modes, such as pk_test_ beside sk_live_, are refused with 400 STRIPE_KEY_MODE_MISMATCH. Before, the pair was saved and payments then failed.
- **Billing:** Payment webhooks details now show the Stripe event ID, under Webhook event. Prices made in Stripe for a plan version carry your organization id in their metadata (the extra labels Stripe keeps on a price), as other prices already did.

### Fixed

- **Billing:** Moving to a cheaper plan on a different billing interval, such as yearly to monthly, now credits the unused time already paid for. The change takes effect at once. Before, that paid time was lost, and the old plan stayed on until the end of the new period. A downgrade on the same interval, or during a trial, still waits.
- **Billing:** Bursts of usage are now billed in full, once. When several calls report usage at the same moment and together cross an allowance or a billing block, every block is billed once. Before, part of a burst could go unbilled.
- **Billing:** Cancelling or resuming a subscription that Stripe had already ended now closes it the way Stripe's own cancellation does. The subscription.canceled event is sent, and the period's plan credits end.
- **Billing:** A deleted plan version or pricing group version draft can no longer be published by its id. It answers 400 and says to unarchive it or create a new version.
- **Console:** Price fields in the plan version, pricing tier and credit pack editors now keep what you type until you leave the field. Before, typing 29 saved 2.01.
- **Console:** Load more on a workspace's invoices now adds the next, older page, instead of the same 20 again.

Source: https://www.buildbase.app/changelog/billing-fixes-and-price-safeguards

## Console and webhook fixes, updated legal pages, and easier docs

29 October 2026. Remove webhook now says what it does, slug fields keep their hyphens, and console pages fit phones. The Terms and privacy pages are updated for October 2026, and every docs page links to the next one.

### Added

- **Environments:** Each environment's home page has a Test mode switch, which is on unless you turn it off. Test mode uses sign-in code 424242 and sends no mail to +test addresses, and each change to the switch is audited. Promoting a workflow never copies an HTTP step's address or headers: the environment keeps its own.
- **Documentation:** Each docs page now ends with when it last changed, and links to the previous and next page. The address docs.buildbase.app/ opens the introduction instead of a blank page. Every page starts with a Skip to content link, and each section's overview page is named after its section.
- **Website:** Posts on the website end with up to three Keep reading suggestions, and long guides open with On this page, a list of their sections.

### Improved

- **Webhooks:** The Remove webhook dialog now says what happens. The endpoint stops receiving events and leaves the list, but its delivery history is kept. It cannot be turned back on, so add it again to resume. The dialog used to say it was permanently deleted.
- **Email:** Marketing templates in the email library now put your postal address in the footer, as {{companyAddress}}, where they showed a sample street.
- **Email:** The emails BuildBase sends your team no longer load Google Fonts.
- **Website:** The Terms of Service now say who may use BuildBase: 18 or older, or the age of majority. They set out your duty under COPPA, the US children's privacy law, for apps aimed at children. They explain how to send a DMCA notice or counter-notice about copyright, and say that paid plans renew automatically. The sub-processor list, the companies that handle data for BuildBase, adds Cloudflare. The privacy, cookie and sub-processor pages are dated October 2026.
- **Console:** The organization tile in the rail now always shows its switch badge, with a Switch organization tooltip and a focus ring. The loading screen stays centred while the console opens.

### Fixed

- **Webhooks:** After you create a webhook, the pop-up message (toast) now says to copy the secret shown above, and labelled copy buttons across the console read Copy.
- **Console:** When your organizations cannot be loaded, the console now says why and offers Try again. Before, it showed No organizations yet with a Create button.
- **Console:** Set default on a pricing group shows that it is working, and cannot be pressed twice. A plan version's Publish button follows the permission the server checks.
- **Console:** A workspace's quotas now read Unlimited or Not in plan, instead of a dash. Archiving a product says Product archived, and a credit transaction with no description reads No description.
- **Console:** Slug and key fields keep a hyphen or space as you type it, so workspaces-owned-per-user is no longer saved as workspacesownedperuser. A new product, plan or category keeps filling its slug, its short id, from the name.
- **Console:** On a phone, a plan version's price and quota tables now scroll sideways in their own box, and Compose email fits a 360px screen. With four or more plans, a pricing group preview lines each price up under its plan.
- **Console:** Links now rest in the link colour, which passes contrast checks. The payment credentials page names the API keys page, instead of saying click here. Each hosting mode in Create organization is a button a keyboard can reach.

Source: https://www.buildbase.app/changelog/console-webhooks-legal-and-docs-polish

## X Pixel conversions that X can count, and page visits inside your app

26 October 2026. Conversions sent to the X (Twitter) Pixel now reach X under the code it counts, whichever form of the ID you pasted, and carry only what X reads. Every move to another page inside your app records a visit with X, and the console checks X conversion IDs as you type and points out conversion labels left blank.

### Improved

- **Tracking:** A conversion sent to X carries only what X reads: the value, currency and items of a purchase, a description, status or search string when your app sets one, and the event ID it uses to drop a duplicate. The visitor's Google and Meta click IDs, UTM tags and your own event fields no longer reach X. From @buildbase/sdk 1.0.0.
- **Console:** Settings > Tracking & tags checks X conversion IDs as you type and refuses a code copied from another pixel's event. Editing a Google Ads, X or LinkedIn tag names the sign-up, trial and purchase events it would not report, and a tag with no conversion labels at all is marked in the list.
- **Tracking:** The Providers page lists the two hosts X sends its data to, t.co and analytics.twitter.com, for a site whose Content-Security-Policy would otherwise block every X hit while the page looks fine.

### Fixed

- **Tracking:** X Pixel conversions are counted. An ID pasted the way X Events Manager lists it, such as o4d5e6, went out without its pixel, so X credited it to nothing; it is now sent as the full tw- code X expects, and a code pasted whole still works. From @buildbase/sdk 1.0.0.
- **Tracking:** X records a page visit each time someone moves to another page inside your app, not only on the first page they load, so an X audience built on pages visited, such as everyone who opened pricing, fills up. From @buildbase/sdk 1.0.0.

Source: https://www.buildbase.app/changelog/x-pixel-conversions

## Development and staging environments, each its own tenant

25 October 2026. Development and staging environments are rolling out to organizations. Each one has its own database, users, keys, webhooks and senders, works on first use, and promotes its templates, workflows and plans to production when they are ready.

### Added

- **Platform:** Environments, rolling out to organizations: once the console shows Environments under Settings > Organization, add one there or with npx @buildbase/sdk env create <name>. Each environment is a tenant of its own: its users, sessions, workspaces, audience, lists, tags, email history, workflow runs, files, API keys, client secrets, webhook endpoints, senders and Stripe keys are never shared with production or another environment. Your team is shared, and you choose which environments each member may enter. Production is your organization itself, unchanged.
- **SDK:** An environment option on the provider and the server client: the environment's key from the console, or nothing for production. It is never guessed from NODE_ENV. npx @buildbase/sdk init --dev wires an app to your Development environment, client secret included, and buildbase env list, use, create, diff, push and pull manage them from the terminal. The SDK's MCP server gains environment_list and environment_create for coding agents. From @buildbase/sdk 1.0.0; an older SDK ignores the environment option and talks to production.
- **Authentication:** A new environment signs people in on first use: Google and GitHub sign-in through shared apps, with no OAuth app of your own, redirects to localhost, and a ribbon on the hosted sign-in pages naming the environment. In test mode, an address ending in +test is never sent mail and every code it asks for is 424242, so automated tests sign up and sign in with no mailbox.
- **Email:** An environment with no sender of its own sends through a platform sender, only to your team's addresses and to people a team member invited in that environment, and keeps every message it sends in its Inbox in the console, with the links and codes picked out.
- **Console:** Changes: compare an environment with production and promote unsubscribe groups, email templates, workflows, plans and plan groups, item by item. A workflow arrives as a draft and a plan as a new draft version, so nothing goes live until you publish it there. Users, records, secrets, keys and webhook endpoints never move.
- **Billing:** Your plan sets how many environments you can have besides production. Environments are never billed: their users, usage and storage do not count toward your plan's quotas or monthly active users. Stripe takes test keys only in an environment.
- **Console:** A go-live checklist: once you build in environments, production's dashboard flags Stripe test keys, sign-in settings that still send people back to localhost, and a missing email sender. Each line links to its setting, and it is advice only.
- **Console:** Each environment's dashboard lists its organization ID, its key and its sign-in client. The client secret is shown only once, and Rotate makes a new one. Reset empties an environment but keeps its key, and Archive retires it. Both ask you to type its name first.

Source: https://www.buildbase.app/changelog/development-and-staging-environments

## Environments get their own allowances, and enterprise SSO too

25 October 2026. Each development or staging environment has its own monthly allowances and is never billed past them. Enterprise single sign-on (SSO), directory sync and company keys, which already work in production, now also work in development and staging environments.

### Added

- **Authentication:** Your team can now try a company's setup in a development or staging environment before changing it in production. Enterprise single sign-on (SSO), directory sync and company keys already work in production. Now they also work inside a development or staging environment, set up against your own WorkOS account.

### Improved

- **Billing:** A development or staging environment never adds overage to your bill. Each one has its own monthly allowances, and usage past an allowance is refused rather than billed. You can see them, read-only, under Limits in this environment.
- **Console:** Inside an environment, you can now see the sign-in apps BuildBase lends it and the platform sender. A Shared sign-in for testing card lists the lent Google and GitHub apps, and can add one back. The Senders page shows the platform sender, whether it is in use or standing by behind the environment's own sender.

Source: https://www.buildbase.app/changelog/environment-allowances-and-enterprise-sso-in-environments

## Admin and app-server API keys, and billing emails that say more

25 October 2026. Each API key is now either an admin key or an app-server key, and billing emails give the amount and the dates that matter. Coupons can be limited to chosen plans, and fixes cover roles, feature flags, campaigns, the audience and the docs.

### Added

- **Billing:** You can now limit a coupon to chosen plans. A plan coupon carries over to later versions of that plan, with the months it has left.
- **Documentation:** A new guide shows how your customers add your app's MCP server to Claude, ChatGPT, Cursor, VS Code and other clients. It also shows how to list the server on the MCP Registry. The docs site, docs.buildbase.app, now serves AGENTS.md, auth.md, an API catalog and the SDK's skill. The console and every hosted sign-in host serve auth.md too.

### Improved

- **API keys:** Behaviour change: when you create an API key, you now choose whether it is an admin key or an app-server key. An app-server key or an app user's token gets 403 ADMIN_SCOPE_REQUIRED from the catalog, coupons, Stripe credentials, organization and storage settings and the blueprint routes. A key made earlier counts as an admin key only if its role is owner or admin.
- **Billing:** Billing emails now tell your customers more. Payment failed emails give the amount, the next retry date and a billing link. The cancellation email names the day access ends. Withdrawing a cancellation or pausing a plan now sends an email. Dates fall on the recipient's own local day. The credits removed email names the refund or dispute behind it.
- **Workspaces:** Behaviour change: updating a workspace's features now tells you when nothing could be changed. If every feature named is one the workspace may not change, the API answers 403 FEATURE_NOT_USER_MANAGED. It used to answer 200 and change nothing. When the request also names features it may change, those are applied and the rest are listed in ignoredFeatures. Route: PATCH /api/v1/public/workspaces/:id/features.
- **Access control:** Behaviour change: a new custom role's name can use only lowercase letters, numbers, hyphens and underscores, up to 64 characters. Anything else answers 400, but roles already saved keep working. A role whose name has a space now opens as that role, instead of a copy with %20 in its name.
- **Console:** The security audit log now shows who changed your pricing. It records who published or archived a plan version or a pricing group version. It also records who changed an add-on offer, a coupon or a promotion code. The Organization audit trail's action filter now filters the list.
- **Console:** After you pay for a new organization, the console now waits for Stripe to confirm the plan. Then it opens that organization or its paywall.

### Fixed

- **Feature flags:** The console and the SDK now agree on whether a flag is on for a user. This holds for flags targeted by user tag, user list or audience, and for archived or disabled flags. Updating a flag through the API keeps any targeting the request does not mention. It also saves the user tags sent with it.
- **Workspaces:** A new person no longer sees No workspace selected on their first load until they reload. Two invitations accepted at a workspace's last seat can no longer both get in past the seat limit. A feature slug the server would rewrite, such as ranked_mode, is now refused with 400 instead of being saved as rankedmode.
- **Billing:** Two organizations that share one Stripe account no longer see each other's Stripe webhook events, coupons or promotion codes.
- **Billing:** A credit pack with no price is no longer offered as Buy at $0.00. Plan credits that do not renew are now granted once per subscription. The revenue page counts recurring add-ons in MRR, your monthly recurring revenue. A workspace's quotas in the console read Unlimited instead of -1.
- **Email:** A sent campaign's report now recounts delivered, opens and clicks within minutes, instead of waiting for the hourly count. Pause and Cancel no longer show on a campaign once its last message is out.
- **Email:** Unsubscribing through a link now fires the email.unsubscribed event and shows on the contact's timeline. Table searches match exactly what you type, so an address with + is found.
- **Audience:** People who sign up with a code now always reach your audience with their tags, attributes and locale. Before, two writes at once could leave the contact without them. An import no longer reads done with no result while it is still finishing.
- **Console:** An organization with no domain can save Settings > General again. Deleting an FAQ now says Deleted, or shows why it was refused. Settings shows your organization's own name instead of Organization.

Source: https://www.buildbase.app/changelog/admin-keys-and-billing-console-fixes

## Clearer API answers and self-hosted installs that stay up

25 October 2026. A badly formed id now answers 400 instead of 500, server errors no longer carry internal text, and the detailed health check needs your internal key. Self-hosted installs start and stay up, and smaller fixes reach the console, workflows and campaigns.

### Improved

- **Platform:** API errors are now clearer and no longer leak internal details. A malformed id in a URL answers 400 with the message Invalid id. Before, it answered a 500 that quoted the database. A server error (status 5xx) no longer carries internal error text, and the generic one has the code server_error.
- **Platform:** A refused plan change now says which change it refused. It also carries a code naming the subscription's state, such as SUBSCRIPTION_PAUSED or SUBSCRIPTION_PAST_DUE.
- **Platform:** Behaviour change: the detailed health check is no longer public. Without your internal API key, /api/health now answers only its status, as /api/health/summary does.
- **Platform:** Behaviour change: by default, API answers are never cached. Every /api answer now defaults to Cache-Control: no-store. The OAuth endpoints answer invalid_request, the standard error for a bad request, when an organization id names no organization. Starting a sign-in while Redis cannot store its state now answers 503, which says to retry, instead of a 500.
- **Billing:** An app with no published plans now gets a clear code from the plan catalog: its 404 carries the code NO_PLANS_AVAILABLE. When a downgrade is scheduled, a workspace's subscription says until when it keeps its current plan, in featurePlanVersionUntil. In the console, a workspace's quota rows are named by their item and show the plan's figure beside the one in effect.
- **Console:** More console controls now have names that screen readers announce. That covers every control on the billing editors, the price tier inputs and a pricing group's reorder and remove buttons. It also covers the refund dialog's Reason field and each table row's checkbox. Every save among these now shows that it is saving.

### Fixed

- **Self-hosting:** Self-hosted installs built from our templates now stay up. The production load balancer starts under its own security settings instead of exiting. Redis is capped well under its container's memory limit, so it is no longer killed and restarted. Health and readiness checks are never rate limited, and the sign-in page's files load without hitting a rate limit and keep their security headers.
- **Self-hosting:** The self-hosted console reads its settings again, instead of showing Installation not configured. Bundled MongoDB no longer crashes over and over after a restart. A server URL on a private address, such as http://localhost:4101, can now complete setup. Rate limits count each visitor, not the whole install as one. The installations list no longer returns installation keys.
- **Workflows:** A workflow built from our docs can now stop when an HTTP step gets a 500. The docs now give the merge tags (placeholders the flow fills in when it runs) that work for an HTTP step's result: {{nodes.<nodeId>.success}} and {{nodes.<nodeId>.statusCode}}. The tags they gave before resolved to nothing. HTTP step logs now name the host only, not the full URL. A Grant credits step that is retried grants its credits once.
- **Email:** A campaign's Send button no longer stays disabled until you reload, because its pre-send review now runs again after every save.
- **Console:** The first click after closing a drawer or dialog is no longer lost. Toasts, the short pop-up messages, now stay on screen. The country pickers spell every country correctly and find one by its name.
- **Console:** The Domains tab now shows when a custom sign-in domain's certificate expires. Four usage meters now count what your plan's limits count: workflow templates, notification events, workspace feature flags and rich content blocks.
- **Console:** A console team member demoted from admin now loses admin rights at once. Before, they kept them for the life of their token, up to seven days.

Source: https://www.buildbase.app/changelog/clearer-api-answers-self-hosting-and-console-fixes

## Website contact page, badge files and a reporting docs fix

25 October 2026. The contact form on buildbase.app is replaced by the support email and chat. Built with BuildBase badges now have one file per theme, and the reporting reference shows filters the API accepts.

### Improved

- **Website:** Removed: the contact form on buildbase.app/contact. The page now offers the support email and the chat instead.
- **Website:** Each Built with BuildBase badge is now its own file, with the theme in the name, such as built-with-dark.svg. An older embed that asks for built-with.svg?theme=dark gets the auto badge, which follows the reader's theme. A size set in the embed is no longer read.

### Fixed

- **Documentation:** The reporting reference now shows filters the API accepts. It sends filter as filter[from] and filter[to], where it showed a JSON string that the API refuses with 400. It also lists the required previous parameter for the counts endpoints.

Source: https://www.buildbase.app/changelog/website-and-docs-changes-late-october

## Two-step sign-in, phone and wallet sign-in, and a sign-in page in eight languages

24 October 2026. Two-step sign-in, new ways in, a sign-in page in eight languages, console setup from one file, an email server API, and fixes to flags, webhooks and workflows.

### Added

- **Authentication:** Two-step sign-in. People add an authenticator app such as Google Authenticator or 1Password, get ten single-use backup codes, and are asked for a 6-digit code after their first step. Set the policy to Off, Optional or Required under Authentication > Security. A device the person chooses to trust skips the code for up to 90 days unless you change the window, a passkey that checked a fingerprint or PIN counts as both steps, and an admin can reset someone's second step from their page in the console. You can also allow a code by text message, through your own SMS provider, beside the app and never instead of it.
- **Authentication:** Email and password works end to end on the hosted page: one form with Forgot password?, a 6-digit reset code, and a reset that also lifts the sign-in lockout. Passwords found in a known breach are refused on sign-up, reset and change, checked against Pwned Passwords with only the first five characters of the password's hash leaving the server.
- **Authentication:** Email sign-in codes. A Magic Link method can send a 6-digit code, a link or both, and a code can create the account too, with the address already verified. A code is the better choice when people read their mail on a phone and sign in on a laptop.
- **Authentication:** Phone sign-in. People sign in or sign up with a 6-digit code by text message, WhatsApp or voice call, sent through your own Twilio account or a signed webhook of yours, so your provider bills you and BuildBase never does. The SMS tab sets a daily cap with an early warning, sends a test, and keeps a 30-day delivery log without the full number or the code.
- **Authentication:** Sign in with Apple and one OpenID Connect or OAuth 2.0 provider of your own, such as Keycloak, beside Google, GitHub, LinkedIn and Microsoft. Google One Tap offers a one-click sign-in to people already signed in to Google. A returning social sign-in now finds its account by the provider's own user ID before the email, so someone who changes their address still reaches the same account.
- **Authentication:** Four more ways in, each off until you add it: usernames beside the email for password sign-in, Ethereum and Solana wallet sign-in by signed message, Continue as guest with an account that keeps its data when the person adds an email, and device code sign-in (RFC 8628) for a CLI or a TV.
- **Authentication:** Bot protection with Cloudflare Turnstile on sign-ups, emailed and texted codes and guests, and on password sign-ins too: every one, or only once an address has failed three times in 15 minutes. On the BuildBase sign-in domain it needs no keys; a custom domain takes your own. A separate switch refuses disposable email addresses at sign-up.
- **Authentication:** Who can sign up: an allowlist and a blocklist of addresses and domains, and a waitlist mode where only the entries you approve on Beta users can create an account. The lists stay private, and a refused address hears the same sentence whichever list refused it.
- **Users:** Import users from Clerk, Auth0, Firebase or Supabase with npx @buildbase/sdk import, or any other system through POST /api/users/import. Each user keeps their email, verified status, name, old id, phone, social sign-ins and password hash, and signs in with the same password, which is moved to bcrypt at that first sign-in.
- **Users:** Sign in as a user from their page in the console, to see the app as they do: read-only unless an owner turns that off, for 5 to 60 minutes, with the start written to the security audit log. Your app needs @buildbase/sdk 0.0.90 or later to open the session; on an older SDK it opens signed out. Custom claims, set per user from the console or the API, reach your backend at sign-in and in every agent token.
- **Authentication:** The routes behind account self-service, for your own screens: change an email with a code, change a password, connect and remove social sign-ins and wallets without removing someone's last way in, add a phone, delete the account after a grace period you set, and Confirm it's you, which re-checks a sign-in older than 10 minutes on the hosted page without signing anyone out.
- **Sign-in page:** The hosted sign-in page in eight languages, with a language switcher, and each app's own name, logo, dark logo, favicon and brand colour. Layouts include a split screen and pattern backgrounds, fonts include twelve families served by BuildBase or your own file, and every sentence you can write is in one editor, per app and per language, with nothing machine translated. Sign-in emails name the app and can show its logo.
- **Webhooks:** Sixteen new events: user.mfa_enrolled, user.mfa_disabled, user.mfa_reset_by_admin, user.email_changed, user.imported, user.account_linked, user.account_unlinked, user.phone_added, user.phone_verified, user.phone_removed, user.deletion_scheduled, user.deletion_cancelled, user.deleted, auth.login_failed, auth.signup_challenged and auth.sms_budget_exceeded.
- **Email:** Send transactional email and manage subscribers from your backend, through a server API at /api/v1/server that takes an org API key and nothing else. One call sends a message from a template or your own subject and body, with an Idempotency-Key header so a retry never sends twice, and another reads its status. The subscriber calls add or update, tag, unsubscribe, resubscribe and delete contacts by email address. Every send passes the same sender, quota and suppression checks as the console. The SDK's createServerClient gets emails and subscribers calls for it from @buildbase/sdk 1.0.0.
- **Audience:** CSV imports carry a list's history across from another tool. Map a status column and unsubscribed people stay unsubscribed, bounced addresses go on your suppression list, spam complaints are kept off your mail for good, and pending contacts get no campaign until they confirm. A status the import does not recognise skips the row and is reported, never read as subscribed. A tags column tags each row, Add everyone to a list puts the whole file on one list, and the result counts each status.
- **Email:** A public newsletter archive, off until you turn it on. A public unsubscribe group gets an address and a page listing the campaigns you published to the web, newest first, with a page per issue, an RSS feed and a subscribe box that asks people to confirm by email. Drafts never appear, a withdrawn issue disappears within a minute, search engines stay out unless you let them in, and older web version links keep working.
- **Email:** Gmail Postmaster Tools on each sending domain: Gmail's own spam rate, domain reputation and SPF, DKIM and DMARC results, read daily and shown on the domain and beside the Gmail row of a campaign report, with a warning when the spam rate passes 0.10%. Connecting waits on Google's review of BuildBase's access, so it opens to workspaces once Google approves it.
- **Console:** Two-step sign-in and sessions for your console login. After Google, the console can ask for a code from an authenticator app, with ten single-use backup codes. The new Security page lists every browser signed in to your account and ends one or all the others, and an owner or admin can require two-step sign-in for the whole organization: a member without it is sent to set it up, not signed out.
- **Console:** Set up an organization from one file. A blueprint, buildbase.blueprint.json, describes your console setup: app settings, workspaces, sign-in, email, billing, roles and API keys, webhooks, integrations, data and workflows. BuildBase checks the file, plans it against your organization and lists every change before it makes any, applies only the plan you reviewed, then compares again to confirm, and can export your current setup as a file. Secrets stay out of the file, and nothing is deleted unless both the file and you allow it. It is in the console under Get started > Set up from one file, and in the API at /api/blueprint, where planning, applying and exporting take the owner or an admin. The npx @buildbase/sdk blueprint command comes with @buildbase/sdk 1.0.0.

### Improved

- **Console:** Behaviour change: in an organization that requires two-step sign-in, a console sign-in that did not use the authenticator app, such as one made before the person set the app up, is now signed out when it opens that organization. Switching in answers 401 with the code SESSION_ENDED, and the next sign-in asks for a code. Setting the app up during a sign-in counts for that sign-in, and a member with no app is still sent to set one up, not signed out.
- **Users:** Behaviour change: blocking or unblocking someone, resetting their two-step sign-in, signing them out of a session or a device, setting their custom claims and signing in to the app as them now take an owner or admin when that person is an owner or admin, and the owner when it is the owner. A role with only the users permission is refused with 403. The owner cannot be blocked (403: transfer ownership first), and blocking the last unblocked owner or admin answers 409.
- **Billing:** Behaviour change: choosing a free plan with select-free-plan, for a workspace or for a person, now answers 400 with Plan version not found on planVersionId when no published pricing group of your app offers that free version, as a checkout does. Moving from one free version to another inside a running period keeps that period and its quota usage. Plan credits from the free version you leave end on the move, while credits from purchases, admin and workflow grants and dispute refunds stay, and the new version's credits are granted once for the period, instead of a fresh month of credits on every switch.
- **Email:** Email goes out through your own provider only. BuildBase no longer sends an organization's mail with its own Mailgun or Amazon SES account: every organization connects its own provider, and the Domains tab has a Bounce reports row to add or replace your Mailgun webhook signing key, without which bounce reports are turned away.
- **Console:** Every Authentication screen explains itself: a ? beside each setting opens a short note in plain words, each method says where to get its provider's keys, and changes that would lock people out ask first and say what they do.
- **Authentication:** A refused sign-in carries a reason a page can translate: invalid_credentials for a wrong password or an unknown address alike, locked during the 15-minute lockout, which a password reset now lifts, and blocked, said only after the right password so an address alone reveals nothing.

### Fixed

- **Authentication:** A password containing <, > or & is hashed exactly as typed. The request sanitiser used to change those characters first; a password stored that way still signs in and is re-hashed as typed at that sign-in.
- **Authentication:** A magic link opened in a browser that did not ask for it, such as a phone's mail app, now says to open it where it was asked for and stays usable there, instead of being spent.
- **Console:** Custom sign-in domains are no longer all marked as insecure on the Domains tab, and link over https.
- **Feature flags:** A user feature flag targeted at user tags now turns on for users with those tags, and "Allow all users" turns it on for everyone. Both settings were saved in the console, but what the SDK read ignored them. A workspace flag set to "Allowed to all" is now on for every workspace, as the console's "Enabled for all users" badge already said, including workspaces whose plan leaves it off. An archived user flag now turns off for everyone it still targeted.
- **Workflows:** A workflow's later steps no longer run before their delay is up. A recovery sweep could start every remaining step of a running drip about 40 minutes in, including both branches of a wait-for-an-event and the steps after a failed one. Recovery now resumes only the step a run has reached, with the rest of its delay.
- **Workflows:** A step that fails by throwing, such as an HTTP request that times out or cannot connect, is now retried under its node's retry policy. When its last attempt fails, the step's error path runs or, without one, the run fails, sends workflow.instance_failed and frees its place in the concurrency limit. Before, the first failure ended the step with no retry and left the run marked running. An HTTP step that gets an answer, whatever its status, still completes with success set to whether it was 2xx.
- **Webhooks:** A webhook endpoint is now switched off only after an outage of at least an hour: 50 failed deliveries in a row, each one counted only after all its retries, the first of them at least an hour old. It used to be 50 failed attempts, so a two-minute outage at your end turned it off; a short outage no longer does, however busy the endpoint. Every event an endpoint we switched off does not send now appears in its delivery log as Skipped, and the organization's owner and admins are emailed when we switch one off.
- **Documentation:** The webhooks documentation now describes delivery as best effort: five attempts over about two and a half minutes, one signature timestamp per event, no resend, and the cases in which an event is lost. It used to promise at-least-once delivery.
- **Security:** Someone removed from an organization can no longer get back into its billing workspace with a sign-in from before their removal. Central's internal API now checks a request's signature against the bytes that were sent, so a webhook endpoint name made only of digits no longer gets its disable notice refused.
- **Platform:** A full Redis no longer makes every API request fail: rate limits let requests through while their store cannot be written, and a member's permission check no longer fails when its cache cannot be updated.
- **Self-hosting:** Self-hosted Redis now starts again after a restart; before, a reboot left the server without it. The images move off Alpine 3.21, which reaches end of life on 1 November, and the database restore script now restores the backup it is given and asks before it overwrites anything.
- **Workflows:** A step that is retried no longer sends its email or push a second time. An HTTP step's POST, PUT, PATCH or DELETE carries an Idempotency-Key header, the same on every retry of that step in that run, so your endpoint can ignore a repeat; a key you set in the step's headers is sent instead.
- **Workflows:** Resuming after the emergency stop turns back on only the workflows the stop paused, and a workflow you paused yourself stays paused. The stop and the resume now appear in each workflow's audit log. Deleting a workflow cancels its runs that are still going, and a paused run keeps its wait for an event so it can still be woken when it resumes.
- **Webhooks:** Every webhook event carries an id, in the body and the x-buildbase-event-id header, the same on every retry, so a receiver can skip one it has already handled. The delivery Logs sheet now pages through older attempts and offers Try again when they cannot be loaded.
- **Billing:** A Stripe checkout delivered twice no longer resets the period's plan credits. The plan screen offers Manage billing when a payment needs attention, and says so with Try again when billing cannot be opened, instead of waiting for ever.
- **Security:** Activity rows, attribute history, email opens and link clicks keep only a short list of request headers, such as the browser and language, and never a session id, token or cookie; a migration cleans the rows already stored. Live workflow updates in the console reach only members whose role can read workflow runs.
- **Platform:** Every API response carries an X-Request-Id, and a console error caused by our side shows it as a Reference to quote to support. Browsers keep the API's CORS check for two hours instead of five seconds, which saves a round trip on most requests. An id or code made only of digits, or one starting with 0 or +, now reaches the API exactly as sent instead of being turned into a number.
- **Platform:** Queued emails no longer keep a copy of their content in the job queue, failed background jobs are kept up to a fixed number, and very large API answers are no longer cached, so one busy organization cannot fill the shared queue store.
- **Documentation:** The Next.js quickstart works as written: it leads with npx @buildbase/sdk init, and shows every file to create by hand, the client provider, the sign-in routes and the callback page included.
- **Platform:** If Redis stops, the API keeps answering instead of hanging. A request that needs a cached value reads it from the database after at most two seconds, and at once after Redis has been gone that long; the health check reports degraded straight away.
- **Webhooks:** A webhook retry now sends exactly the body and signature of the first attempt, instead of looking up the person or workspace it names again, so one event id never arrives with two different bodies.
- **Authentication:** A custom sign-in domain is marked verified only once it can serve sign-in: Vercel has confirmed you own it, its DNS points at Vercel and the sign-in page answers over HTTPS. Until then sign-in stays on the BuildBase domain, and the Domains tab says which check is failing. A verified domain that stops serving goes back to the BuildBase domain after about an hour of failed checks.
- **Sign-in page:** Opened inside the built-in browser of Instagram, Facebook, TikTok, LinkedIn, X or another app, the hosted sign-in page says how to open it in the phone's own browser, with a link to copy that keeps the sign-in going (and an Open in browser button on Android), and hides Google sign-in and passkeys, which those browsers refuse.
- **Email:** Adding a sending domain no longer shows an error when the domain was in fact created, and the domain is now registered to your organization, so no other organization can add it.
- **Sign-in page:** The hosted sign-in page shows a spinner while it loads instead of a blank page.
- **Sign-in page:** Pressing Back after leaving for a sign-in provider such as Google or GitHub no longer leaves the sign-in page stuck with every button turned off: the page says that sign-in did not finish, and you can choose a way in again.
- **Sign-in page:** An app with no sign-in methods says so on its sign-in and sign-up pages instead of offering Create account, and with public sign-up off, Create account no longer appears for a moment while the page loads.
- **Sign-in page:** The Japanese Create account link wraps instead of being cut off, and a password refused because it appears in a known data breach is now explained in the page's own language instead of in English.
- **Console:** The Audit tab under Authentication names each change to sign-in security, sign-up, SMS and bot protection settings, lists every setting that changed with its old and new value, and names methods and clients instead of showing ids. A save that changes nothing adds no row, and a secret is shown as changed, never its value.
- **Authentication:** A new sign-in method that cannot be told apart from one you already have, with the same kind, title and delivery or networks, is refused, and a Microsoft tenant that is not common, organizations, consumers, a tenant ID or a domain is refused when you save it.
- **Console:** Pressing Enter in an auth client's settings no longer removes one of its redirect URLs, and Update takes you to the first field that needs fixing instead of doing nothing.
- **Documentation:** The setup guides for Apple, GitHub, Google, LinkedIn, Microsoft and your own OpenID Connect provider, and the guide to importing users, show the API URL correctly. It was printed with stray characters and linked to an address that did not work.

Source: https://www.buildbase.app/changelog/two-step-sign-in-and-new-ways-in

## A whole office can sign in at once, plus security fixes

24 October 2026. Many people sharing one office IP address can now sign in at the same time, and sign-in codes still go out after the day's email allowance is spent. Security fixes cover agent consent, Slack notices, CSV exports and blocked people's keys.

### Improved

- **Authentication:** Many people sharing one office IP address can now open your app and sign in at the same moment. SDK calls are now counted per person. The session code exchange and the hosted sign-in steps allow 300 requests a minute per IP address, up from 30. Only failed passwords count toward the sign-in limit.

### Fixed

- **Email:** Sign-in and verification emails keep going out after your organization's daily email allowance is spent. Sign-in and verification codes, magic links and reset codes used to be dropped at that point. Now they have their own allowance, ten times larger. If that runs out too, a resend says the email could not be sent, instead of saying it was.
- **Sign-in page:** Someone with an unverified email address now gets a code when sign-in sends them to Enter the 6-digit code. Before, the page said a code was sent when none was.
- **Sign-in page:** An app with no brand colour shows BuildBase orange on its sign-in page again, instead of near-black.
- **Authentication:** The older passkey route can no longer delete someone's only way to sign in. It answers 409 last_sign_in_method instead, as the SDK's route does. Route: DELETE /api/v1/auth/passkey/:id.
- **Authentication:** An outdated sign-in can no longer be used to connect an AI agent. A sign-in token issued before a password change or reset, a block or a role change is now refused on the consent screen. The consent and device pages then say the sign-in has ended, in the page's language.
- **Security:** Console sign-in with Google is now tied to the browser that started it. Disconnecting an agent also ends a token refresh it had already started.
- **Security:** Names in Slack notices are now shown as plain text, so a name like <!channel> no longer pings the channel. Values merged into emails also stay plain text. A notification your app sends can now link only to your own app.
- **Security:** A member demoted in your console team no longer keeps admin rights on your organization's BuildBase billing, and a promoted member now gets them. Blocking someone stops the API keys they created at once, instead of up to five minutes later.
- **Security:** A CSV exported from the console no longer turns a cell that starts with =, +, - or @ into a spreadsheet formula. This covers table exports, the audience export, a company's audit trail, Google Ads conversion files and the unsubscribe group list.
- **Security:** Behaviour change: a workspace's invoices and subscription card now need permission to read subscriptions, not only workspaces.

Source: https://www.buildbase.app/changelog/sign-in-for-a-whole-office-and-security-fixes

## Billing that charges once, in the right currency

24 October 2026. Billing requests take a key so a retry charges only once, and checkouts use the customer's currency. Plans published before Stripe was connected can be bought, failed plan credit grants are retried, and a scheduled downgrade keeps what was paid for until it takes effect.

### Added

- **Billing:** A retried billing request no longer charges twice. You can send an optional Idempotency-Key header with a checkout, plan change, add-on or credit pack purchase, cancel, resume, pause, coupon or billing portal call. A retry with the same key reaches Stripe only once. Keys are scoped to your organization and the caller, and the console sends one per click. Reusing a key for a different request answers 409 IDEMPOTENCY_KEY_REUSED.

### Improved

- **Billing:** Behaviour change: a price made for one customer's deal can no longer be bought by someone who learns its id. Checkout from your app now accepts only a plan version that a pricing group sells or has sold, in a group that is not archived. Any other id answers Plan version not found. The console's checkout link still sends any published version.
- **Billing:** You can now test usage resets, credit expiry and plan change previews with Stripe test clocks. With Stripe test keys, they follow a subscription's Stripe test clock, which is Stripe's simulated time for tests.

### Fixed

- **Billing:** A retried usage call can no longer bill your customer's overage twice. Two usage reports sent at the same time with the same idempotency key, which marks them as one report, now count once. Before, both could move the counter.
- **Billing:** Plans and credit packs published before you connected Stripe can now be bought. Their missing prices are created by saving your Stripe keys, by the new Sync with Stripe button on Subscriptions > Plans, or by a checkout. Stripe Checkout shows the plan's name without its version. A checkout made while prices are still being created answers 409 STRIPE_CATALOG_SYNCING.
- **Billing:** Checkouts now charge in the right currency when none is named. A plan checkout or plan change with no currency uses the customer's billed currency. Failing that, it uses the first of your billing currencies the plan is priced in. It never simply takes the plan's first listed price, which sent some USD visitors to a EUR checkout. A plan priced in none of them answers 400 PLAN_CURRENCY_UNAVAILABLE.
- **Billing:** More billing calls now say plainly when Stripe is not connected. In an organization that has not connected Stripe, add-on purchases, plan change previews and the coupon routes also answer 409 STRIPE_NOT_CONNECTED. Before, a recurring add-on purchase answered 500. Plan & Billing in such an app shows no invoices, instead of an error about missing Stripe credentials.
- **Credits:** Customers no longer go without plan credits when a grant fails. Plan credits that fail to be granted are now stored and retried automatically. That covers checkout, an upgrade, the monthly reset, a downgrade and a move to a free plan. The new credit.plan_grant_failed webhook and Slack notice say whether a grant is retrying, resolved or needs a person.
- **Billing:** A scheduled downgrade no longer takes away what the workspace paid for straight away. The workspace keeps its quotas and monthly credits until the downgrade takes effect. Before, they dropped at once. A plan change now ends only plan credits set to reset, not those set to top up.
- **Billing:** A trial started without a card now sends the trial expired email when it runs out. It sends the subscription.trial_expired event, where it used to send subscription.canceled and no email.

Source: https://www.buildbase.app/changelog/billing-that-charges-once

## Sign-in fixes, notification links that open your app, new limits

24 October 2026. Bot protection and disposable-address settings now sit in one place, and Sign in with Apple uses Apple's own button. Notification and billing links open your app, and new limits cover consent records, logout and monday.com.

### Improved

- **Authentication:** Removed: the Sign-up tab's own switches for disposable addresses and a sign-up captcha. Each is now a single setting on the Security tab, under Disposable email addresses and Bot protection. The disposable list covers eight more services. Where Turnstile, Cloudflare's bot check, cannot serve the page, sign-up asks for the forms captcha instead, never both. That happens on a custom domain without keys or a self-hosted install, for example.
- **Feature flags:** Behaviour change: adding targets to a flag through the API now needs a plan with advanced flag targeting. That covers adding users, user tags, user lists or audience lists, as the flag's own PATCH already required. Removing targets stays open on every plan, and the console shows the plan lock. Route: PATCH /features/:id/{users,tags,user-lists,audience-lists}/add.
- **Authentication:** Social sign-in and Google One Tap now require a PKCE challenge when they start. PKCE is a one-time secret that ties the end of a sign-in to the app that started it.
- **Authentication:** Guest upgrade and email change codes now count toward the daily code allowance, and answer not_sent once it is spent. Two identical sign-in method saves at the same moment now create one method, and the other save answers 409 method_write_busy.
- **Authentication:** Responses no longer send X-Powered-By, a header that revealed what the server runs on. When the token endpoint refuses an app's credentials with 401 invalid_client, it now sends WWW-Authenticate, the header that says how to authenticate.
- **Platform:** Consent records now have a daily cap of 500,000 per organization. Past that, the route answers 429 (too many requests) and the organization.public_write_limit_reached event fires. Logout is now limited to 60 a minute per IP address, and monday.com action reports to 600 a minute.
- **SDK:** From @buildbase/sdk 1.0.0, a platform outage no longer signs people out. The session is kept, and isSessionUnverified is true while the SDK retries. A sign-in callback whose state does not match is refused with OAUTH_STATE_INVALID. The state is the value that ties a callback to the sign-in that started it.

### Fixed

- **Sign-in page:** On the consent screen, Allow and Deny now wait until the page knows which app is asking. A guest is never asked Trust this device?
- **Sign-in page:** Sign in with Apple now uses Apple's own Continue with Apple button, on its own row. Email, username, password, phone and code fields now read left to right in Arabic.
- **Authentication:** A device signing in no longer has to start again when the app server fails to issue its token. When it retries, it now gets the token instead of expired_token.
- **Notifications:** A notification link with a path such as /billing now opens your app, not the platform's tracking host. That holds for the email link and the push click. Billing notices link to an https address of your own app, never a localhost or private address. An app with two addresses no longer gets an empty link.
- **Email:** The trial conversion email now names the plan instead of Version 1. The trial started email no longer reads The your plan trial.
- **Self-hosting:** An unknown address on a self-hosted sign-in page now shows the not-found page, with a 404. An installation can no longer register a public suffix such as co.uk or github.io as a domain. A public suffix is a shared ending that many unrelated sites sit under.
- **Documentation:** A staging host on plain http now keeps its session when it follows the quickstart. The quickstart's token route now sets the cookie's Secure flag from the request's protocol. That flag sends a cookie over https only. The route also passes on the platform's reason and status, instead of a bare 401.

Source: https://www.buildbase.app/changelog/sign-in-notifications-and-rate-limits

## Billing charges, emails and screens that say what really happened

23 October 2026. An end-to-end pass over billing found plan changes that charged the wrong amount, emails that misdescribed a trial or a lost plan, and screens that hid what a plan includes. They are fixed, and one usage response changes status.

### Improved

- **Billing:** Behaviour change: a usage report refused because a hard-capped quota is used up now answers 402 with the code QUOTA_EXHAUSTED, the quota slug and when it resets, instead of 400. A bad request still answers 400 and the rate limiter 429. Code that checked for 400 to detect a used-up quota should check for 402 or the code; the SDK error carries all three fields from @buildbase/sdk 1.0.0.
- **Workspaces:** Behaviour change: a workspace name created or renamed through the API is stored as typed, so GET /workspaces and the workspace webhooks now return Zoe & Son's <Lab> instead of an HTML-escaped Zoe &amp; Son's. Escape the name wherever you put it into HTML, Markdown or a chat message; React does it for you.
- **Billing:** Behaviour change: buying a credit pack or an add-on in a currency other than the one the workspace or person is already billed in now answers 400 with the code SUBSCRIPTION_CURRENCY_MISMATCH, as a plan checkout does, instead of charging in the billed currency anyway. A purchase that names no currency is unchanged and is charged in the billed currency.
- **Billing:** Behaviour change: a workspace's or person's billing currency is now set when a checkout is paid, not when it is opened. A Checkout that is opened and left unpaid no longer ties the customer to its currency, so they can still buy in the currency they chose. Opening a checkout in one currency closes that customer's open checkouts in another.
- **Billing:** Behaviour change: in an organization that has not connected Stripe, a plan checkout (a workspace's or a person's own) and a credit pack purchase now answer 409 with the code STRIPE_NOT_CONNECTED and the message "Payments are not set up for this app yet", instead of a 400 about a missing price or missing Stripe credentials. Publishing an add-on offer in the console says to connect Stripe first. Code that read the 400 should check for 409 or the code.
- **Billing:** Billing emails say what happened and what it cost: a trial start gives the trial end and the first charge, a payment receipt gives the amount, plan, period and invoice link, refunds and add-on purchases give their amounts, and a plan lost for non-payment says so with the open invoice, instead of announcing the Free plan as good news.
- **Console:** Pricing groups can be archived and restored from their row, and Allowed to all can no longer be turned on for a subscription-managed feature by accident, because it gives the feature to every workspace on every plan.

### Fixed

- **Billing:** A customer who downgraded and then changed their plan again in the same period was credited at the cheaper plan instead of the one they paid for. The unused time of the plan they paid for is now credited.
- **Billing:** An upgrade left waiting on a declined card no longer bills the usage before the change twice: the carried usage is held back until the upgrade is paid, and dropped if it never is.
- **Billing:** A dispute that arrives before its credit pack purchase is recorded is retried until it can take the credits back, a trial ended early no longer sends a trial ending soon email, and a plan's monthly credits are granted when a scheduled downgrade onto it takes effect.
- **Billing:** A refund made before its credit pack purchase is recorded now takes the credits back as soon as the pack is granted, instead of leaving them with the buyer.
- **Billing:** A credit pack priced in only some of your organization's billing currencies can be bought by a workspace that has not paid for anything yet. It is sold in the first of your currencies the pack has a price in, where before only your first currency was tried and the purchase was refused.
- **Authentication:** Someone who signs up through an invitation link goes straight in. The link already proves the address, so no code is sent, but the sign-up page still asked for one and the only way on was back to sign in.
- **Agents:** A blueprint exported from a billing setup with graduated seat or overage prices now plans back with no changes, and one default pricing group is allowed for workspaces and another for people.
- **Documentation:** Billing code samples format money with the currency's own decimals, so a yen price is no longer shown a hundred times too small, and pages that use SDK features newer than the published release say so.

Source: https://www.buildbase.app/changelog/billing-fixes-from-the-release-qa-pass

## Seat rules, spend caps per project and an Installations page

23 October 2026. Plans gain seat rules, a workspace can cap each project's share of its spend, and self-hosted owners see their installations in one place.

### Added

- **Billing:** Seat rules on a plan: which roles take a seat, whether pending invitations or blocked members count, a minimum, seats sold in blocks, and one seat per person across everything one payer pays for.
- **Billing:** A workspace can cap each project's share of a quota's spend.
- **Self-hosting:** The Installations page shows how many installations you are allowed, how many you have, and how many organizations each may hold. Detached organizations can be reattached from the same page. When you make a new installation API key, the old one keeps working for up to 60 minutes.

### Improved

- **Billing:** With the fall-back switch on, a workspace whose paid plan ends moves to your Free plan. And a plan's coupon keeps applying when a subscriber moves to a newer version of that plan.

Source: https://www.buildbase.app/changelog/seat-rules-project-spend-caps-and-installations

## Refresh tokens a copied database can't use, and sign-ins tied to one browser

23 October 2026. A copy of your database holds no refresh token that works. Every token has one job, and Continue with SSO now finishes only in the browser that started it.

### Added

- **Security:** Refresh tokens, which keep people signed in, are stored only as a one-way hash, so a copy of the database holds none that work. Refresh tokens your app's users already held are cancelled once, right after this release is deployed, so each of them signs in to your app one more time. AI agents' access is untouched.
- **Security:** Every token BuildBase signs says what it is for and which part of the platform it opens, and each part accepts only its own kind. A sign-in token from your hosted page is refused by the console, for example, and a magic link's token works for that link and nothing else.
- **Security:** Sign-in gives nothing away about who has an account. Ten wrong passwords lock any address, username or phone number, with the same answer whether or not an account exists. And a sign-in for an unknown address takes as long as a wrong password.

### Improved

- **Authentication:** Behaviour change: Continue with SSO now finishes only in the browser that started it, as social sign-in and Google One Tap already do. The hosted sign-in page already handles this. A sign-in screen of your own must send a PKCE challenge when it starts, and the matching verifier when it redeems the code, as the docs on sessions and tokens show.

Source: https://www.buildbase.app/changelog/hashed-refresh-tokens-typed-tokens-and-pkce

## Workflow and console fixes, and billing answers that say more

23 October 2026. Workflow steps and runs now say what happened, and console pages keep their place and fit on phones. Archiving is now called archiving, and billing answers gain hasPaymentMethod and clearer refusals.

### Added

- **Billing:** You can now see whether a subscriber has a payment method on file. Reading a workspace's or a person's subscription returns hasPaymentMethod, based on what BuildBase already stores. It is left out when it is unknown.
- **Console:** An organization on a trial can now pay and end the trial from its Plan & Billing page. The Pay now and end trial option first shows today's charge and the next invoice.

### Improved

- **Console:** The plan version editor's price hints no longer assume dollars, and show a yen example. The pricing group preview's Require card row reads Required or Not required.
- **Console:** The workspace features page warns when features override every plan. The revenue page opens on the currency with the most active, past-due or trialing subscriptions.
- **Billing:** Selecting a free plan with an unknown or unoffered version is refused with the code PLAN_VERSION_NOT_FOUND.
- **Console:** Removing a draft plan version or pricing group version is now called Archive, because the draft was always kept as archived. The button, the confirmation and the message all say Archive. The versions list hides archived drafts until you filter for them.

### Fixed

- **Workflows:** A Wait for event step placed right after a contact trigger, such as Audience Member Created, now offers that contact's events, matched to the same contact.
- **Workflows:** On a workflow's page, Test, Pause and Resume now show the server's reason when they fail. An accepted Retry says Retry started, and the builder's Audit log panel names every action.
- **Console:** Reloading the plan screen no longer retries the organization switch. A reload keeps a dedicated, self-hosted or cell organization on its own server. The organization picker no longer opens over the page when the console first loads.
- **Console:** Creating your first organization now says Opening <name>. A failed organization switch names the organization instead of showing Network Error.
- **Console:** A dismissed setup welcome now stays closed for the browser session. More Save and create buttons show that they are working, and the new template dialog shows the server's refusal. The clients table names an OAuth 2.0 client's type instead of App.
- **Console:** Several console pages now fit phones and laptops. A workflow run's header wraps, and the webhooks Status column is no longer covered at 1280px. The revenue By month table scrolls, the product dialog fits a 360px screen and the user page's locale pickers wrap.
- **Billing:** Deleting a pricing group through the API no longer reports a failure after it worked. DELETE /api/subscriptions/groups/:id now answers 200 with the archived group. Before, it archived the group and then answered 500.
- **Billing:** Recording usage from the console no longer claims success for a quantity under 1. The console usage route now refuses it, instead of saying Usage recorded successfully and recording nothing.

Source: https://www.buildbase.app/changelog/workflow-and-console-fixes-from-the-release-pass

## Billing for people and workspaces, add-ons, Stripe Tax, and magic links bound to one browser

22 October 2026. Plans for people and workspaces, add-ons, Stripe Tax and tiered prices; magic links bound to one browser; Markdown for agents and Standard Webhooks headers.

### Added

- **Billing:** Plans for people as well as workspaces. A pricing group can sell to a person, who pays on their own card and their own Stripe customer for what is theirs, such as their API keys or the agents they connect, while a workspace plan goes on covering the workspace. Every check says whose plan it reads, and neither plan lifts the other.
- **Billing:** Someone else can pay for a workspace: a person, or another workspace they manage billing for, pays on their own Stripe customer, so one card covers every project while each workspace keeps its own plan. A workspace plan can also give its owner or every member something on their own account, which is how a family or group plan works.
- **Billing:** Add-ons on top of a plan, in four shapes: a one-time unlock that lasts a set number of days, a lifetime unlock, a consumable pack of units that counts down as it is used, and recurring units billed with the plan. Your gates read them through the same entitlement check as the plan, and you refund a purchase from the console.
- **Billing:** Behaviour change: a trial is offered once per person by default, where it was once per workspace: someone who has had one, in any workspace, is not offered another, and both the workspace owner and the person checking out count. A plan version can choose once per person per plan, or once per workspace, instead.
- **Billing:** Promotion codes. Make coupons and codes under Billing > Subscriptions > Coupons, and customers use them from a link with ?promo=, in the plan picker, on a plan change or on a credit pack, with the code checked before anyone pays.
- **Billing:** Tax through Stripe Tax, on your own Stripe account and switched on under Billing > Credentials. Checkout asks for a billing address and takes a business's tax ID, and invoices and the payment.succeeded event carry the subtotal, discount and tax.
- **Billing:** Graduated and volume tiers for overage and seat prices, and overage reported to Stripe through Billing Meters.
- **Credits:** Reserve credits before a job runs and settle at what it actually cost, so a long agent run never finds the balance gone halfway through. A workspace can top up on its saved card when its balance falls under a threshold you set, and a person can hold credits of their own.
- **Billing:** Checkout can open inside your app instead of on Stripe's page, a customer sees what a plan change will cost before confirming it, and cancelling asks for a reason and can offer a coupon or a pause first. Customers can pause a subscription themselves when you allow it. The screens for these are in @buildbase/sdk 1.0.0.
- **Billing:** A notice before a card expires: when the card a subscription is charged on expires within 30 days, the workspace owner gets an email and a push, and you get the payment.card_expiring webhook.
- **Webhooks:** New events: payment.stripe_events_failed when Stripe events still fail after the hourly retry, subscription.stripe_out_of_sync when the daily check finds subscriptions it cannot match with Stripe, and payer.subject_added and payer.subject_removed when someone starts or stops paying for a workspace.
- **SDK:** useEntitlement, useLimit and WhenEntitled answer for a workspace or for the signed-in person's own plan (from @buildbase/sdk 1.0.0).
- **Website:** Every post and changelog page on buildbase.app has a Markdown twin: add .md to the URL. /llms-full.txt holds every published post and the changelog in one file, beside /llms.txt.
- **Website:** Files for AI agents on buildbase.app: /AGENTS.md says what the site is and where to look, /auth.md which credential to use, /feedback.md where to report a problem, and /.well-known/api-catalog lists our APIs in the RFC 9727 format.
- **Webhooks:** Every delivery also carries the Standard Webhooks headers, webhook-id, webhook-timestamp and webhook-signature, so a receiver can verify it with any Standard Webhooks library. The x-buildbase headers you verify today are unchanged.
- **Console:** Sign a terminal in to the console with a device code: npx @buildbase/sdk login prints a short code, you approve it on the console's device page while signed in, and the token is saved on that machine. The command comes with @buildbase/sdk 1.0.0.
- **Agents:** MCP servers built with the SDK speak protocol 2026-07-28 beside 2025-11-25, publish a server card (SEP-2127) and an AI Catalog, and let each client narrow the tools with ?toolsets=, ?readonly= and ?omit_tools=. npx @buildbase/sdk agent doctor checks a server the way AI clients connect to it, agent install makes install links for each client, and agent listing drafts a directory listing (from @buildbase/sdk 1.0.0).

### Improved

- **Authentication:** A magic link opened in a browser other than the one that asked for it cannot sign in. This is on for every organization, new and existing; if your users ask for a link on one device and open the email on another, turn off Require the same browser in the magic link method's settings, or send a 6-digit code instead.
- **Tracking:** The bb_attr attribution cookie waits for marketing consent: nothing is written before the visitor agrees, and refusing deletes it. An app that captures attribution without the tracking provider uses setAttributionConsent and getAttributionConsent (from @buildbase/sdk 1.0.0).
- **Authentication:** A refresh token given to an Application (first-party) client now carries a 180-day lifetime from when it was issued, after which it is refused with 400 invalid_grant and the person signs in again; refreshing does not extend it. For this release, older tokens issued without a lifetime, or signed with a secret since replaced, are still accepted and logged so you can be told first. Agent clients are unchanged.
- **Agents:** The consent screen and the device approval page list everything an agent gets: that it acts as the person, which of their details your app sees, how long it stays connected and any permission it asked for by name.
- **Console:** Deleting a user refuses the organization owner, an owner or admin deleted by someone who is neither, the last owner or admin, and your own account, each with its reason.

### Fixed

- **Billing:** A refund or a dispute is recorded once, even when Stripe sends its event again or a second partial refund follows, and a dispute you win gives back the credits or the unlock it took, without anyone restoring it by hand. Add charge.dispute.closed to your Stripe webhook endpoint for this.
- **Console:** Invitations to your console team: accepts sent at the same time add one membership, a revoke or reject racing an accept leaves nobody in, and removing someone removes every membership they had. After an ownership transfer, the outgoing owner loses owner-only access at once instead of keeping it until their token expired.
- **Billing:** The Plan Canceled email goes out when a cancellation is scheduled, while its words are true, instead of after access has ended. Billing emails about a person's own plan no longer call it a workspace, and a $0 invoice no longer sends a Payment received email.
- **Billing:** Prices in currencies without two decimals show and save correctly: in the console's plan and credit pack editors and lists, the pricing group preview, the overage note on the pricing page and the affiliate calculator. A yen price of 5000 reads ¥5,000, not ¥50.00, and three-decimal currencies such as the Kuwaiti dinar show three.
- **Billing:** A workspace whose trial ended, or whose payment lapsed or is paused, reads 0 available on every quota in the SDK, the API and the MCP tools, matching what it can use; before, some reads still showed the plan's allowance.

Source: https://www.buildbase.app/changelog/billing-for-people-and-workspaces

## Campaigns that check themselves before they go, and a two-level sending suspension

22 October 2026. Every campaign is checked before it goes, from the console or the API. A sending suspension can stop bulk mail while sign-in mail keeps going.

### Added

- **Email:** Campaigns check themselves before they go, from the console and the API. A campaign with no subject, no content, no unsubscribe link, no postal address or no working sender is stopped, and so is one whose email is over 100 KB. A long subject or missing preview text is flagged as advice.
- **Email:** A sending suspension has two levels. Bulk stops campaigns, workflow mail, the email API and push, while sign-in codes, magic links, resets and invitations keep going. All stops everything.

Source: https://www.buildbase.app/changelog/campaign-safety-checks-and-deliverability

## Groups inside groups, and managers who keep a team's group current

20 October 2026. A company you sell to can now put its groups inside one another, so Engineering is Backend plus Frontend, and name managers who add and remove a group's people without holding a company role.

### Added

- **Authentication:** Groups inside groups. A company's group can include up to ten of its other groups, three deep at most, and what the outer group gives, its workspaces with their roles and its company role, reaches the people of every group inside it, while what an inner group gives stays with its own people. A group can sit inside several. A cycle or a chain of four is refused with the groups named, and one change to a company's groups is saved at a time. Including a group in one that gives a company role is for whoever holds Company roles, and in your app asks them to confirm it's them first. The console shows what each group includes, what it is inside and what it gets through it, and Everyone in it lists each person with how they are in the group and through which group. The company API sets includes and reads a group's people.
- **Authentication:** Group managers. Whoever manages a company's groups can name up to ten managers for a group, such as a team lead, who then add and remove the people named in it by hand and nothing else: not its workspaces, role, links or nesting, not themselves and not another manager. A manager holds no company access, and while their group gives a company role, by itself or through a group that includes it, every change of theirs is refused, so managing a group can never be used to climb. In your app, a manager sees Groups you manage on the Single sign-on screen (from @buildbase/sdk 1.0.0), with Add people and Remove. Your team names managers in the console, and the company API names them too. Deprovisioning someone ends their place as a manager at once.
- **Webhooks:** enterprise.group_members_changed whenever the people named in a group change, by a manager, a company admin, your team or a key, with who was added and removed and who acted, and a workflow trigger for it. enterprise.group_updated now says which groups were included or taken out, how many people that reached, and which managers were named or removed. All of it is in the company's trail, where someone joined to a workspace through a group inside a group reads as group Engineering, through Backend.

Source: https://www.buildbase.app/changelog/nested-company-groups-and-group-managers

## Stricter rules for one of a company's workspaces

20 October 2026. A company you sell to can now hold one of its workspaces to stricter rules than its own access policy, never looser, and its people confirm it's them there instead of being signed out everywhere.

### Added

- **Authentication:** Stricter rules for one workspace. A company you sell to can hold one of its bound workspaces, say its finance workspace, to shorter sessions, only its office network, fewer ways in or single sign-on required, fewer agents, people outside it kept out, or your team not signing in as its people there. Its admins set them on the Single sign-on screen in your app (from @buildbase/sdk 1.0.0), your team in the console, and its scripts with a company API key. A workspace's rules are never looser than the company's own policy, which still applies first: anything looser is refused and says which rule and why.
- **Authentication:** Someone a workspace's rules refuse is asked to confirm it's them there, with single sign-on or their passkey, and keeps working in the company's other workspaces with the same session; nobody is signed out when the rules change. Single sign-on is offered only when the app they signed in to offers it, and someone with no way to confirm is asked to sign in again instead. The refusal is a 403 your app can show as it is, and the SDK's new useWorkspaceAccess and WorkspaceAccessRefused offer Confirm it's you or Sign in again to match. Notifications from that workspace stay out of their inbox, and its live updates are not sent, until they are back in.
- **Webhooks:** A new event, enterprise.workspace_policy_updated, says when a company sets, changes or removes a workspace's rules, or loses them with the workspace's binding, and a matching workflow trigger, Workspace Policy Updated, starts a workflow from it.

Source: https://www.buildbase.app/changelog/stricter-rules-for-one-workspace

## Your customers' CI jobs call your app with no stored key

19 October 2026. A company you sell to can now let its CI jobs and cloud workloads act as one of its service accounts by exchanging the short-lived token their platform already gives them, so no company API key sits in CI.

### Added

- **Authentication:** Workload identity for company service accounts. Turn it on in the console on the WorkOS provider card, and a company's admin who manages its API keys can add a workload credential under one of its service accounts: GitHub Actions, GitLab, Google Cloud, AWS, Microsoft Entra or another OpenID Connect issuer, pinned to its repository, project or account by number and to a branch or environment. The job sends its own token to POST /api/v1/company/token and gets a company API token of at most an hour with the credential's scopes, and no refresh token. The card shows the step to put in the workflow, when the credential was last used and why it was last refused. Your team can add one from the enterprise in the console, and the company sets it up in your app from @buildbase/sdk 1.0.0, which also brings a helper for the exchange.
- **Authentication:** How a workload's access ends. Turning a credential off or deleting it, deleting its service account, or turning workload identity off ends its live tokens at once; narrowing a credential leaves live tokens their scopes until they expire, unless the company ends them now. Every token issued is in the company's trail with the run that got it, and every change it makes names it.
- **Webhooks:** Two webhook events and workflow triggers: enterprise.workload_credential_updated when a company adds, changes, turns on or off, or removes a workload credential, with the live tokens it ended, and enterprise.workload_access when a workload exchanges its token or is refused, with the reason.

### Fixed

- **Authentication:** A change in behaviour: in your app, a key made for a company's service account now carries only the scopes the admin making it reaches through their own company roles, as their own key and a workload credential already do. A scope beyond their roles is refused, naming it. Keys already made keep their scopes, and your team in the console may still give any scope.

Source: https://www.buildbase.app/changelog/workload-identity-for-company-service-accounts

## Several identity providers for one company

19 October 2026. A company you sell to can now sign its people in through more than one identity provider, each email domain sent to its own, and a second connection in WorkOS no longer stops its single sign-on.

### Added

- **Authentication:** Several identity providers per company. Add a second connection to a company in your WorkOS dashboard, such as Microsoft Entra ID for a company it bought beside its own Okta, and each of its verified email domains is sent to its own: the one it had stays the default, your team in the console or the company's admins in your app (from @buildbase/sdk 1.0.0) send a domain to another, and where a domain has two, the sign-in page asks which. Each one is a connection on your own WorkOS bill.
- **Authentication:** Each identity provider on its own. Its state, its SAML certificate and its warnings are kept apart from the others', the console and the Single sign-on screen list each one with the domains it signs in, and a domain no active identity provider signs in is named. An identity provider's answer for an address on a domain it does not sign in is refused before anyone is looked up.
- **Webhooks:** A webhook event and workflow trigger, enterprise.sso_routing_updated, when which identity provider signs in each domain changes. The connection and certificate events now also say which identity provider, whether it is the default, the domains it signs in and the domains nobody can sign in at.

### Fixed

- **Authentication:** A company with a second connection in WorkOS could no longer sign in from your login page. Every sign-in now names its connection to WorkOS, never the company's organization.

Source: https://www.buildbase.app/changelog/several-identity-providers-per-company

## Agents approved by your customers' identity providers

18 October 2026. A company you sell to can now let its own identity provider approve the AI agents that act for its people in your app, with no consent screen, and their access ends when it stops approving them or the person leaves.

### Added

- **Authentication:** Enterprise-managed authorization. Turn it on under Agent readiness, and a company you sell to can let its own identity provider approve the AI agents that act for its people: its admin pastes the identity provider's issuer once on the Single sign-on screen in your app (from @buildbase/sdk 1.0.0), copies what to enter into Okta, and an agent it approves then gets a short-lived token for one of the company's people with no consent screen. It is the Identity Assertion JWT Authorization Grant, which Okta calls Cross App Access, and it is built for Okta. An issuer the company's admin saves waits until its first sign-in matches one of the company's people by single sign-on, or your team approves it in the console, and an issuer that signs for everyone at a provider, such as Google's, is refused.
- **Authentication:** How an approved agent's access ends. Its token lasts an hour at most, or less if you or the company choose, and comes with no refresh token, so an agent the identity provider stops approving stops when its token does. Turning the identity provider off or removing it, a policy that no longer allows the agent, and a person deprovisioned, blocked or signed out by the company end its live sessions at once, and your app's revoke URL is told why. An agent's session can never change the company's settings, whoever it acts for.
- **Agents:** Agents that name themselves by a client ID metadata document, as Claude does, connect with no registration once you turn it on under Agent readiness. The consent screen names each one by its document's host and marks it unverified unless you listed that host as vetted, a company's identity provider can approve one only when the company's policy names it, and the clients table's new Metadata document source lists them apart from the clients you created.
- **Webhooks:** Two webhook events and workflow triggers: enterprise.agent_issuer_updated when a company's identity provider for agents is trusted, proven, approved, turned on or off, changed or removed, and enterprise.agent_access when it approves an agent for one of the company's people or your app refuses one, with the reason.

Source: https://www.buildbase.app/changelog/agents-approved-by-company-identity-providers

## Who WorkOS alerts, Google Workspace on demand, and an alert when roles drift

18 October 2026. See each company's IT and security contacts, have Sync now ask WorkOS to read a Google Workspace directory at once, and hear by webhook when a company's roles in WorkOS need attention.

### Added

- **Authentication:** Each company's IT and security contacts, the people WorkOS emails before its SAML certificate expires and when its connection has errors. The list is WorkOS's own, kept by the company's IT admin in the WorkOS Admin Portal, and you see it read only on each enterprise in the console, the company's admins whose role reaches Company roles see it on the Single sign-on screen (from @buildbase/sdk 1.0.0), and the company API reads it at GET /it-contacts under admins:read. Change in WorkOS opens the Admin Portal where the list is changed, for your team in the console and, in your app, for whoever holds Setup at Can manage, once the company's single sign-on is set up. A change made there shows within a minute, or at once with Refresh; Invite the IT admin by email still adds the address it invites.
- **Authentication:** Sync now on an enterprise's provisioning card also asks WorkOS to read a Google Workspace directory at once, rather than at WorkOS's own read about every 30 minutes. It asks only while the directory is linked or validating, and says what WorkOS answered: reading it now, already reading it, read less than five minutes ago with the minutes left (a cooldown WorkOS shares with its dashboard and Admin Portal), or syncing paused. The usual pull of the directory's changes runs whatever WorkOS says. A SCIM directory is never asked, since its identity provider sends each change to WorkOS as it happens.
- **Webhooks:** enterprise.workos_roles_attention when a company's roles in WorkOS start to need attention, such as a published role deleted or renamed in the WorkOS dashboard, or WorkOS unreachable for more than 24 hours, and enterprise.workos_roles_recovered when they are back in sync, with a workflow trigger for each. Each is sent once per change, never for the state you turn role assignment on in, and a WorkOS blip shorter than a day sends nothing. Both are in the company's trail too.

Source: https://www.buildbase.app/changelog/company-it-contacts-sync-now-and-roles-alert

## Companies choose how their people sign in, and admins confirm it's them

18 October 2026. A company you sell to can now choose the ways its people sign in without single sign-on, down to passkeys only, and reset a lost passkey. Its admins confirm it's them, at their identity provider or with a passkey, before its security settings change in your app.

### Added

- **Authentication:** Sign-in methods for each company. In its access policy, the company's admins in your app, your team in the console, or a company API key with policy:write tick the ways its people may sign in when they do not use single sign-on: Password, Magic link, Passkey, Google, Microsoft, GitHub or LinkedIn, down to Passkey alone. Single sign-on is always allowed, and with nothing ticked every way your app offers stays open, as before. Every way in checks the list once the person's password, link, passkey or social account is proven, and refuses with a sentence naming the ways the company allows; break-glass people follow it too, and each refusal is in the company's trail. A way your app's sign-in does not offer cannot be saved on the list, and a company admin cannot save one that would leave them no way back in. Sessions already open stay open: the policy counts the ones that began a way the list no longer allows, and Sign them out ends them.
- **Authentication:** Passkeys the company asks for. Under a list, a passkey counts only when the device verified the person with a fingerprint, a face or its PIN. Someone who signs in a way the list leaves out, with Passkey on it and no passkey yet, is sent to set one up, once, and then signs in with it. Adding another later takes a passkey sign-in from the last ten minutes, so a stolen password cannot add one, and while the company asks for passkeys nobody can remove their last. Someone who loses theirs is reset by the company's admins in your app, by your team in the console, or by a company API key with the new passkeys:write scope: their passkeys for your app are removed, they are signed out and emailed that it happened, and their next sign-in sets up a new one.
- **Authentication:** Company admins confirm it's them before the company's security settings change in your app: its access policy, signing everyone out, its single sign-on setup, its admins, roles and the groups that carry a company role, a new API key or service account, its log streams and a passkey reset. Unless they did so in the last ten minutes, they sign in again at the company's identity provider, which is asked to sign them in afresh rather than reuse a session it already has, or with a passkey that verifies them, set up first if they have none. A password sign-in does not count, however recent. They come back to the same session, in the browser tab that asked, with their change waiting to be saved: the confirmation is bound to that tab, so an address copied from it confirms nothing. A session your team opens as one of the company's people, or an agent's, cannot confirm, and the console and company API keys are never asked. Each confirmation is in the company's trail.
- **SDK:** The Single sign-on screen gives your customer's admins the sign-in methods, with how many of their people hold a passkey and Sign them out, and Reset passkeys beside a person's sessions (from @buildbase/sdk 1.0.0). A change that needs a confirmation opens Confirm it's you and keeps the unsent change on the screen until they save it again. useSaaSAuth().requireReverification() and isReauthRequired() do the same for your own screens, and removing a passkey from the account settings asks for a passkey first.

Source: https://www.buildbase.app/changelog/company-sign-in-methods-and-step-up

## Spam protection for forms, deploy hooks that report back, and monday.com in the console

18 October 2026. Forms can require a captcha and hold suspicious submissions for review. Deploy hooks and the monday.com integration, built but hidden until now, are in the console and working, and a workflow set to run every time no longer runs once per person.

### Added

- **Forms:** Forms can require a captcha, on the hosted page and in an embed, with no code to write. Pick a provider once under Forms > Spam protection, then switch on Require a captcha in a form's Protect dialog. The default, Managed by BuildBase, needs no keys or account, and your own Cloudflare Turnstile, hCaptcha or reCAPTCHA v2 Checkbox keys work too, with the secret encrypted at rest and never sent back to the console. Where the server has no Turnstile keys of its own, as a self-hosted install ships, Managed falls back to a proof of work the visitor's browser solves in about a second, with no third-party script or cookie: it makes every bot submission cost CPU time, but on its own it does not tell a person from a headless browser.
- **Forms:** Every form now drops the obvious bot traffic with nothing to switch on. Hosted and embedded forms carry a hidden field a person never fills, and a submission that fills it sees the usual success message and is never stored. The same content from the same address to the same form within ten minutes is stored once, so a retrying client no longer fires form.submitted twice. For spam that gets past a captcha, the Protect dialog adds a limit on links, up to 200 blocked words or phrases, a block on 70 known throwaway email domains or on your own list, and a daily cap. A link or word hit waits for review, badged with its reason such as "3 links (limit 1)", and reaches no webhook or workflow until someone approves it.
- **Forms:** Forms can be embedded in any website. A form's page has a Share and embed card with its link and an iframe snippet, and the embedded form resizes its frame as it grows and keeps its captcha and rules; until now the hosted form refused to load in a frame at all. A form you render yourself can carry the captcha too: the public form read names the widget and its site key, and the token travels in a _captcha field that is removed before the submission is stored or sent on. Require a captcha is off by default, because a form your own code posts sends no token until you add one, and on your own domain it needs the built-in check or your own keys, since the managed Turnstile key only works on BuildBase's own hostname.
- **Deploy hooks:** Deploy hooks are in the console, under Settings > Configuration. Save a deploy hook URL from Vercel, Netlify, Cloudflare Pages or Render, and the banner at the top of the console lists the blog posts changed since the last deploy and starts a build on the hook you pick. The screens were built but had no menu entry, and no step worked: a hook's first deploy was refused, and hooks were called with a GET, which Netlify and Cloudflare Pages do not build on. Adding a hook now refuses a URL that cannot start a build, such as a site address or a provider's dashboard page, and the deployment history never returns a hook's URL, since anyone holding it can start a build. Three new docs pages, with screenshots, cover each provider.
- **Deploy hooks:** A deploy from a Vercel hook reads Success, Failed or Canceled for the build it started. Point a Vercel webhook at BuildBase (Vercel offers them on Pro and Enterprise teams) and save its secret on the hook: only events signed with it count, and when Vercel cancels an older build because a newer one replaced it, the old deploy reads Canceled and the new one Success. If a build fails or is canceled before its content went live, the banner offers that content again instead of marking the hook up to date. A Deploy status column on the hooks list says whether the webhook works, from Not set up to Connected or Secret does not match.
- **Integrations:** The monday.com integration is in the console, under Apps. If your product ships a monday.com app, BuildBase runs its OAuth sign-in, records every install and uninstall, and forwards those events to your server, and the Settings tab opens with a five-step setup guide in the order monday's Developer Center asks for things. The screens were built but had no menu entry, and the main path was broken: a first install was refused before it reached monday.com's consent screen, every lifecycle event failed until a forward URL was saved, and the URLs the console told you to paste into monday.com pointed at the wrong host. All of it works now, credentials can be edited after Connect, there is a Disconnect, and three docs pages cover the setup.
- **Integrations:** Your monday.com app server gets two more URLs. Tokens from monday's new OAuth flow expire after a day, so the token handed over at install is dead by the next one; the Token URL answers a request signed with your client secret with a token refreshed as needed, and says when the person has to sign in again. And because monday workflows do not support the Authorization URL older integrations used, BuildBase now answers the Credentials URL and Delete Credentials URL that monday's replacement needs: one lists the person's saved sign-in without its token, the other removes it and revokes its tokens at monday.com too.
- **Agents:** Allow agent self-signup is on the Agent readiness screen under Authentication. With it on, your server can create an account for an agent with no person behind it, in one call to POST /api/v1/auth/agent/register made as one of your OAuth clients; the account has no console access and counts against your plan's end-user limit. The endpoint was built and documented, but its switch was missing from the console, and it now accepts only OAuth clients an admin created, never a public or self-registered one. Turning dynamic client registration on or off also reaches the metadata agents read at once, where it could lag by five minutes.

### Improved

- **Billing:** An upgrade waiting on its payment, for a card that needs 3-D Secure or was declined, is no longer announced before it is paid. subscription.upgraded, the Slack notice and the workspace notification go out once Stripe applies the upgrade, and an upgrade that is never paid is dropped without one. From @buildbase/sdk 0.0.86, Plan & Billing shows Complete payment with Stripe's invoice page instead of saying the plan was updated.
- **Billing:** BuildBase listens for two more Stripe events, customer.subscription.pending_update_applied and customer.subscription.pending_update_expired, so a paid upgrade applies as soon as Stripe confirms it and an unpaid one clears at once. An existing webhook endpoint needs them added: the Stripe setup check on the payment credentials page lists them as missing, and Fix the endpoint for me adds them. Until then upgrades still apply on invoice.paid.
- **Console:** More of the console says when something failed. A list whose request failed shows the error and Try again instead of an empty list or a zero, and a user page says Not found only when the user does not exist. The notification settings drew push and email as on when they could not be read, and a user's Devices tab said "No devices recorded"; both show the failure now. Delete, archive and confirm dialogs wait for the server and report a refusal instead of closing first, a refused invitation no longer says "Accepted", and Grant credits, Revoke credits and Reconcile on a workspace, which drew as buttons and opened nothing, work.
- **Console:** The console shows more of your plan's limits, where each one applies. Fifteen more limits have a usage meter, among them assets, audience and user lists, smart lists, deploy hooks, tracking scripts and workflow templates, and every meter recounts after a change. Eight features a plan can leave out show a lock on the control they govern, such as your own SMTP sender, targeting a feature flag at specific users, retrying from the dead-letter queue and audience bulk import. Assets can also be deleted now: there was no way to remove one, so every upload counted toward the asset limit for good.
- **Platform:** One organization can make at most 1,200 writes a minute through the console and organization APIs, however many API keys and sessions it spreads them across. The existing limits were per address and per API key, so an organization writing on several keys had no ceiling of its own, and its burst could queue ahead of other customers' work. A write over the limit is refused with "This organization is making changes too quickly". Only POST, PUT, PATCH and DELETE count, the SDK routes your end users call are not covered, and the number is the same on every plan.
- **Deploy hooks:** Deploys on the other providers say more. A Netlify build BuildBase starts reads "Deploy triggered by BuildBase hook" and the hook's title in Netlify's deploy list, instead of Netlify's generic hook message. A Render deploy that Render queued behind one already running reads Queued rather than Triggered, and a Render deploy links to it in your Render dashboard. View response on any deploy says which HTTP status the hook answered.
- **SDK:** Plan comparison tables and plan cards print "Unlimited" where a plan has no ceiling and a dash where it leaves something out, instead of -1 and 0. On our own live plans that was seven cells reading -1 and seventeen reading 0. That is @buildbase/sdk 0.0.82; from 0.0.81, a freemium plan reads "Start free" rather than "Subscribe" when there is no subscription yet, since there is nothing to pay. Both are in all eight locales.
- **Platform:** Lookups by a unique key on records that can be deleted now have an index they can use, on 48 collections in every organization's database. Those lookups scanned the collection instead: rollup lookups alone examined about 1.3 million documents in one test run's query log. That corrects last week's entry, which credited the rollup fix to the query itself; this index is what makes those reads cheap. A server builds the new indexes once, in the background, on its first start after updating.

### Fixed

- **Billing:** Changing plan during a free trial no longer ends the trial. The trial keeps running on the new plan and ends when it would have, and the new plan is billed then. Until now a plan change ended the trial at once: a trial started without a card had nothing to charge, so Stripe cancelled the subscription and the workspace landed on the paywall a moment after a Plan Upgraded notice, and with a card on file the new plan was charged at the click. The trial-ending banner now asks for what keeps access, a payment method, with Add payment method opening the billing portal, instead of Choose a plan.
- **Workflows:** A workflow set to "Allow always", the default, now runs every time it is triggered, and one set to "Cooldown" runs again once the cooldown has passed. Both ran once per person: the guard against duplicate triggers was meant to last 60 seconds but was also a unique key on a run record kept for a year, so a second login or the next monthly renewal for the same person was skipped as a duplicate. Only a repeat inside the same 60 seconds is refused now. A workflow that relied on running once should be set to "Once only".
- **Platform:** A request that names a record by an id that is not a valid id now answers not found. The lookup lost its only condition on the way to the database and matched the organization's first or newest row instead, so a malformed campaign id acted on the organization's first campaign, and cancelling a pending ownership transfer sent the withdrawal notice to an unrelated account rather than the person it was offered to. A key, slug or email of exactly 12 characters, such as ab@email.com, went the other way: it was read as a database id and never found. Attributes, audience members, rich-content blocks, plans and plan items now find it.
- **Security:** Secrets nested inside a setting were stored unencrypted when it was created, and encrypted only if that field was edited later: the client secrets of social sign-in providers, an email sending account's SMTP and Google credentials, server-side tracking secrets and the Google Ads refresh token. They are encrypted on create now; one saved before the fix and not edited since stays unencrypted until it is saved again, so re-enter it to encrypt it. The request log also stops writing credentials carried in a URL, such as a magic-link or password-reset token or an OAuth code: the value reads [redacted].
- **Security:** The push subscribe endpoint accepted any address as a push endpoint. In production it now accepts only the browser push services (FCM, Mozilla, WNS and Apple) and checks the rest of the subscription, and a stored subscription that fails those checks is never called. The subscriber list returned each subscription's encryption keys to any member who could read campaigns; the keys never leave the server now, and a subscriber's IP and location go only to members who may read users. Two organizations sending at the same moment could also have their pushes signed with each other's keys; each send carries its own.
- **Email:** Blocking a user now stops the email linked to them. The check matched the organization's newest user instead of the recipient, so whether a linked email went out depended on one unrelated account. Retrying an email whose queue job had expired said "Email being retried" and queued nothing; it resends now. Bounces, complaints and unsubscribes reported by the mail provider now reach the contact's activity timeline, and the email.bounced and email.unsubscribed events your webhooks and workflows receive carry the contact's audienceId instead of "[object Object]".
- **Billing:** A plan now sets the workspace features it manages. A feature marked "Subscription managed" was never written onto the workspace when a plan was assigned, changed, restored after a failed payment or reset for the month; a workspace picks up its plan's values the next time one of those happens. Reading the subscription of a workspace whose plan sat in no published pricing group failed, which the console showed as "no active subscription"; it answers with the subscription now.
- **Forms:** A published form no longer gives away who built it. Its public read, which answers anyone with the form's link, included the name, email address and profile image of the staff member who created the form; it answers without them now. The hosted page never used them, and your team still sees the creator in the console.
- **Notifications:** A push campaign sent to a list where nobody could receive push went to every push subscriber in the organization, because an empty list read as no list. It is refused now, before the campaign is marked sent, and so is a campaign sent with push switched off for the organization, which went out anyway, or with no VAPID keys, which showed Sent while reaching no one; each refusal says why, and the campaign stays a draft. Delivery logs also finish, as sent, partial, failed or completed, instead of staying at processing.
- **Integrations:** A monday.com app with New OAuth flow switched on can be installed. Every install was refused with "code_challenge is required"; the sign-in now sends the PKCE challenge and redirect URL the new flow asks for, so the Redirect URL registered in your monday.com app has to match the one the console lists. Tokens from the old flow, which monday.com is retiring, are traded for OAuth 2.1 tokens automatically with no one asked to consent again (all six in our test organization moved), and installer tokens, stored as plaintext until now, are encrypted at rest.
- **Integrations:** Signing in through your monday.com app created a verified user even with public sign-up switched off, and ignored the end-user limit; it obeys both now, like every other way a user is created. Process events, which adds everyone who installed your app to your audience, could pass the plan's contact limit; it stops at the same allowance a CSV import uses and says how many people it left out. With no Auth callback URL set, an installer was also sent back to monday.com with the access token still in the URL, where it stayed in browser history; nothing is added to that URL now.
- **Platform:** Organizations created before 12 June can reuse a value that belonged to something they deleted. Their databases kept unique indexes from before deleted records were exempted, so a rich-content or collection slug or an attribute key answered 409, a removed auth domain could not be added back, renaming a post to a deleted post's slug failed, and a browser that subscribed to push again after unsubscribing got an error and no working subscription. Those indexes were replaced on BuildBase cloud on 15 October, without leaving any value unguarded during the swap.
- **Self-hosting:** Calls from BuildBase's central server to a self-hosted installation, such as revoking a removed member's access, now carry the API key the installation checks. The central server stores that key encrypted and sent it as stored, so the installation refused the call; only a key regenerated under Account > Installations worked, because regenerating saved it without encryption. Every installation key is now stored encrypted and decrypted only to be sent, and a key the central server cannot decrypt stops the call.
- **Short links:** An archived or deleted short link answers 404 from its own organization at once. An archived link's next click, or any click on a deleted one, searched every organization on the server; on a test stack of about 1,250 organizations each such 404 took 138 to 216 seconds. Unarchiving a link works on the next click instead of staying 404 behind a cached miss, an archived link can no longer resolve to another organization's link with the same id, and a live link's click reads one index entry instead of scanning the organization's links.
- **SDK:** Push notifications shown by the SDK's service worker keep what the server sends: the image, action buttons, staying on screen when asked, and replacing an earlier notification with the same tag, where the worker showed only a title, body and icon. The tracked click link also wins over a url in the payload's data, so that url can no longer skip click tracking. That is @buildbase/sdk 0.0.83: an app that writes public/push-sw.js from PUSH_SERVICE_WORKER_SCRIPT at build time gets it on upgrade, but a hand-copied worker, including the one the README used to show, has to be replaced with that build step. The push docs also stop telling you to wrap your app in PushNotificationProvider, which SaaSOSProvider already mounts.
- **Console:** Console tables and pages fit the screen. Columns without a set width were fixed at 150px, cutting titles and URLs while a wide screen showed an empty band; columns now share the spare width, 28 of the 124 columns holding buttons were widened after measuring each one, and text that still does not fit ends in an ellipsis with the full text on hover. On a phone, Authentication's eight tabs drew a 991px strip on a 390px screen and several page headers ran past the edge; tab strips and headers now scroll inside their own row. The IP column on Beta users, always empty before, shows the IP.
- **Access control:** Changing a member's role now takes an organization owner or admin, and the role picker no longer offers owner: ownership moves only by transfer. Nobody can give a role above their own, and the last owner or admin cannot be demoted. The Change role dialog says why it is disabled rather than offering a Save that would be refused.
- **Security:** An API key now works only while its role is within its creator's current role. Demote the creator below a key's role and the key is refused from the next request; remove them from the organization and every key they created is revoked. A key already above its creator's role stops working with "API token role exceeds its creator's current role." and needs to be issued again by someone who holds that role.
- **Integrations:** A monday.com app server now signs its action reports with the installer's account and user ids and an expiry at most five minutes out. A report signed with an empty payload, as the setup page used to show, is refused with 401, and one naming a different installer than its signature with 403. The app server page shows the new signature. Lifecycle events are accepted only when monday.com signed them for your app's Client ID.
- **Users:** User attributes written through the SDK now have limits: at most 100 keys in one write, keys of letters, digits, underscores and hyphens up to 100 characters, text values up to 1,024 characters, and per person at most 100 keys the console does not define and 64 KB in all. A write over a limit answers 400 naming the field. A person whose attributes were already over a limit keeps them and can still change them; only growing past the limit is refused.
- **Users:** Responses that return a user no longer include that person's pending email verification or password reset codes, in the console API, in lists that include a user, and in the SDK's profile and attribute updates.
- **Self-hosting:** Only an owner or admin of an organization can view its self-hosted setup credentials or complete its setup, and setup can be completed once. BuildBase now calls a self-hosted server only with that server's own installation key; a self-hosted organization with no key of its own is refused until one is generated.
- **Platform:** A request body the server cannot check is now refused with 400 instead of being passed on. List endpoints accept only plain field names in a projection and the documented operators in a filter, and answer 400 for anything else; a single read stops after 30 seconds instead of running on after the caller has gone.
- **Authentication:** The OAuth token, revocation and introspection endpoints now answer 400 invalid_request when a parameter is not a single value of at most 4,096 characters, before anything is looked up. A parameter written in bracket form in a form-encoded body, or sent as an object in JSON, could widen the lookup to a token or code the caller never held. resource may still be repeated, up to 20 times.
- **Platform:** The 29 console and SDK routes that read a request body with no schema now check it before anything is read or written. Public form submissions refuse field names over 256 characters and lists over 1,000 items, collection records refuse field names over 256 characters, and a smart list filter is held to the same operators as any other list filter, so a list saved with one outside them stops syncing instead of running it.

Source: https://www.buildbase.app/changelog/form-spam-protection-and-deploy-hooks

## Schedule campaigns, test subject lines and keep bounces low

18 October 2026. You can schedule campaigns and A/B test subject lines. A big list goes to a small sample first, sending pauses itself when bounces or complaints climb, and Amazon SES joins the senders.

### Added

- **Email:** You can schedule a campaign from a minute to a year ahead, and unschedule it.
- **Email:** The first campaign to a list of 1,000 or more goes to 5% of it first, as a warm-up. The rest is held for 3 hours while bounces and complaints stay low, and Send the rest now skips the wait.
- **Email:** You can A/B test two subject lines. A share of the list, 20% by default, gets one of the two subjects. After a wait, 4 hours by default, the better one goes to the rest. Pick the winner now decides early.
- **Email:** Sending health: a campaign pauses itself past a 2% bounce rate or a 0.08% complaint rate, where a complaint is someone marking your email as spam. Over 7 days, 5% bounces or 0.3% complaints block marketing mail until you choose Lift block.
- **Email:** An address that hard-bounces, meaning mail to it fails for good, goes on a never-email list for 180 days. A send with no unsubscribe link or no usable sender is refused with 422.
- **Email:** You can pause, resume and cancel a campaign while it sends.
- **Email:** You can send through your own Amazon SES, connected under Add sender > Amazon SES. Bounces and complaints come back through SNS, Amazon's notification service.
- **Email:** SMTP senders get bounce tracking: BuildBase reads a mailbox you name every ten minutes over IMAP, the standard way to read a mailbox.
- **Audience:** Forms can collect subscribers with double opt-in, where each new subscriber confirms by email first.
- **Audience:** Campaign reports break results down by mailbox provider, and domain checks show DMARC, the email record that guards your domain against spoofing.

### Improved

- **Email:** Readers can unsubscribe in one click from their mail app: one-click unsubscribe (RFC 8058) works.
- **Email:** An unsubscribe never stops sign-in codes, magic links or password resets, and they no longer wait behind campaigns.
- **Webhooks:** Behaviour change: when someone marks your email as spam, the event is email.complained, not email.bounced.
- **Email:** Removed: the empty Microsoft tab in Add sender.

### Fixed

- **Email:** A double click no longer creates an unsubscribe group twice, and changing a template's type asks you first.
- **Email:** Template selects have names that screen readers announce. A receiving record (the DNS record for incoming mail) reads Verified only when Mailgun says it is valid.

Source: https://www.buildbase.app/changelog/scheduled-campaigns-warm-up-and-sending-health

## See the storage you use, plus security and sign-in fixes

18 October 2026. You can see every stored file counted against your storage allowance. Image URLs are capped, rate-limited answers say when to retry, and fixes reach security, sign-up, workflows, push, the audience, the console and self-hosting.

### Added

- **Billing:** You can see how much storage you use against your allowance, because every stored file is counted. The Storage card on the billing page and the meter in Assets show the bytes you store, in GB-months. One GB-month is 1 GB kept for a whole month.
- **Console:** Before you delete an image or make it private, the console lists where it is used.

### Improved

- **Platform:** Behaviour change: an image URL field takes at most 2048 characters, and a longer one is refused with 400.
- **Platform:** When you send too many requests, the answer says when to try again: a 429 answer carries the reason rate_limited and retryAfter.
- **Platform:** A request with an unknown ?org= answers 404 (not found) instead of 500.
- **Authentication:** Behaviour change: when your app has no Email and password method, people cannot sign up with a password. /register refuses it with 403 method_unavailable.
- **Console:** Long selects can be searched, and the Devices tab asks before ending a session. Menu names are in sentence case, and 24 more audit log actions have labels.
- **SDK:** The plan and credit pickers open on the visitor's currency, which is a behaviour change. 28 more countries have a currency, and Plan & Billing shows no N/A price while it loads. These came in @buildbase/sdk 0.0.84 to 0.0.88.

### Fixed

- **Security:** An audience import's status can be read only by its own organization. The organization export hides password hashes, session ids, tokens and secrets.
- **Security:** Requests sent at the same time can no longer reuse a reset code or get past the five-try limit.
- **Security:** Redirect URLs that start with javascript: or data: are refused. Code requests take the same time to answer whether or not an account exists, so the timing gives nothing away.
- **Platform:** A badly formed request now gets a 400 answer. That includes one the sanitiser (the input cleaner) cannot read, and one whose whole shape breaks a schema rule. Before, these passed through or failed with a 500 or 503.
- **Platform:** Busy servers no longer fail requests by closing database connections that are still in use.
- **Authentication:** A failed sign-up no longer locks its address out, and the browser that signs up appears under Devices. The password and magic link method routes refuse another method's id.
- **Workflows:** A Wait for event step resumes again after a server restart.
- **Notifications:** A push retries only the devices that failed briefly, and a push campaign sent right after you turn push off no longer goes out.
- **Audience:** Audience migrate reports the records it could not move, and collection versions get unique numbers.
- **Self-hosting:** The compose file passes TRUST_PROXY, and the generated compose gives the server 180 seconds to stop. Installation routes act only on organizations the caller runs.

Source: https://www.buildbase.app/changelog/storage-meter-security-and-platform-fixes

## Enterprise SSO and directory sync, through your own WorkOS account

17 October 2026. Sell to companies whose IT team asks for single sign-on. Add the company as an enterprise, let its IT admin connect their identity provider from a link, require SSO if they ask, and let their directory add and block their people. It all runs through your own WorkOS account.

### Added

- **Authentication:** Enterprise single sign-on. Save your WorkOS API key on the new Enterprise tab under Authentication, add a company you sell to as an enterprise, and send its IT admin a setup link. They connect Okta, Microsoft Entra, Google Workspace or any SAML or OIDC provider in WorkOS's Admin Portal without asking you. Their people choose "Continue with SSO" on the hosted sign-in page and are sent to their own identity provider by the domain of their email. WorkOS bills the connections to your WorkOS account.
- **Authentication:** Require single sign-on per company. Once it is on, that company's people cannot sign in with a password, a magic link, a social account or a passkey: the sign-in page sends them to their identity provider instead. Sign-ins started from the identity provider's own dashboard land in your app too, once you set the sign-in endpoint in your WorkOS dashboard.
- **Workspaces:** Bind an enterprise to the workspaces its people belong in. Someone from that company who signs in for the first time lands in those workspaces with the role you set, without an invitation, and someone you later remove is not put back by signing in again.
- **Authentication:** Directory sync (SCIM). Turn provisioning on for an enterprise and its own directory adds and updates its people, puts them in the bound workspaces, gives them roles from their directory groups, and blocks and signs out the people who leave; someone rehired is let back in. Nobody the directory touches gets a welcome or "you were added" email. Changes arrive within five minutes, or within seconds with the optional webhook.
- **SDK:** A Single sign-on screen in the SDK's settings (from @buildbase/sdk 1.0.0). A workspace admin in your app sees which company the workspace belongs to, whether its single sign-on and directory sync work, and opens the setup for their IT admin, without asking you. Hide it, or keep it and drop the buttons, from the settings config.
- **Webhooks:** Three webhook events for the directory: enterprise.user_provisioned when it creates someone, enterprise.user_deprovisioned when it blocks someone, and enterprise.directory_synced once per enterprise per sync, with counts.
- **Authentication:** A warning before a company's SAML certificate expires. When it does, nobody at that company can sign in by SSO, and until now nothing said so. The enterprise's row and detail show "Certificate expires in 5 days" or "Certificate expired", with Check now and a link that opens the setup on the certificate for their IT admin. Two webhook events, enterprise.certificate_expiring and enterprise.certificate_renewed, let you page someone or email the customer.
- **Authentication:** Each enterprise has its own audit trail: sign-ins, refused sign-ins with the reason, people sent to SSO by the requirement, what the directory added, changed and removed, certificate warnings and every setup change. Read it in the enterprise's Activity section, filter it by kind and date, download it as CSV, or pull it with an API key for a SIEM. It reaches back as far as your plan keeps the auth audit log.
- **SDK:** The SDK's Single sign-on screen shows the certificate warning with a Renew button, and gives your customer's own admins their company's activity with a CSV download (from @buildbase/sdk 1.0.0), so their security team gets its sign-in report without a ticket to you.
- **Authentication:** An access policy for each company you sell to. Sign its people out after a stretch of inactivity (15 minutes to 30 days) or after a fixed time however active (1 hour to 180 days), allow sign-in and requests only from its own network (IPv4 or IPv6 ranges), and name up to five break-glass people who can still sign in, optionally only with a passkey, when its identity provider is down and single sign-on is required. Every break-glass sign-in is in the company's trail and sent as a webhook so someone can be paged.
- **Authentication:** Sign one of a company's people out, or all of them, at once: every session and every connected app or agent ends. From the people list or Sign everyone out in the console, or by the company's own admin in your app.
- **SDK:** The Single sign-on screen gives your customer's admins the same access policy and sign-out (from @buildbase/sdk 1.0.0). It offers the address they are saving from and refuses an allowlist that would shut them out; you can keep the policy to yourself in the console. Three new webhook events: enterprise.policy_updated, enterprise.break_glass_used and enterprise.sessions_revoked.
- **SDK:** Someone who opens your app from outside their company's allowed network keeps their session instead of being signed out, and your app hears about it once with useAccessRefused() or onAccessRefused, with a sentence ready to show. Back on the network, the app opens signed in.
- **Authentication:** Roles from your customer's identity provider, without provisioning. Map the roles WorkOS's role assignment sends at sign-in, or the identity provider's groups, to a role in your app or a workspace; they are worked out again at every sign-in, and saving the mappings applies them at once to everyone who has signed in.
- **Authentication:** You hear when a customer's IT admin deactivates, deletes or reactivates their single sign-on connection: three new webhook events (enterprise.connection_deactivated, _activated and _deleted), an entry in the company's activity, and a warning in the console while nobody can sign in through it.
- **Authentication:** Stream a company's audit trail to its own SIEM. Add up to three log streams per enterprise: an HTTPS endpoint (each request signed the same way as our webhooks), Datadog, or a Splunk HTTP Event Collector. Entries arrive in order within about ten seconds, and when the receiver is down nothing is lost: the stream retries for as long as it takes, says it is failing, and catches up once the receiver answers. Two new webhook events, enterprise.log_stream_failing and enterprise.log_stream_recovered, so you can page someone.
- **Authentication:** Insights for each enterprise: how many of its people signed in over the last 7, 30 or 90 days, how they signed in, who was refused and why, day by day, and the health of the connection, the certificate, the directory and each log stream.
- **Workflows:** Enterprise SSO events start workflows. A certificate about to expire, a connection your customer's IT admin turned off, a log stream that keeps failing, a break-glass sign-in and every other enterprise event are triggers under Enterprise SSO in the workflow builder, each with its details as merge fields, so you can email the customer's IT admin or page your own team without a webhook receiver of your own.
- **SDK:** Your customer's own admins get the same insights and manage their log streams from the Single sign-on screen, with a test event and the signing secret shown once (from @buildbase/sdk 1.0.0). If you keep their security settings yourself, they see the streams read-only.
- **Authentication:** Company admins, apart from workspace admins. Until now anyone who could edit a bound workspace's settings could change the whole company's access policy, read its trail or sign everyone out. Name the company's admins in the enterprise's detail, let the company name them from your app, or let its identity provider decide with a role mapping to Company admin; from then on only they manage the company's security settings. Two webhook events and workflow triggers, enterprise.admin_added and enterprise.admin_removed.
- **Authentication:** The company's trail now shows who joined, left or changed role in its workspaces: invitations sent and withdrawn, people added by hand, by single sign-on or by the directory, role changes and removals, with the workspace and who did it. Its admins read it, export it and stream it to their SIEM like the rest of the trail.
- **Authentication:** Connected apps and agents, for the company. See which third-party apps and AI agents a company's people have connected to their accounts, how many people and which scopes, and disconnect one person or everyone at once. The access policy decides which may connect at all: any, only the ones approved, or none. A refused app gets the company's sentence on the consent screen, and tightening the policy ends existing access at the app's next refresh. Signing people out, and the directory removing someone, now also take their connected apps' consents.
- **SDK:** Your customer's admins name their company admins and manage connected apps from the Single sign-on screen (from @buildbase/sdk 1.0.0), and the activity gains Workspace members, Company admins and Connected apps filters.
- **Authentication:** Company API keys. A company's own tools, its compliance archive, its SIEM jobs, the script that signs a leaver out, can now call your app as the company with a key that carries only the scopes it was given: read the trail, read people, sign people out, read or change the access policy, insights, company admins, connected apps and log streams. A key is shown once, can be limited to the company's addresses, lasts 30, 90 or 365 days or does not expire, and never manages other keys. Every change made with one is in the company's trail under the key's name.
- **Authentication:** Service accounts for each company. A company admin's own key stops working the moment they stop being an admin; a key that belongs to a service account outlives whoever set it up, so automation keeps running when people leave. Your team can make keys for a company's service accounts in the console, and revoke any key.
- **SDK:** Your customer's admins make and revoke API keys and service accounts from the Single sign-on screen, and see the key once beside the address it calls (from @buildbase/sdk 1.0.0).
- **Authentication:** Company roles. A company no longer has to make everyone who touches its settings an admin. Each person it names gets a role: Company admin manages everything, Security admin manages the access policy, sign-outs, connected apps, API keys, log streams and setup and only views the rest, and Auditor views everything and changes nothing. A company can make up to 20 roles of its own, area by area, such as a help desk that signs people out and reads the trail. Only a Company admin gives roles out, so no role a company makes can be used to climb to a broader one. A company API key someone makes for themselves can never do more than their roles allow, on the day it is made or after.
- **Workspaces:** Company groups. A company's admins put people in a group by hand, or link it to a group or role from their identity provider, and say what being in it gives: a role in up to 20 of the company's workspaces, and a company role. Someone added to the group joins those workspaces with that role, and someone who leaves it goes back to what they had before. It applies when the group is saved and again at every sign-in and directory sync, without your team writing a mapping.
- **SDK:** Your customer's admins manage their company's groups and roles from the Single sign-on screen, and each section of that screen shows only to the people whose role reaches it.
- **Webhooks:** Six webhook events and workflow triggers for the company's groups and roles: enterprise.group_created, enterprise.group_updated, enterprise.group_deleted, enterprise.role_created, enterprise.role_updated and enterprise.role_deleted. enterprise.admin_added and enterprise.admin_removed now carry the role given or taken away.
- **Authentication:** WorkOS verifies your customers' email domains. Add a domain to an enterprise and it goes on the company's WorkOS organization; its IT admin publishes the DNS record WorkOS's Admin Portal shows them, opened from Verify in WorkOS in the console or from the IT-admin invitation with its new Domain verification option. BuildBase keeps no DNS record of its own. A domain the IT admin adds and verifies in the portal shows up on its own, Refresh from WorkOS reads the verdict on the spot, removing a domain removes it in WorkOS too, and a domain counts only while WorkOS verifies it.
- **Authentication:** Joining by email domain. A company can let anyone with a verified email on its domains who signs in with a password, a magic link, a social account or a passkey become one of its people on the spot, or ask to join first, with requests its admins approve or decline. Someone declined is not asked about again for 30 days.
- **Authentication:** Claim the accounts already on a company's domains. The people at Acme who signed up with a password, and verified their email, before Acme became your customer are listed, and the company's admins or your team bring them in, 100 at a time, picked by hand or all of them: they join the company's workspaces and are signed out, so their next sign-in follows its policy and its SSO. Nobody is emailed; hook a workflow to enterprise.person_joined if you want them told.
- **Workspaces:** Rules for people outside the company in its workspaces, such as contractors. Allow them, limit them to editor or viewer and hold them to the company's IP allowlist, or block them: a blocked outsider cannot be invited or added, and one already in is refused and no longer sees the workspace. The workspace's owner is never refused or lowered.
- **Authentication:** Required single sign-on now reaches everyone on a company's verified domains, including accounts made before it was turned on, which link to the company at their first SSO sign-in. Break-glass still covers only the company's own people.
- **Authentication:** Someone who loses access to a company's setup, through a role, a group, a block, being signed out, leaving its workspace or removal from your console, has any WorkOS Admin Portal session they opened ended in WorkOS too.
- **Authentication:** The company API reads requests to join, the accounts on the company's domains and the people outside it, and approves, declines and claims, under people:read and people:write. GET / now answers each domain's status, who verified it and WorkOS's last error.
- **Webhooks:** Four webhook events and workflow triggers: enterprise.person_joined, enterprise.join_requested, enterprise.join_request_declined and enterprise.domain_removed; enterprise.domain_verified now fires on WorkOS's verdict. The WorkOS webhook you register from the console now carries the certificate, connection and domain events as well as the directory's, so they arrive in seconds; if you registered it earlier, choose Register again, and the endpoint it replaces is deleted in WorkOS for you.
- **Authentication:** Company audit logs in WorkOS, a switch on the Enterprise tab. Turn it on and each company's trail also goes to WorkOS: its IT team reads and exports it in WorkOS's Admin Portal, you choose how long WorkOS keeps it, from 30 days up to ten years, and its activity can stream to its SIEM from WorkOS. It is off by default because WorkOS bills it as an add-on to your own WorkOS account, and nothing changes until you turn it on. Retention can be raised but never lowered, so the console asks before it saves.
- **Authentication:** Two exports of a company's trail. The CSV stays for everyone and reaches back as far as your plan keeps the auth audit log. With company audit logs on, Export from WorkOS adds WorkOS's own: up to 31 days at a time from the last three months, as a link that works for ten minutes. Both are in the console, in your app and in the company API, and every download is now in the company's trail.
- **Authentication:** With company audit logs on, a company's new log stream comes from WorkOS: Datadog, Splunk, AWS S3, Google Cloud Storage, Microsoft Sentinel, Snowflake or any HTTPS endpoint. Your team sets it up from the console, or invites the company's IT admin to from there; each stream is billed to your WorkOS account, so the company sees its stream in your app but cannot start one. Streams BuildBase already sends for a company keep delivering until it deletes them, and every org without the switch keeps BuildBase's own.
- **SDK:** With company audit logs on, the Activity on the Single sign-on screen adds Export from WorkOS and Open the audit log viewer beside Download CSV, and Log streams shows the company's WorkOS stream, read only (from @buildbase/sdk 1.0.0).
- **Webhooks:** enterprise.log_stream_failing and enterprise.log_stream_recovered now say which kind of stream it was, source: buildbase or workos, so a workflow can tell a WorkOS stream in error from one of ours whose receiver stopped answering.
- **Authentication:** Roles WorkOS assigns, read for every company. When a company's IT admin assigns their groups to roles in WorkOS, BuildBase now reads the role WorkOS gives each person, from the directory as well as at sign-in, and offers it first in the enterprise's role mappings as WorkOS role. Map it to a role in your app, a workspace role or Company admin, or let the company link it to one of its groups. There is nothing to turn on, and your directory group, SSO role and SSO group mappings keep working beside it.
- **Authentication:** Let the IT admin assign roles in WorkOS, a switch per company in the console, off until you turn it on. The company's roles and groups can then be published to its WorkOS organization, and its IT admin assigns their identity provider's groups to them in WorkOS's Admin Portal, opened from Assign roles in WorkOS. Each role and group has a Show in the Admin Portal switch. What each role gives is still decided in BuildBase, WorkOS never takes away a role someone was named with by hand, and only your team can publish Company admin. A published role keeps its slug for as long as it stays published, so renaming it never breaks the IT admin's assignments.
- **Authentication:** A WorkOS roles card on each enterprise reads the company's roles back from WorkOS and says they are in sync, or what needs attention: a role deleted or renamed in the WorkOS dashboard, a change still waiting to be written, a role people carry that gives nothing. Each comes with its fix, such as Publish again, Retry now or Map it, and the enterprises list marks a company that needs a look. Taking out a role the IT admin still has groups assigned to is refused, with a sentence saying what to remove in the portal first.
- **Authentication:** The company API reads a company's roles in WorkOS at GET /workos-roles under admins:read, and its role and group changes take assignableInWorkOS to publish one or take it out.
- **SDK:** Once you turn it on for a company, its admins publish their roles and groups to WorkOS from the Single sign-on screen, see each one's slug and whether the company's roles are in sync, and open Assign roles in WorkOS for their IT admin (from @buildbase/sdk 1.0.0).
- **Webhooks:** enterprise.role_updated and enterprise.group_updated name workos among what changed when a role or group is published to WorkOS, renamed while published, or taken out, so a workflow can tell the company's IT admin a new role is ready to assign.
- **Authentication:** A company can keep its network to its own accounts. Its IT team sets their proxy to add an allowed-company-ids header naming the company to every request to your API host, and on that network a personal account, or another company's, is refused at sign-in and on every request, while the same session keeps working off that network. The header only applies in an app whose companies it names, so on the shared cloud host it never touches another app, and Check this network on the SDK's Single sign-on screen (from @buildbase/sdk 1.0.0) says what the proxy actually sent. Each refusal is in the company's trail with the refused account's email.
- **Authentication:** Every session your team opens as one of a company's people is now in that company's trail. A token exchange with an owner or admin key that names one of its people is recorded as Session opened by the app's team, with your key's name and the reason you send, and fires the enterprise.app_team_session webhook. In the company's access policy, Your team may sign in as the company's people (its admins see it as The app's team signing in as one of your people) can be set to Not allowed, from your console or by the company: the sessions your team has open as its people end, and the exchange is then refused with app_team_sessions_refused. Name your support keys for what they do: the company reads the name.
- **Authentication:** End one session on one device. Sessions, beside Sign out in a company's people list, shows each session a person has, with the device, browser, place, when it began and how they signed in, and End signs out a lost laptop while the person stays signed in everywhere else. It is in the console, on the SDK's Single sign-on screen (from @buildbase/sdk 1.0.0) and in the company API (GET and DELETE /people/:userId/sessions), and enterprise.sessions_revoked fires with scope: session.
- **Authentication:** People a company's policy signs out are told why. Instead of a bare 401, the next request gets session_ended with the reason and a sentence such as "Your company signs you out after 8 hours. Sign in again." Your app hears it with useSessionEnded or the onSessionEnded callback (from @buildbase/sdk 1.0.0), and the hosted sign-in page shows the same sentence when they come back.

Source: https://www.buildbase.app/changelog/enterprise-sso-and-directory-sync

## Manage any subscription from one menu, and see revenue by month

17 October 2026. Your team can act on any workspace's subscription from one menu and see revenue by month. Your customers get overage caps, allowances per member, billing contacts, and limits on devices, workspaces and agents that BuildBase counts for them.

### Added

- **Billing:** Your team can act on a workspace's subscription from one place: the Actions menu on its subscription card in the console. It holds Change plan, Comp plan, Extend trial, End trial now, Reset trial eligibility, Apply discount, Remove discount, Cancel at period end, Resume, Pause, End pause and Re-sync from Stripe. Comp plan gives a plan for free. Each action asks for a reason and is logged, and the same actions are at /api/subscriptions/actions.
- **Console:** A Revenue page shows your subscription revenue by month, per currency. It covers MRR (monthly recurring revenue), churn, trial conversion and cash, and counts subscriptions that are paying, trialing, past-due or comped (given free).
- **Billing:** Your customers can cap a workspace's overage on a quota, meaning its use past the included allowance. They can also get alerts at up to five usage levels of the allowance. When usage is refused, the answer says when the quota resets. Route: PATCH /api/v1/public/workspaces/:workspaceId/quotas/:slug.
- **Billing:** A quota on a workspace plan can give each member an allowance of their own, with a shared pool to draw on when it runs out.
- **Billing:** Your app can count named items against a plan limit, claiming a slot for each one and releasing it later. Routes: POST /api/v1/public/me/limits/:slug/claim and /release. A plan can also limit the devices a person signs in from, the workspaces they own and the agents they connect, and BuildBase counts these for you. It answers with CLAIM_LINKED, DEVICE_LIMIT_REACHED or CEILING_REACHED.
- **Workspaces:** Each person can pick a default workspace, and a call that names no workspace lands there. Set it with defaultWorkspaceId on PATCH /api/v1/public/profile.
- **Billing:** You can name up to 10 billing contacts besides the owner. They get failed payment notices, receipts, refunds and expiring card notices.
- **Billing:** A workspace's plan can move to the signed-in person's own account, without charging twice for anything already paid. Route: POST .../subscription/move-to-user.
- **Billing:** You choose what happens after a failed payment. A pricing group's lapse policy sets how many days of grace follow it, and then whether the workspace drops to free, turns read only or is suspended.
- **Billing:** Five add-on rules under Settings > Organization let you decide how add-ons behave in particular cases. Two of them are "A recurring add-on bought during a trial" and "Deleting a workspace or a person holding paid add-ons". The second can refuse the delete, and the API then answers 409 PAID_GRANTS_PRESENT.
- **Webhooks:** Your app can hear about many more billing and account changes through new webhook events. Subscriptions: subscription.trial_extended, subscription.paused, subscription.unpaused, subscription.discount_applied and subscription.discount_removed. Add-ons: addon.purchased, addon.expired, addon.revoked and addon.changed. Credits: credit.reserved, credit.settled, credit.released, credit.threshold_crossed and credit.top_up_failed. Limits: quota.threshold_reached and entitlement.ceiling_reached. Consent: oauth.consent_granted and oauth.consent_revoked. Enterprise: enterprise.created, enterprise.deleted, enterprise.key_created and enterprise.key_revoked. Every subscription and payment event now names its subject: the workspace or the person it belongs to.

Source: https://www.buildbase.app/changelog/subscription-actions-revenue-and-billing-contacts

## Billing changes to know about, two removals and fixes

17 October 2026. Free plans can no longer allow overage, and Stripe Checkout charges the price you set, in the plan's own currency. Recurring add-ons follow clearer rules, two old payment routes and a never-enforced workspace option are gone, and billing and console bugs are fixed.

### Improved

- **Billing:** Behaviour change: a free plan can no longer allow overage, meaning usage past its quota. Publishing one with a quota that allows overage is refused, and the refusal names the quotas.
- **Workspaces:** Behaviour change: you cannot switch to Personal mode (one workspace per person) while anyone owns two or more workspaces. The API answers 409 PERSONAL_MODE_OWNERS_OVER_LIMIT.
- **Billing:** In Stripe Checkout, your customers now pay the price you set. Checkout no longer converts a price into the buyer's local currency, because Adaptive Pricing is off.
- **Billing:** Lowering a recurring add-on keeps the units already paid for until the period ends. Switching billing interval re-prices it, and a plan that already includes it removes it. You can also limit an offer so it sells only beside plans you choose.
- **Billing:** Removed: two old payment routes. GET and DELETE /api/payments/subscription and GET /api/payments/get-checkout-url now answer 410 ENDPOINT_GONE. Use the workspace subscription routes instead.
- **Workspaces:** Removed: the Owner only choice for who can create workspaces. It was never enforced and behaved as Everyone, so the API now takes true or false only. @buildbase/sdk 0.0.85 reads it the same way.

### Fixed

- **Billing:** A seat quantity changed in the Stripe dashboard now shows in the console, and usage resets at renewal without waiting up to ten minutes.
- **Billing:** Quota refusal messages no longer read "per month a month" or "magic links sents". A payment-action-required email goes out once per invoice.
- **Workspaces:** A workspace on a Free plan can be deleted again.
- **SDK:** Reading one plan group version through the SDK works: GET /api/v1/public/:orgId/plan-group-versions/:id now answers. That fixes usePublicPlanGroupVersion, plans.getVersion and the get_plan_version tool.
- **Console:** Accepting an ownership transfer moves the organization's BuildBase card and plan to the new owner.
- **Console:** The paywall no longer offers a second trial, and Manage billing opens one Stripe tab instead of two.
- **Console:** Choosing Free and then switching organization no longer asks you to choose a plan. The pricing group preview loads catalogs of more than 139 items.

Source: https://www.buildbase.app/changelog/billing-behaviour-changes-removals-and-fixes

## Plan allowances checked up front, and push failures that say why

12 October 2026. Push sends, webhook deliveries, conversions and workflow events are checked against your plan before they happen. A failed push says why, monday.com and deploy hooks explain themselves, and the console gets a round of fixes.

### Improved

- **Billing:** Your plan's monthly allowance is now checked before work happens, not counted afterwards. That covers push sends, webhook deliveries, conversions sent to ad platforms and workflow trigger events. Once an allowance with no overage is used up, the work is skipped, and you hear about it at most once an hour through organization.end_user_ceiling_reached. A skipped webhook delivery is not retried, and a skipped conversion is logged with its reason. Self-hosted installs are never refused.
- **Email:** Email drafts count against a plan limit, and archived drafts do not. Create drafts on a campaign is refused once the organization holds its plan's max-email-drafts in drafts that are not archived. The Drafts page shows the meter.
- **Console:** When your plan refuses or locks something, the message names the feature in words, such as "Your plan does not include the monday.com integration". Counts read monthly active users and GB of storage instead of mau and storage gb.
- **Deploy hooks:** When a deploy does not start, the message names the hook and what it answered, and never shows the URL. For example, "Production site" answered 404 Not Found and may have been deleted at your hosting provider, or it did not answer within 15 seconds. On a plan without deploy hooks, Create hook is locked instead of refusing after the form is filled in.
- **Integrations:** To use Connect for monday.com, you need a plan that includes the integration. Reading, editing, Disconnect and installs through monday.com are never refused. A user's page shows the monday.com tab only on such a plan.
- **Integrations:** The monday.com tab's chart counts the person's tasks. For someone who never linked an account, it reads "This user has not linked a monday.com account yet". Resend reports what your application server answered, and the events table shows each installer's email, name and ids.
- **SDK:** From @buildbase/sdk 0.0.80, agent clients stop asking you to confirm writes that only add something. Every built-in MCP tool (an action an AI agent can take) has a title, such as List Workspaces or Invite Member, and says whether it is destructive. The consume_credits tool is marked destructive, so a client asks before spending credits.

### Fixed

- **Notifications:** When a push does not reach someone, the Delivery log on Notifications, a user's page and a workspace's page says why. It shows reasons such as Subscription expired or Service timed out, where it read 0/1 device.
- **Notifications:** A push campaign's page shows its error with Try again, and says Not found only when the campaign does not exist. Generate VAPID Keys, which makes the keys web push needs, shows that it is working.
- **Workflows:** The Send Push Notification step reports what really happened. It returns the real push log, so its status and delivered outputs fill in. With no VAPID keys or no push on the plan, it reports skipped with push_unavailable, where it reported success.
- **Workflows:** The welcome push to a newly subscribed browser follows your plan and push switch, and counts toward the push allowance. A new organization can read and change its email and push switches straight away. A push campaign's click URL can be cleared.
- **Console:** Search and filter terms that read as a number, such as 2024, work instead of answering 400. The IP filter on Beta users now filters.
- **Agents:** After a downgrade, you can switch something off in Agent readiness without the plan refusing it, because saving sends only what you changed. A maxClients set through the API is kept.
- **Console:** The floating Setup guide no longer hides the bottom of a page. On a phone, a table's actions column no longer pins over the other columns. An empty table reads Page 1 of 1, and a dropdown in a short dialog no longer opens over its title.
- **Console:** The asset upload dialog states your plan's maximum file size, instead of always saying 1 MB.
- **Console:** A member who cannot save sees the Agent readiness switches and Hide BuildBase badge disabled, instead of being able to flip them.
- **Console:** Switches that depend on your plan, and icon-only buttons, have names that screen readers announce. Toasts, the short pop-up messages, fit the screen, and a copy confirmation says what was copied.

Source: https://www.buildbase.app/changelog/allowances-checked-first-push-reasons-and-console-fixes

## Charts that no longer take the server down, migrations that run themselves, and a bounded page size

7 October 2026. A week on the platform's own health after an incident on 7 October: the analytics rollup collection had never had an index, and the email history chart formatted twelve million dates per load. All of it measured in production and fixed, with the one-off repairs now running on their own after a deploy.

### Added

- **Self-hosting:** Migrations run themselves after a deploy. The worker runs every registered migration the ledger does not record as succeeded, under a lock so two replicas cannot run the same one, and retries one that failed or was cut off by a restart on the next start. Each run is recorded with its timing, host and outcome in a migrations_applied collection, so "did the index build run on production?" has an answer other than memory. Two repairs from this week, the tenant index build and the empty-rollup prune, are the first entries.
- **Platform:** The API edge speaks HTTP/2 and resumes TLS sessions. Measured from Ahmedabad: a request that does no work cost 270 ms to connect, 280 ms to handshake and 265 ms to answer, 1.08 s cold against 0.26 s on a warm connection, and a console page of twenty calls spent 4.82 s on HTTP/1.1's six connections. Over one HTTP/2 connection those calls multiplex, and a returning client skips the certificate exchange.

### Improved

- **Analytics:** An idle organization no longer writes a rollup row for every empty bucket. One created in September that had done nothing held 668 rollup rows, 666 of them zero, every one rewritten by the ten-minute cron, about 290 database operations per organization per pass for charts that render an absent bucket as zero anyway. Only a small expiring watermark is written now, and the existing zero rows are pruned by migration.
- **Platform:** Every list endpoint bounds its page size. A request for limit=0 went straight to the paginator, which treats zero as no limit, and the endpoint returned the whole collection; limit=100000 did the same. Anything that is not a positive number now becomes the default page, and anything above 500, the largest page any console asks for, is clamped to it.
- **Platform:** A read can decline a model's default joins. Every email history read also loaded the user, contact and audience behind each row, whether the caller wanted them or not. The chart's read of 5,899 rows, which only counts statuses, took 530 ms that way and 119 ms without.
- **Platform:** A health check miss during a busy minute is not a dead replica. The checks do no I/O, so a miss meant the host was too busy to answer inside five seconds, three probes running, which on a box that also runs the database and hourly backups happens; twice on 7 October a healthy replica was restarted for it, and every restart cost users about four seconds of first-byte on a cold process. A replica now has to fail for two minutes before it is restarted, and a fresh one gets a minute to warm up uncounted.
- **Platform:** The load balancer follows replicas through DNS. It resolved the replica address once at startup, so every restart since 25 September left a dead address in its list, and on 7 October four restarts produced 62 user-facing 502s in one minute. The peer list now follows Docker's DNS, a replica is removed after three failures rather than one, and requests round-robin across both replicas instead of pinning a client to one, so a user whose replica just restarted is no longer served every request from the cold one.
- **Self-hosting:** The MongoDB log rotates. Nothing rotated it and the package ships no rule, so production's single log file had reached 29 GB. It rotates daily now, fourteen kept, compressed a day late so yesterday's stays readable.
- **Platform:** Database backups keep two tiers: hourly dumps for two days and a daily dump for thirty, instead of 720 hourly archives. At today's size that is the same protection for a fraction of the storage; at ten thousand organizations it is the difference between 780 GB and 7.2 TB.

### Fixed

- **Analytics:** The analytics rollup collection was created with no indexes, in every organization's database. The upsert that brings it into being used a raw model that builds none, so the query it runs on every pass scanned the whole collection: 47,592 documents examined per upsert, and 97,929 of roughly 98,500 slow queries in the log were this one collection. Sent in a batch, that is what crashed the server during email and campaign analytics. Every raw write that can create a collection now builds its indexes, a test fails if one is added that does not, and existing databases get the build from the migration runner.
- **Analytics:** With the index built, the rollup queries still could not use it. Every soft-deletable model queries with deleted not equal to true, and the unique index is partial on deleted equal to false, which the planner cannot prove from the first; a single-bucket upsert examined 6,104 documents through the wrong index. The rollup queries now name deleted: false, and the same upsert examines one.
- **Email:** The email history chart re-scanned every email for every tracking event. On one organization's last thirty days that was 2,129 events by 5,897 emails, about 12.5 million date formats on the event loop, after loading 65 MB of rendered email bodies the chart never read. The process answered nothing for over a minute, was read as dead and restarted, eleven times on the morning of 7 October, each one a minute of 502s for every user. It is two passes now, each date formatted once, reading only the fields it counts.
- **Platform:** The production database backup never uploaded. The dump worked and then failed to copy, for two bugs that could only show once a bucket was set: a flag that pointed the uploader at the text log as a manifest, and a log line captured as if it were the archive path. Until this week the disk's daily snapshot was the only copy. Verified by a real run into the bucket and by reading the lifecycle rules back.

Source: https://www.buildbase.app/changelog/charts-that-stop-taking-the-server-down

## Invite-only sign-up, a console that loads once, and one subscription per workspace

4 October 2026. Close public sign-up and still let invited people in, get a console that no longer bootstraps twice on every load, and never pay for a second subscription from a double-clicked checkout. The SDK went from 0.0.74 to 0.0.78 across the week.

### Added

- **Authentication:** Invite-only sign-up. An "Allow public sign-up" switch on a new Sign-up tab under Authentication closes every door that creates a user - the hosted form, social sign-in and the monday.com webhook - while someone holding the emailed link of a live invitation addressed to them still gets in. The hosted register page says the organization is invite-only instead of showing a form that would be refused, and the account an invitee creates through the link is marked verified, since the link only ever went to that mailbox. The SDK's own invite screen passes the invitation along from @buildbase/sdk 0.0.75; an earlier SDK still shows the invitee the invite-only notice.
- **Notifications:** Slack posts when an API token is deactivated, reactivated, archived or restored. The event was offered on the Slack settings page and never posted: 55 events to tick, 54 that arrived. A rename or a description edit still sends nothing, and a test now fails if the settings page offers an event with no handler behind it.
- **Website:** The homepage links each supported framework to its setup guide, with React and Node.js pointing at the Vite and Express guides for the searches that use those names. A framework without a published guide drops its tile rather than linking a 404.

### Improved

- **Console:** The console loads once. A provider shifted position when the config answered, so React recreated everything below it on every page load: auth initialised twice, the organization list loaded twice, every shell request fired twice, and a toast raised before the config landed was dropped. A fresh sign-in also rendered the dashboard as logged out for one frame, bounced through the login page and ran the whole bootstrap again. Sign-in now lands on the dashboard in one document load, measured at zero duplicate requests across all 72 dashboard routes. Sidebar icons are bundled rather than fetched from a third-party icon service at runtime, which a self-hosted network may not reach.
- **Console:** Every action says what it is doing. Confirmation dialogs hold their button pending until the handler finishes; archive a workflow, purge the dead-letter queue, cancel a run, make an asset public, unpublish a testimonial and rotate or revoke the export token all ask first; exports show a pending state and a completion toast; a list whose request failed shows the error instead of "Nothing yet". The last 30 raw error toasts are rewritten, and the burn-down list behind that rule is empty.
- **Console:** Switching organization keeps your place on the keyboard. The switch remounts the shell, which destroyed the control that opened the switcher before focus could return to it, so a keyboard user finished every switch at the top of the document with the whole rail to tab through again. Focus is restored to the new switcher, and the control has an accessible name before the organization resolves. The switch itself was measured at zero frames without a shell and no document load.
- **SDK:** useSubscription, useAllQuotaUsage and useCreditBalance share one in-flight request instead of each sending its own copy, and an inline auth prop no longer re-dispatches the whole configuration on every render. From @buildbase/sdk 0.0.76.
- **SDK:** A refused request keeps its HTTP status and the server's error code, so a documented 409 stops reading as an outage; the plan picker offers only the billing intervals your plans actually price; and content webhooks pass a cache-life profile so Next.js 16 stops warning on every tag. From @buildbase/sdk 0.0.78.
- **SDK:** An app whose own session cookie had expired kept authenticating as the previous user: the SDK still sent the stale session id and left it in storage, so the app showed signed out while requests carried the old identity. From @buildbase/sdk 0.0.74 the id is cleared with the cookie. Three public, org-scoped reads that fire before hydration can still carry it, which moves no one's data anywhere; it is reported as its own failing check in the starter's end-to-end suite until it is closed.
- **Webhooks:** One organization's slow receiver no longer holds every delivery slot. The queue was a single line with no notion of whose job was whose, so a receiver that answered slowly could occupy all ten slots while another organization's payment.succeeded waited behind it. At most three deliveries are in flight per organization now; one over the cap is deferred for a few seconds, not dropped. A delivery close to its five-minute signature window is sent rather than deferred, so fairness never manufactures a rejected signature.
- **Platform:** A momentary database stall no longer refuses every organization. In shared-client mode a five-second heartbeat timeout marked the server unknown and every request answered "Tenant database connection not available" until the next heartbeat: a 20 s stall failed 21,371 of 44,226 requests. The same stall after the change fails none, with the slowest request taking the 20 s of the stall.
- **Documentation:** Nine docs described a product we no longer ship. Assets said any file type and named a delete route that does not exist; uploads are five image formats decided by the file's bytes. Collections still warned about two bugs that were fixed. The folder tree route, draft preview, a reporting chart that does not exist, the Slack webhook URL, the service worker push notifications need, archived short links and theming's dark class were each corrected against the shipped build, and the "Auth > Clients" path that outlived its screen is gone from docs and console alike.
- **Documentation:** Seven ways to sign in, not eight. The OAuth 2.0 authorization server was counted as a sign-in method on every page that prints the list and in 25 posts; it is how agents and third-party apps get access, not a way for a person to sign in, and it now has its own line. The RBAC FAQ said new teammates join as editor; they join as viewer.

### Fixed

- **Billing:** Two checkout sessions opened before either completed, a second tab or a second click, were both payable, and the second completion left the first subscription billing in Stripe with nothing pointing at it: two trialing subscriptions on one customer. Opening a checkout now expires the customer's other open sessions, and a completion cancels every other live subscription on that customer, refunding one that had already been charged. Four more billing edge cases are proved end to end: publishing a newer version of a plan moves nobody, a double checkout leaves exactly one subscription and refuses a third, an upgrade on a card that asks for authentication waits on the open invoice, and a promotion code typed at checkout lands on the first invoice.
- **Workspaces:** An invited admin who already had an account landed on an empty console. A customer's team are usually end users of the customer's product too, so the invitee already had a row with the default user role, and the first org switch kept it: one menu item and the no-access page everywhere else, with nothing short of remove-and-re-invite to reach the role again. An invitation now lands on the role it names, custom role or tier, over any existing row, for every tier and custom role; once the membership is recorded the role chosen in the org is authoritative again. The invitation email also named no role when no custom role was chosen; it names the tier.
- **Workspaces:** An invitation naming owner as the role was stored, printed "as owner" in the email, and landed the person on user; it is refused, since ownership moves by transfer. A tier named at the other tier was dropped silently; it is refused with the field to set.
- **Email:** An organization over its send budget could lose mail for good. Deferring an over-budget job cost it a retry attempt, which the comment above the code said it did not, and when the attempts ran out the sender recorded the message as failed and returned, which the queue counts as success: one relay blip while throttled lost a sign-in code with nothing in the failed set. Measured against a real Redis, four deferrals left one real attempt out of five. Both the mail and webhook workers refund the attempt now, and a test fails if a third queue defers without doing the same.
- **Email:** Three workers counted their last attempt one early. Mail got four of its five attempts and the fifth never ran; a campaign was marked failed on attempt two of three; and the webhook delivery log printed every attempt one higher than it was, so a first try read as "attempt 2". Rows written before this keep the old numbering.
- **Audience:** Exporting a filtered audience exported everyone. The button sat above a filtered list and sent no filter, so a list narrowed to 200 people produced a file with all of them. It sends the filter the table is showing and reads "Export filtered" when there is one.
- **Console:** Saving one field in the blog or doc editor discarded the others. Each Save button sends one field, and the response reset the whole form: saving the title threw away an unsaved description, slug and body. Only the field that was sent is folded back in.
- **Authentication:** Rotating a client secret hung the tenant for any client that had tracking settings. The hook that decrypts protected fields walked the document without cycle detection, a nested subdocument points back at its parent, and the walk never ended; the console showed a bare "Network Error". New clients, with no tracking settings, rotated fine.
- **Access control:** Two controls were offered to roles that could not use them: Add users on a user list, to a role with read but no update, and Edit on the auth settings sheet, to a reader. The server refused both writes; what leaked was the offer. Both follow the permission now.
- **Console:** An oversized upload answered 200 with success: false, where every other refusal on the route answers 400. The upload dialog branches on the status, so the spinner never stopped and the message was never seen. It answers 400.
- **Website:** The contact form reported "Message sent" when the enquiry was dropped. Delivery was an unchecked fetch, which does not reject on an HTTP error, so a revoked or rate-limited webhook returned an error and the sender was told it arrived. A failed delivery now answers with the support address, and the failure is logged. The two new error pages also rendered in the browser's default serif; they use the site font.

Source: https://www.buildbase.app/changelog/invite-only-sign-up

## Workspace invitations, a notification inbox, and plans that say what they include

25 September 2026. Invite people to a workspace by email before they have an account, give every member an in-app inbox that updates live with their own notification preferences, and see exactly what each plan includes. It ships in @buildbase/sdk 0.0.71; signOut() revoking the server session shipped in 0.0.70 the same week.

### Added

- **Workspaces:** Invitations. A workspace owner can invite someone by email before that person has an account. The invitee gets an email with a link, sees which workspace they are joining and as what role, and lands in it as a member on accept. The members screen lists pending invitations next to members, with resend and revoke, and an invitation that lapses is announced to the inviter in the inbox and by email. Pending invitations count toward the seat limit, so a workspace cannot invite past what it can hold. From @buildbase/sdk 0.0.71.
- **Notifications:** An in-app inbox. Every notification your app sends a member now also lands in an inbox the SDK renders, updated live over a socket while the page is open, with read, seen and archive. A member who arrives from a push notification finds that item already marked read. From @buildbase/sdk 0.0.71.
- **Notifications:** Per-member preferences. Each member picks, per notification type, whether they want email, push, or neither; the workspace's own settings become the default for members who never chose. Delivery reads the member's choice first, then the workspace default. From @buildbase/sdk 0.0.71.
- **Notifications:** notification.send() with a type you never set up now registers it. The first send of `order_placed` creates the notification type in the console, switched on, where you can rename it, pick its channels and let members manage it. Type names are normalised on the way in (`Order Placed` becomes `order-placed`; dots, underscores and colons are kept), so a send from code and the entry in the console always agree.
- **Billing:** Every plan now states what it includes. The catalog grew from 36 sold items to 163: every feature, limit and quota in the product has a row, each plan carries a value for it, and the plan version editor, the publish comparison and the public pricing endpoint print `Unlimited` and `None` rather than -1 and 0. Existing subscriptions keep the version they bought; a published version only changes what new subscribers get.
- **Billing:** Usage against your plan, in the console. Monthly active users, emails sent, campaigns, storage and the other metered quotas show as a proportion of what the plan includes, on the screen where each one is counted, so a limit is visible before it is reached.
- **Workflows:** Starter templates, on a Templates page in the console. Ten workflows in two tiers: three "Getting started" templates that each show one connection - an event from your app sends an email, an event posts to your backend, a follow-up waits for a click and stops when it comes - and seven ready-made automations: trial ending, payment failed, cancelled win-back, form to webhook, CRM sync, feature flags on a plan change, and an unsubscribe follow-up. Cloning one fills in your default sender and your copy of the email template, and tells you what is still blank before you publish.
- **Authentication:** The hosted sign-in page shows your organization's logo, and its default copy says BuildBase rather than CMS.

### Improved

- **Authentication:** Signing out ends the session on the server. signOut() used to clear the browser's copy and leave the session itself valid until it expired, so a stolen token outlived the sign-out that should have killed it. From @buildbase/sdk 0.0.70 it revokes the session first, and signOut({ everywhere: true }) ends every session the user has.

### Fixed

- **Workspaces:** Adding a member to a workspace that is full answered a bare 402 with no way to tell why. It now answers with the code SEAT_LIMIT_REACHED, the current member count and the limit, whether the seat ran out on a direct add, an invitation, or an accept, and a blocked invitee is refused with a code of its own.
- **Workspaces:** A denied workspace request answered 401, which the SDK read as a lost session and signed the user out. It answers 403 now, so a viewer who opens a screen they may not use stays signed in. A workspace the organization creates for a new user also fires the workspace.created event, which it did not.
- **Authentication:** Social sign-in created an account for a new user even when the organization had public sign-up switched off. It is refused now, with the same message the email form gives.
- **Authentication:** A magic-link budget of five sent four, and when it ran out the sign-in page still said "check your email" while nothing was sent. All five are sent now, and the next request is told the limit is reached - identically for an address with an account and one without, so the refusal reveals nothing about which addresses exist.
- **Authentication:** A slow or unreachable BuildBase control plane was treated as a definite no: it reset an organization's passkeys once, and a console user signing in with Google was asked for consent on every visit. A degraded answer is now a non-answer, cached like one, and the consent prompt appears once.
- **Domains:** A custom domain was marked unverified on its first failed check, which a DNS hiccup could trigger. It takes four consecutive failures now, a domain that recovers is restored on its own, and a domain that Vercel no longer has is recognised as such rather than retried forever.
- **Billing:** A downgrade could take effect before the period the customer had paid for ended. It now holds the paid plan until renewal reliably, ignores stale and out-of-order Stripe webhooks, and no longer processes another organization's events; trial status is reported correctly through the change.
- **Billing:** In the plan version editor a price of $1,000 or more displayed as 0.00, and the pricing preview printed -1 where a limit was unlimited. Both display correctly; no stored price was wrong.
- **Billing:** On a plan that caps how long credits and API keys may live, the console offered "never expires" and the server refused it. The forms now default to the plan's cap and say so.
- **Audience:** CSV import with "update existing contacts" ticked matched the contacts and then updated nothing. Existing contacts take the imported values now.
- **SDK:** A JSON null in a request body arrived at the server as the string "null". It arrives as null; a field typed as text that used to accept the string now answers 400, as it should have.
- **Authentication:** Social sign-in buttons on the hosted pages show their names again. With three providers every label was cut off, and on a phone Google and GitHub both read "G".
- **Self-hosting:** The self-hosted quick start runs as written. The compose files required a Redis password that the environment template and the secret-generating command never created, so the first docker compose up stopped before starting anything.

Source: https://www.buildbase.app/changelog/sign-out-ends-the-session

## Tracking & Tags: your ad and analytics tags, managed from the console

20 September 2026. Add GA4, Google Tag Manager, Google Ads, Meta and a dozen other tags in the console, attach them to an app, and the SDK installs them and reports sign-ups, checkouts and purchases for you - plus the funnel in between. It ships in @buildbase/sdk 0.0.68.

### Added

- **Tracking:** Tracking & Tags, under Settings. Add a tag once - GA4, Google Tag Manager, Google Ads, Meta, TikTok, LinkedIn, X, Reddit, Bing, Clarity, Hotjar, PostHog, Plausible and more - and attach it to the apps that should load it. Your marketing site and your product can carry different tags without either of them naming an id in code.
- **Tracking:** A Connect your app panel on the same screen. Pick an app and it shows the exact code to add - the install line, the provider or the standalone tracker for a marketing site, and the consent call - with your organization and client ids already filled in, which tags will load there, and how to report sales from your servers.
- **Tracking:** Conversions are reported for you. Pass `tracking={{}}` to the SDK provider and sign-ups, logins, checkouts and purchases reach every attached tag, with the ad click the visitor arrived on carried all the way through Stripe. A purchase reports what was actually charged, after any promotion code, with no success page to build.
- **Tracking:** The funnel between sign-up and payment. The plan picker, the settings screens, feature and quota limits and the cancel flow now report each step - who opened the plan picker and closed it, who chose a plan and backed out of Stripe, who keeps hitting a limit - and every event says which workspace and plan it belongs to. These go to your analytics tools, never to an ad network unless you ask.
- **Tracking:** Consent is respected by default. Nothing but consent-aware Google tags loads until your cookie banner answers, and that answer carries over to the hosted sign-in pages. If you already have a lawful basis to measure, you can say so and everything loads immediately.
- **Tracking:** Sales the browser never saw are reported from our servers. A buyer who closes the tab before the return page loads reaches GA4 and Meta directly, matched to the browser event so nothing counts twice. Refunds go to GA4, and renewals are sent once you switch them on. Every send, and every deliberate skip, is listed in the console.
- **Billing:** Check Stripe setup, on the payment credentials screen. One click reads your own Stripe account and tells you, line by line, what is right and what is not: whether your keys work and which mode they are in, whether the webhook endpoint exists, is on, and sends every event we need, whether a second endpoint is sending everything twice, and whether the events Stripe sent actually reached us. Where it can, it fixes the endpoint for you - creating it with the signing secret saved, adding missing events, or replacing duplicates - after showing exactly what will change.

### Fixed

- **Tracking:** A visitor who clicked two different ads was remembered as a mix of both: the first ad's click id with the second ad's campaign, so Google Ads and Google Analytics credited different clicks. Each visit is now remembered whole, and a newer ad click replaces an older one. Fixed in @buildbase/sdk 0.0.68.
- **Tracking:** When a free trial turned into a paying subscription, the first charge was treated like a renewal, so Google Analytics and Meta were never told about the sale unless renewals were switched on. It is now reported as the purchase it is, and the payment.succeeded webhook marks it with trialConverted.
- **Webhooks:** Each payment sent the payment.succeeded webhook twice, because Stripe reports a paid invoice as two events. It is now sent once per invoice, so a backend reporting its own conversions no longer counts every sale twice.
- **Tracking:** On Safari, the step where a visitor leaves for the sign-in pages or for Stripe checkout was recorded but never reached Google Analytics, so those funnels looked like everyone dropped out there. Fixed in @buildbase/sdk 0.0.67.
- **Billing:** When two organizations were connected to the same Stripe account, a payment event could be processed for only one of them, so the other never saw the new subscription. Each organization now processes its own copy.
- **SDK:** Choosing a plan on a pricing page while signed in did nothing; it now opens the plan picker. Pages with a pricing table no longer briefly show "no plans", and paying customers no longer see free-plan content flash before their subscription loads.
- **Billing:** The payment setup page listed 8 Stripe events to subscribe to, and checkout.session.completed was not one of them. An endpoint set up from that list recorded subscriptions but never completed a checkout on our side: no credit-pack credits, no subscription.created webhook, no server-side conversion. The page now lists all 14 events we act on, with what stops working without each one.
- **Workspaces:** New users get their first workspace again in organizations set to create it for them. With workspaces set to be created on sign-up and users not allowed to make their own, a new user was asked the question meant for them and got an empty workspace list instead of the workspace the setting promised.

Source: https://www.buildbase.app/changelog/tracking-and-tags

## Invitations that carry a role

12 September 2026. An invitation can now name the role the person lands on, and it arrives by email instead of waiting to be found. Owners can read what the built-in roles grant, and the last console controls that ignored permissions now respect them.

### Added

- **Access control:** An invitation can name the role the person lands on. Inviting somebody previously offered Member or Admin, and Member grants nothing, so the normal case was to invite a content editor, watch them land on the no-access page, and then go and find the change-role dialog. The invite dialog now lists the organization's own roles.
- **Users:** Invitations are emailed. An invitation was only discoverable by signing in and finding the invitations screen, so the inviter usually ended up messaging the person separately to say it was there. The mail comes from an address we control and can sign for, with the inviter in Reply-To so there is still a human to answer.
- **Access control:** Owners and admins can open the built-in roles and read what they grant. The user role is the one that matters: it is the default for an invitation and grants nothing, so a new member lands on the no-access page everywhere and it looks like the invite failed. Each role now says what it is, read-only.
- **Authentication:** Email sign-up can be switched off. Organization IDs are public by design, so anyone could previously create an account in any organization through its email sign-up endpoint. Set allowPublicSignup to false in the organization settings API and email sign-up is refused, while existing users keep signing in as before. Social sign-in is governed by the providers you enable, and agent sign-up keeps its own switch.
- **Billing:** The pricing page is arranged in the console. What each plan includes now has an order, is grouped into categories and can be highlighted, and a dialog lets you drag the whole page into shape instead of numbering thirty items one at a time. Every pricing page built on the SDK picks up the order, so your best feature no longer loses its place to whichever item was added last.
- **Billing:** Usage-priced items show as figures with their overage rate. A plan that includes 10,000 emails a month now says so as a number, alongside what each email past the allowance costs, and the figure follows the monthly or yearly toggle on screen.
- **Organizations:** Ownership moves by handshake. Transferring an organization used to happen instantly and could only be undone by the person who received it. It is now an offer: nothing changes until they accept it from their invitations screen, you can withdraw it until then, and it expires if nobody answers.

### Fixed

- **Access control:** Creating an auth client now shows its client ID, client secret and organization ID in a dialog you can copy from. The secret only ever exists in that one response - every read of a client masks it to its first and last five characters - so the console was quietly dropping the single copy of it, and a client created in the console could not be configured without deleting it and starting again. The client screen also has a Regenerate button now, for a secret that was lost or leaked: it mints a new one, shows it the same way once, and retires the old one immediately.
- **Console:** Every console write is gated behind the permission it needs. A role with read access could still find create, update and delete controls enabled. The API refused those requests, so nothing was exploitable, but a console full of buttons that answer 401 reads as a broken product rather than a permission you lack. The workflow editor was the worst case: it auto-saved on any canvas interaction, so a viewer nudging a node wrote to the draft.
- **Access control:** Granting, revoking and reconciling a workspace's credits are gated on the permission the server actually enforces, rather than on the screen around them, so the buttons no longer offer something the API refuses.
- **Console:** The roles editor lists only the permissions a role does not already hold. It previously rendered every grantable resource, so on a role holding a lot the two tables were near-identical with every box ticked in both, which reads as a broken screen rather than "there is nothing left to add".
- **Access control:** The owner role states the rule it follows instead of showing a permission matrix. Owner is a bypass, not a set of permissions, so listing its rows implied it was the same thing as admin and that unticking one would limit it. Neither is true.
- **Console:** A control you cannot use no longer shrinks what it wraps. Gated cards and tables collapsed to their content width, so a screen that was merely read-only looked broken, and only for the people who could not use it.
- **Email:** Platform mail is sent from the mail subdomain, which is where the relay signs, so DKIM aligns with the From domain instead of failing alignment. It also keeps transactional and marketing sending reputation apart.

Source: https://www.buildbase.app/changelog/invitations-that-carry-a-role

## Custom roles, link safety, and a billing audit

6 September 2026. Custom roles now work end to end, with the organization's own database deciding what a member may do. Links BuildBase hosts are checked for reputation and can be killed at click time. And a systematic pass over billing fixed six real issues.

### Added

- **Access control:** Custom roles work end to end. The organization's own database is now authoritative for what a member may do, so the role you assign is what the API enforces, rather than the broader membership tier the person signed in with. On a self-hosted install that database is yours, which is the only place the answer can live.
- **Access control:** An audit log for the organization itself, in organization settings: who was invited and at what role, who accepted or declined, who was removed, and when support impersonated the organization. Readable by owners and admins only.
- **Access control:** An append-only security trail inside each organization now records every authorization denial, the full API token lifecycle, workspace membership changes, invitation rejections and revocations, secret rotations, and admin-API actions.
- **Security:** Links BuildBase hosts on your behalf are checked before a click goes through. A destination on the trusted list redirects straight away; anything else gets a reputation check and an interstitial that navigates itself once the verdict comes back safe.
- **Security:** Kill switches for hosted links. A single destination, or the tracking code covering every link in one sent message, can be blocked and refused at click time. That includes mail already sitting in an inbox: the message cannot be recalled, but the redirect can be refused.
- **Security:** A malicious verdict blocks the destination and disables the message carrying it, rather than warning only the one reader who happened to click. Both are audited, and the operator alert carries a one-click reversal, because false positives are certain.

### Improved

- **Console:** The console decides "may I do this" in one place instead of four, evaluating in the same order the server does, so the buttons and the API agree. A control you lack permission for is disabled with the reason on hover rather than hidden, because a control that vanishes cannot tell you what to ask for.

### Fixed

- **Access control:** A Slack incoming-webhook URL is a bearer credential: anyone holding it can post into the organization's channel. Any authenticated member could read it, whatever their permissions. The route now carries the guard it was missing.
- **Access control:** Revoking a permission could keep working for up to 60 seconds on any instance that had already cached it, including the one that made the change, so an admin who removed a permission watched the old one keep working. A change now reaches every instance immediately.
- **Console:** Screens and controls that reached data they did not gate on now check the permission they actually need, so a role with read access no longer sees write controls that answer 401.
- **Access control:** The roles editor no longer offers permissions the API rejects, and the audit screen resolves who did what instead of showing raw identifiers and truncated rows.
- **Email:** Phone, SMS and in-message anchor links keep working in tracked mail. A scheme allowlist added alongside click-time blocking had turned tel:, sms: and relative links into a blocked page, including in mail that had already been delivered and previously worked.
- **Email:** Open and click tracking links are signed with their own key rather than the one used for sign-in sessions. Existing links keep working, because verification falls back to the old key, which matters when a tracked link stays valid for a year.
- **Short links:** Archiving or deleting a short link actually stops the redirect, and a destination is validated when it is saved, so a javascript: or data: URL can no longer be stored and later emitted in a redirect.
- **Authentication:** Cloud-hosted auth domains serve the full security header set. The auth UI is a static export, so the headers configured for the self-hosted container were never served by the cloud deployment, which is the surface where custom auth domains are attached.
- **Billing:** Webhook events for a failed payment, a payment needing extra verification, and a successful payment could be silently dropped depending on which Stripe API version sent them - so the dunning emails and the usage reset after payment did not always run.
- **Billing:** Canceling a subscription could report the pre-cancellation state back for a few seconds right after the cancel succeeded, so a page that refetches on success looked like nothing had happened.
- **Billing:** Hitting a seat or trial limit returned a generic server error instead of a clear response an app could detect and use to prompt an upgrade.
- **Billing:** A workspace on the free plan could get stuck there and never be able to upgrade to a paid one.
- **Billing:** Rapid concurrent checkouts could create more than one Stripe customer for the same workspace, and a subscription on the extra one could go unnoticed by our duplicate-subscription checks.
- **Billing:** Checkout did not always prefill the buyer's own account email, so a trial could be started under a different address than the one on file.

Source: https://www.buildbase.app/changelog/billing-audit-fixes

## Badges for your app, and billing exemptions

29 August 2026. Any app built on BuildBase can now show a "Built with BuildBase" badge, an organization exempt from billing says so instead of looking unsubscribed, and the console picks up a round of fixes.

### Added

- **Website:** Embeddable "Built with BuildBase" badges. Three designs, four themes and three sizes, copy-paste ready as HTML, Markdown, React, a plain URL or a PNG for email, from the new page at /badges. The badge is an image, so it works on a Webflow or Framer site, a WordPress footer or a README with nothing installed - the auto theme follows the reader's system setting on its own. No plan requires one and nothing checks for it.
- **Console:** A product panel on the landing route, so the console opens on something useful rather than an empty shell.
- **Billing:** Organizations can be exempt from billing. An exempt organization shows a "Billing exempt" chip in the org picker and on its billing page, with the plan row reading "Not required" - rather than looking like one that has not subscribed yet.
- **Console:** Creating a cloud-hosted organization switches you straight into it, instead of leaving you at the picker to click the org you just named.
- **Console:** Any organization's setup guide can be opened straight from the admin panel.
- **Console:** The rail's footer icons now live in the user menu, so the account controls sit in one place instead of two.

### Fixed

- **Billing:** The billing page no longer crashes when BuildBase is not configured - a self-hosted install gets a clear "Billing is not available" card instead of an error page.
- **Billing:** The entry paywall read the subscription with the wrong identifier, so someone who had just paid sat on the paywall instead of being walked into their organization automatically.
- **Billing:** An exempt organization no longer sees warnings about losing access - a block that cannot happen to it.
- **Console:** The theme toggle works again and cycles in place, back on the rail where it was.
- **Console:** The user menu no longer sticks, and a non-modal sheet stays open when you use a dropdown inside it.
- **Console:** The account entries moved out of organization settings and into the avatar menu, where people look for them.
- **Console:** The SDK portal host no longer reserves a viewport of empty space on pages that do not use it.
- **Users:** Dialogs and sheets all carry an accessible name, so a screen reader announces what just opened.
- **Audience:** Every widget on the page refreshes after a write - the stat cards included - instead of only the totals.
- **Email:** The template filter applies to the history table and the charts, not just the list, and the table reloads after you create, update or send.
- **Workflows:** Workflow execution limits are accepted and saved, including the per-minute trigger cap that was being dropped.
- **Platform:** Generated installation keys stay inside their dialog instead of escaping the layout.

Source: https://www.buildbase.app/changelog/billing-exemptions

## A setup guide that verifies itself

23 August 2026. Get Started rebuilt as a six-phase flow whose steps are proven from live data, live chat support in the console, and a subscription gate that holds server-side.

### Added

- **Console:** Get Started rebuilt as a six-phase setup flow - 22 steps in real dependency order, with a floating progress guide that follows you across the dashboard.
- **Console:** Fourteen setup steps verify themselves against live tenant data and show their evidence; steps with no reliable signal stay manually tickable rather than showing a tick nobody earned.
- **Console:** Every setup step links the documentation page, build guide or starter repository that helps finish it.
- **Console:** Live chat support in the console. Cloud only - a self-hosted install never ships the widget, and a read-only support session cannot write into a customer's conversation.
- **Billing:** A subscription gate for cloud organizations: a lapsed plan now blocks the console and revokes tenant API access server-side. It fails open during an outage on our side, so a paying customer is never locked out by our downtime, and every degraded decision is logged for alerting.
- **Website:** An affiliate program. Tracking is consent-gated and never ships in self-hosted installs.

### Improved

- **Billing:** Entitlement decisions are cached in Redis rather than per process, so revoking access takes effect across every instance at once.

### Fixed

- **Billing:** A brand-new organization whose provisioning failed was let in free under the fail-open rule. An organization that has never subscribed now blocks instead - there is no paying customer to protect.
- **Billing:** Support impersonation is exempt from the subscription gate everywhere, so a support session is never paywalled out of the unpaid organization it was sent in to look at.
- **Console:** Every create dialog now runs the same validation as its edit form, and the server enforces the same rules, so a record created through one path can always be saved through the other.
- **Users:** Number and boolean user attributes save again - values were coerced to strings before validation, so a typed default could never pass its own type check.
- **Console:** Table filters: dropdowns work inside dialogs, saved filter values survive editing, and a smart list's filters can be updated on their own.
- **Platform:** Setting workspace creation or member invites to Disabled now enforces - the flags were stored as strings, which the boolean guard never matched.

Source: https://www.buildbase.app/changelog/verified-setup-and-subscription-gate

## Documentation for every module

16 August 2026. All 19 modules are now documented, and writing the docs surfaced four bugs worth fixing.

### Added

- **Documentation:** Every one of the 19 modules now has documentation. Email campaigns, workflows, forms, notifications, collections, content, short links, assets and audience management were previously undocumented.
- **Documentation:** A reference for the admin REST API - token format, error shapes, rate limits, and the list-query parameters every collection endpoint shares.
- **Authentication:** Redirect URLs accept wildcards, so preview deployments no longer need a new client per branch.
- **Authentication:** Open signup, with self-serve accounts placed in one shared organization.

### Improved

- **Platform:** New organizations no longer create empty collections up front, and indexes are built as collections appear.

### Fixed

- **Forms:** Boolean fields on public forms are validated again. A type-name mismatch meant any value at all was accepted and stored.
- **Workflows:** Workflow endpoints are permission-controlled, split across eight resources so runs, definitions, versions, logs and the trigger queue are granted separately. A support role can read runs without seeing the automations behind them. Previously any valid token reached all of it.
- **Workflows:** Resuming a paused scope resumes every instance in it. Past the first 1,000, instances were marked running without being re-queued and quietly stopped.
- **Security:** Listing API tokens returns a masked preview instead of the full secret. The complete value is shown once, when the token is created.

Source: https://www.buildbase.app/changelog/documentation-for-every-module

## Device-aware sessions and trusted devices

16 July 2026. Sessions now know which device they belong to, with a trusted-device flow and configurable security emails.

### Added

- **Authentication:** Sessions are bound to a device, so a person can see where they are signed in and sign out one device without ending every session.
- **Authentication:** A trusted-device flow, with an organization-level toggle for whether to offer it.
- **Authentication:** Configurable notification emails for authentication events, so you decide which ones reach your users.

### Improved

- **Authentication:** Social login and password login now follow one unified path, with the handoff after a social callback hardened.

### Fixed

- **Authentication:** Cache leaks in the session layer, found while consolidating the login flows.

Source: https://www.buildbase.app/changelog/device-aware-sessions

## Agents can register themselves

11 July 2026. Dynamic Client Registration (RFC 7591) lets an AI agent become an OAuth client without a human provisioning one.

### Added

- **Authentication:** Dynamic Client Registration (RFC 7591), so an agent can register itself as a client instead of waiting on someone to create one by hand.
- **Authentication:** Per-user agent sessions, so an agent acts as the person who authorized it rather than as a shared identity.
- **Authentication:** Scopes and app-minted tokens, giving you control over what an agent is allowed to reach.
- **Console:** An audit trail for client lifecycle events, recording which registrant created each client.

### Improved

- **Authentication:** Redirect URI and PKCE handling hardened, and duplicate OAuth2 clients de-duplicated.

Source: https://www.buildbase.app/changelog/dynamic-client-registration

## Passkeys and PKCE

4 July 2026. WebAuthn passkey sign-in with progressive enrollment, plus PKCE support with a per-client requirement flag.

### Added

- **Authentication:** Passkey sign-in with WebAuthn, including progressive enrollment so existing accounts can add one without a migration.
- **Authentication:** Passkeys are labelled with the app domain, so someone who belongs to several organizations can tell theirs apart.
- **Authentication:** PKCE (RFC 7636), with a per-client flag to require it.
- **Billing:** A pricing page driven by live plan data, with plan categories and FAQs, rather than hard-coded tiers.

Source: https://www.buildbase.app/changelog/passkeys-and-pkce

## Making the platform legible to AI agents

27 June 2026. Agent skills discovery, OAuth metadata, signed bot authentication, and markdown content negotiation.

### Added

- **Agents:** An agent skills index, so an agent can discover what your BuildBase app can do without being told.
- **Agents:** A Web Bot Auth key directory for HTTP message signatures, letting well-behaved bots identify themselves cryptographically.
- **Documentation:** Content negotiation on the docs site: request a page with `Accept: text/markdown` and get markdown instead of HTML.
- **Website:** A robots.txt route carrying AIPREF content signals, stating how the content may be used for training.

### Improved

- **Analytics:** Chart endpoints gained richer filtering, and email history charts were made faster.

Source: https://www.buildbase.app/changelog/built-for-ai-agents

## Self-hosted deployment

19 June 2026. Docker images for the central and tenant servers, a setup wizard, and request hardening across the API.

### Added

- **Self-hosted:** Dockerfiles for the central and tenant servers, with deployment workflows and shared configuration templates.
- **Self-hosted:** An organization setup wizard for configuring a self-hosted install.
- **Console:** More chart types - donut, funnel, heatmap, radar, radial and treemap.

### Fixed

- **Security:** Protection against NoSQL injection on request payloads, and stricter CORS handling.

Source: https://www.buildbase.app/changelog/self-hosted-deployment

## Multi-instance scaling, and the docs site

13 June 2026. Shared state moved to Redis so the platform runs on several instances, and docs.buildbase.app went live.

### Added

- **Documentation:** docs.buildbase.app, statically exported with full-text search.
- **Console:** User impersonation for support, restricted to read-only - any request that would change data is rejected.
- **Console:** A super admin panel with per-collection backup import.
- **Self-hosted:** Organization hosting modes, so an organization can run against its own infrastructure.

### Improved

- **Platform:** In-memory caches replaced with Redis, so several application instances stay consistent with each other.
- **Platform:** Analytics and chart queries rewritten as database aggregations instead of in-process work.
- **Platform:** Background jobs reorganized into a fan-out queue architecture, with duplicate queries removed.

Source: https://www.buildbase.app/changelog/multi-instance-scaling

## Fifty more workflow triggers

5 June 2026. The workflow builder gained six actions and unhid fifty triggers, grouped by category.

### Added

- **Workflows:** Six new workflow actions, fifty additional triggers, and a category-grouped picker so the catalog is navigable.
- **Notifications:** A wider system-event catalog, with Slack alerts and email notifications wired to it.
- **Console:** Settings reorganized into sections, with a reworked sidebar and the pages that were missing from it.

Source: https://www.buildbase.app/changelog/fifty-more-workflow-triggers

## A shared component library

30 May 2026. UI components centralized into one package, with a navigation and accessibility pass across every screen.

### Added

- **Console:** UI components centralized into a shared package, so every screen draws from one set.
- **Authentication:** Cross-organization domain uniqueness, with a cached auth domain resolver and automatic cleanup.

### Improved

- **Console:** Navigation sidebar, rail icons and accessibility reworked across the console.
- **Authentication:** Auth flow security hardened and magic link handling made clearer.

Source: https://www.buildbase.app/changelog/shared-component-library

## Smart lists and a system event catalog

20 May 2026. Audience lists that filter on email activity and membership, plus a centralized catalog of system events.

### Added

- **Audience:** Smart lists resolve their members from filters rather than a fixed set - filter on email activity (opened, clicked, campaign, template, delivery status), list membership, or any native audience field, combined with AND.
- **Audience:** A preview endpoint, so you can see who a smart list matches before saving it, and edit the filters on an existing list afterwards.
- **Notifications:** System events for audience, email, push and forms, with the event enums centralized in one place.
- **Security:** Production startup now refuses to boot without JWT and OAuth2 secrets set, rather than falling back to defaults.

Source: https://www.buildbase.app/changelog/smart-lists-and-system-events

## Slack notifications

6 May 2026. Real-time Slack alerts for signups, workspaces and subscriptions, plus a 223-test authentication suite.

### Added

- **Notifications:** Slack alerts for user registration, workspace creation and subscription changes, configurable per event.
- **Email:** Email senders can be shared with other administrators rather than being locked to their creator.
- **Platform:** A 223-test authentication suite, which caught several crashes on the way in.

### Improved

- **Audience:** Audience list membership moved to a mapping collection, so large lists stay fast.

Source: https://www.buildbase.app/changelog/slack-notifications-and-monorepo

## Audience import and tagging

30 April 2026. CSV import with column mapping, audience tags, and automatic syncing from user lifecycle events.

### Added

- **Audience:** CSV import, with a column-mapping step and duplicate handling before anything is written.
- **Audience:** Tag management, wired through to email campaigns so a tag can drive who receives one.
- **Audience:** Automatic syncing from user lifecycle events, so signing up adds someone to your audience.
- **Email:** Sending from either a template or custom content.

Source: https://www.buildbase.app/changelog/audience-import-and-tagging

## Webhooks and freemium plans

21 April 2026. A webhook system with enriched payloads and signature verification, and support for freemium plans.

### Added

- **Webhooks:** A webhook system built on a central event emitter, with enriched payloads and an admin interface for managing endpoints.
- **Webhooks:** A signature verification guide, so you can confirm a delivery came from BuildBase.
- **Billing:** Freemium plan support across subscription management, including trial details on the plans response.

Source: https://www.buildbase.app/changelog/webhooks-and-freemium-plans

## Multi-currency billing and failed payments

7 February 2026. Plans priced in several currencies, a currency locked per workspace, and dunning when a payment fails.

### Added

- **Billing:** Plan versions can be priced in several currencies, with the plans a workspace sees filtered to its own.
- **Billing:** A workspace locks to one billing currency when it first subscribes, so pricing cannot change underneath an existing subscription.
- **Billing:** Handling for Stripe invoice.payment_failed - the local subscription status is updated, the event is processed idempotently, and a notification is queued when the customer needs to act.
- **Billing:** Overage billing with a configurable unit size, so metered usage can be charged in blocks rather than per unit.

### Fixed

- **Billing:** Quota resets now run correctly at the start of a billing period.
- **Billing:** Cancelling a subscription in Stripe is reflected locally instead of leaving a stale record.

Source: https://www.buildbase.app/changelog/multi-currency-billing

## Checkout, invoices, and per-workspace Stripe customers

22 January 2026. Stripe Checkout for new subscriptions and upgrades, with invoice history on the workspace.

### Added

- **Billing:** Stripe Checkout sessions for new subscriptions and for upgrading an existing one.
- **Billing:** Each workspace gets its own Stripe customer, with a duplication check so a retry cannot create a second one.
- **Billing:** Invoice history, exposed through an API and shown on the workspace.

Source: https://www.buildbase.app/changelog/checkout-and-invoices

## Workspace plans and quota limits

16 January 2026. Quota and limit calculation per workspace, with plan history kept as a log.

### Added

- **Billing:** Quota and limit calculation at the workspace level, so entitlements follow the plan a workspace is actually on.
- **Billing:** A workspace now shows its current plan and subscription state.
- **Billing:** Plan changes are recorded as history rather than overwriting the previous value.

Source: https://www.buildbase.app/changelog/workspace-plans-and-quotas

## Plan groups and pricing versions

10 January 2026. Plans became versioned, so changing pricing no longer rewrites what existing subscribers are on.

### Added

- **Billing:** Plans are organized into groups with versioned pricing, so publishing new prices leaves existing subscriptions on the version they signed up to.
- **Billing:** Subscription items and categories, and Stripe credentials and webhooks configurable per organization.
- **Audience:** Date-typed attributes with matching filters, and a record of how an attribute changed over time.

Source: https://www.buildbase.app/changelog/plan-groups-and-pricing-versions

## User attributes

1 January 2026. Custom attributes on users, editable from the console and from the SDK, and filterable in the user table.

### Added

- **Users:** Custom attributes on a user, created and updated from the console.
- **Users:** Attribute updates from the SDK, so an application can record what it knows about someone.
- **Console:** The user table filters on attributes, and a user page shows the workspaces they belong to.
- **Email:** A test send button on the template editor.

### Improved

- **Platform:** Indexes added to the models behind the slowest queries.

Source: https://www.buildbase.app/changelog/user-attributes

## Sending email from a template, and settings APIs

27 December 2025. Send directly from the template editor with merge tags visible, plus organization and workspace settings APIs.

### Added

- **Email:** Send an email straight from the template page, with the available merge tags shown in the send dialog.
- **Platform:** Organization and workspace settings APIs, with the auth screen configuration cached.

### Fixed

- **Authentication:** A blocked account now gets a clear error instead of a generic failure.
- **Security:** Server-side auth data is passed by reference rather than as a token in the URL.

Source: https://www.buildbase.app/changelog/email-sending-and-settings-apis

## Users on a map

19 April 2025. Country, language and timezone captured for every user, with a world map and per-country counts on the dashboard.

### Added

- **Audience:** Country, language and timezone are saved against a user and applied automatically in the background, rather than asked for.
- **Console:** A world map on the dashboard, with user counts by country.
- **Console:** Country and language as sortable columns and filter dropdowns on the user table.

Source: https://www.buildbase.app/changelog/users-on-a-map

## Device and location on every activity

10 April 2025. User activity records now carry resolved IP information - location, browser and device - with charts over the result.

### Added

- **Audience:** User activity records carry resolved IP information, so an event shows where it came from and on what.
- **Console:** Browser and device detail surfaced alongside activity, with the agent information laid out readably.
- **Console:** Composite charts over user list changes, so growth is visible rather than inferred.

Source: https://www.buildbase.app/changelog/device-and-location-on-activity

## Login screens configured from the console

26 July 2024. The hosted login screen takes its configuration and branding from the console, with magic link sign-in completed.

### Added

- **Authentication:** The login screen renders from configuration set in the console, so branding and enabled methods change without a deploy.
- **Authentication:** Authentication methods are attached to an auth setting, with redirect URLs editable in the interface.
- **Authentication:** Magic link sign-in, end to end.

Source: https://www.buildbase.app/changelog/login-screens-from-the-console

## Redis, background queues, and short links

10 December 2023. Caching and a job queue moved onto Redis and BullMQ, and short links arrived.

### Added

- **Platform:** Redis for caching and BullMQ for background jobs, which is what let slow work move off the request path.
- **Short links:** Short link management.
- **Email:** Email templates provisioned automatically at server start, rather than seeded by hand.

Source: https://www.buildbase.app/changelog/redis-queues-and-short-links

## Feature flags, campaigns, and encryption at rest

2 December 2023. The first feature flag system, email campaigns with open tracking, and field-level encryption in the data layer.

### Added

- **Feature flags:** The first feature flag system, so functionality could be turned on per customer without a deploy.
- **Email:** Email campaigns carrying their own design and HTML, with open tracking on delivered mail.
- **Users:** Blocking and unblocking accounts, user tags, and a picker that excludes people already added.
- **Security:** Field-level encryption in the model layer, so sensitive values are encrypted before they reach the database.
- **Security:** HTML sanitization on rich content, including nested fields.

Source: https://www.buildbase.app/changelog/feature-flags-and-email-campaigns

## Before April 2026

Entries reach back to the first working version in November 2023. They are not evenly spaced, because development has not been: ten of the twenty-five months before December 2025 have no commits at all, including an unbroken stretch from June to November 2025. Rather than pad those periods, they are simply absent - a changelog records what happened, not what a calendar expects.
