Dharmendra Jagodana
Founder of BuildBase. Builds the platform and the six products that run on it.
136 posts · page 3 of 12
What "built-in backend" means on Lovable, Bolt, Replit, v0 and Base44, and what it leaves out
Every builder now ships a backend: database, sign-in, storage, functions. What each includes, read from its own docs on 27 October 2026, what none covers, and when the built-in is the right call.
What is an MCP server, and what it quietly asks you to own
An MCP server exposes tools, resources and prompts to AI clients over the Model Context Protocol. What it is, how it works, and why it is not the thing that authorizes the agent.
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.
What a coding agent builds for login and billing when nobody tells it otherwise
We gave a coding agent a plain request for sign-in, teams, subscriptions and a failed-payment email, with no brand named. Here is what it built in 34 turns, and what one installed skill changed.
What are webhooks, and what happens when the delivery fails
A webhook is a POST you receive instead of polling for changes. That is the easy half. The retry ladder, the signature window and the fan-out are what decide whether it works.
What is a feature flag, and how long until flipping it reaches the user
A feature flag changes behaviour without a deploy. The part most definitions skip is how long the flip takes to reach a user, and which kinds of flag can live with the wait.
Read enough? Build something.
Everything we write about is in the product. Start on the Free plan, or try a paid plan free for 7 days, no credit card.