Build guides
Step-by-step walkthroughs for shipping real features with @buildbase/sdk.
63 posts · page 1 of 6
How to add enterprise SSO to your SaaS through your own WorkOS account
Enterprise SSO and SCIM for a B2B SaaS, in order: your WorkOS keys, the IT admin setup link, verified domains, required SSO, workspace bindings and the in-app screen.
Credits and usage limits for an AI app you built with a prompt
An AI feature needs a balance someone can spend down and a hard stop when it is gone. What the agent builds instead is a number in a column. Here is the shape that holds, and the prompts that get it.
Add login, teams and paid plans to a Bolt.new app, and keep Bolt Cloud or Supabase for your data
Bolt runs Node in your browser tab, so the three sign-in routes answer inside the preview. Where the live copy of them runs is the one decision this guide is built around. Read on 27 October 2026.
Add login, teams and paid plans to a Replit Agent app, and keep Replit's database for your data
A Replit project is a real Linux workspace with a shell, so the SDK installs like anywhere else. The three sign-in routes go on the Express server Agent already wrote; we ran them on 27 October 2026.
Emails that arrive: confirmation, reset and welcome emails for an AI-built app
The confirmation email worked for you and never reaches a stranger, because the sender is for development. Find the sender, put your domain behind it, and make the lifecycle emails run on their own.
Add login, teams and paid plans to a Lovable app, and keep Lovable Cloud or Supabase for your data
New Lovable apps are TanStack Start apps, which means they can hold the three server routes BuildBase sign-in needs. Built and typechecked on 27 October 2026, with the Supabase wrinkle stated plainly.
Add sign-in, teams and paid plans to a v0 app without leaving Next.js
A v0 app is a Next.js app, which is the easiest place to add BuildBase: one prompt or one init command, five variables in Vercel, one redirect address, then teams, plans and the failed-payment email.
Login that works after you publish: the live-site checklist for a vibe-coded app
Sign-in works in the preview and loops, lands on localhost or hangs on the live site. Six checks, in the order a stranger hits them, with the exact error strings and the setting behind each one.
Paid plans that actually gate features: plans, trials, limits and seats for a vibe-coded app
Every builder takes the money. The hard half is after: the plan has to change what the app does, and nobody may mark themselves paid. Each step with a prompt, from the webhook to the server gate.
Teams, invites and admin vs member for an app you built with a prompt
No builder ships teams for your end users. Give every customer their own workspace, let them invite colleagues by email, and make admin vs member a rule the server enforces, not a hidden button.
The vibe coder's launch checklist: 20 things between a demo and a product
Your AI-built app works for you. Before strangers use it, twenty things have to be true that a demo never tests: login that holds up live, teams, plans that gate access, emails that arrive.
Vibe coding with Claude Code or Cursor: one skill, then sign-in, teams and billing
In a coding agent the SDK installs in your own repo, so the whole job is making the agent know it exists. One skill line, one init command, one prompt, and what to check in the diff it hands back.
Follow a guide with your own project
Every guide starts with one install. Create a project and build along.