Dharmendra Jagodana
Founder of BuildBase. Builds the platform and the six products that run on it.
129 posts · page 5 of 11
Stale data on screen after a workspace switch
Stale data after a workspace switch is a cache that never learned the workspace changed. One switch with the Network tab open tells you which cache. The fix is a key, not a purge.
How to add team invitations in Next.js, and decide when the seat starts billing
Team invitations in Next.js: a pending invite holds a seat from the moment it is sent. Why that is the right default, and what it does to the invoice at renewal.
Transactional email landing in spam
Transactional email in spam is a verdict the receiving server already wrote into the header. How to read it, and five causes to check in the order that settles fastest.
Usage counts that do not match the invoice
Usage does not match the invoice? The invoice bills overage blocks for a period that already closed. How to reconcile the two, fastest check first.
What are entitlements in SaaS, and what a plan change does to each kind
In SaaS, an entitlement is what a customer's plan lets them do: a feature, a limit, a quota or a credit grant. The four look alike until the plan changes.
What is multi-tenancy, and why the tenant is whoever pays
Multi-tenancy is one app serving many customers with their data kept apart. The decision that costs you later is which object in your schema is the tenant.
What is RBAC, and where it leaks in a B2B SaaS app
RBAC grants permissions to roles and roles to people. In a B2B app the role sits on the workspace membership, and the leaks are in the defaults, not the matrix.
Why a permission change no longer waits for the hourly refresh
RBAC permission propagation delay, from our code: role and grant changes land at the write, and the hourly refresh only catches writes that announce nothing.
Multi-tenant workspaces in Express, Hono and Fastify: one middleware that checks membership
Multi-tenant workspaces in Express, Hono and Fastify: take the workspace from the path, then refuse any user who is not a member, in one middleware.
Multi-tenant Remix: put the workspace in the URL, and check membership before any loader runs
Multi-tenant workspaces in Remix and React Router v7 or v8: the workspace lives in the URL, and one membership check runs before any loader can fetch.
Usage-based billing in React Router (Remix): meter in the action, never the loader
Usage-based billing in React Router (Remix): record usage in the action, not the loader, and key each form render so a retried submit bills once.
Usage metering middleware in Express: record before the handler or after the response (Hono and Fastify too)
Usage metering middleware for Express, Hono and Fastify: when to record before the handler, when to batch after the response, and the rate limit that decides it.
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.