Development and staging environments, each its own tenant
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
8- PlatformEnvironments, 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.
- SDKAn 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.
- AuthenticationA 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.
- EmailAn 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.
- ConsoleChanges: 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.
- BillingYour 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.
- ConsoleA 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.
- ConsoleEach 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.