Everything new in October, one line per feature
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
20- EnterpriseThe 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.
- EnterpriseA 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-inYour 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-inPeople 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.
- BillingYou 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.
- BillingYou 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-onsYou 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.
- CouponsYou 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.
- StripeCustomers 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.
- CreditsCredit 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 versionsYou 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.
- BillingA 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.
- EntitlementsYour 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.
- EnvironmentsYou 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.
- TrackingThe 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.
- AgentsMCP 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.
- EmailCampaigns 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.
- ConsoleYou 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.
- AuthenticationHosted 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.