A deep dive on how I approached secrets management early in a multi-tenant, GPT-integrated, production system and what I learned the hard way.
A deep, practical introduction to multi-tenancy, common architectures, and the real-world pitfalls when adding it to existing systems.
A deep dive into how I used C4 modeling to clarify a multi-store ecommerce SaaS where one user can run unlimited niche stores.
A deep dive into how I used C4 modeling to clarify a multi-store ecommerce SaaS where one user can run unlimited niche stores.
How I built a single Vercel-hosted API that serves many Custom GPTs via OpenAPI, with strict tenant isolation and safe action execution into warehouses/lakes.
Reflections on designing a system where each tenant connects their own Stripe account—and what that unlocks (and complicates) compared to platform-owned payments.
Standing up a lightweight commerce layer with Firestore, Stripe, and an admin that doesn’t feel heavy.
Foundational notes on how to structure multi-tenant data when HubSpot is part of the stack, including where HubSpot fits as system-of-record and where external persistence is needed.
How factory patterns keep tenant-specific logic clean, pluggable, and safe—plus practical patterns you can drop into our stack.
My approach to building signup/auth, where data lives, and how security fits—kept intentionally stack-agnostic until the problem is clear.
Hands-on exploration to design and prototype a customizable iPaaS with connectors, triggers, actions, a workflow engine, secure auth vault, and multi-tenant isolation.
Principles and decisions for running a multi-tenant Integration Platform (IPaaS) with Model Context Protocol (MCP) agents/tools. No code—just the hard choices.
How tenants can bring their own Stripe accounts/keys, why we’d do it, and the practical architecture for our booking platform.
Notes from exploring how services, rentals, and forms attach to tenants in the booking platform.
A simple explanation of tenants, scoping, and why sometimes we split big tenants into their own databases.
An easy-to-grasp explanation of multi-tenancy for people new to software — with examples, analogies, and why it matters.
How business and compliance tangles around payments distract me from building value—and why Bring Your Own Keys (BYOK) is the cleanest way to get back to software.
How I’ve approached multi-tenancy repeatedly in Next.js and why the pattern keeps proving itself useful.