Blog
Product updates, guides, and ideas for teams building with clarity.
More from the blog
Why I Chose a Node.js Monorepo Over Next.js for a TypeScript SaaS Boilerplate Why I Chose a Node.js Monorepo Over Next.js for a TypeScript SaaS Boilerplate
Most SaaS founders default to Next.js, but the real architectural decision isn't the framework—it's the product shape. Here's how to recognize when a split Node.js backend pays for itself before technical debt compounds.
Apollo GraphQL SaaS Boilerplate 2026: The Actual Shortlist Apollo GraphQL SaaS Boilerplate 2026: The Actual Shortlist
Most "best SaaS boilerplate" lists are Next.js-first by default, not by merit. Here's an honest audit of what Apollo GraphQL TypeScript starters actually offer in 2026, and how to test maintenance health before you fork one.
Pluggable AI tooling: three providers, one contract Pluggable AI tooling: three providers, one contract
Importing an AI SDK directly into product code feels fast until providers, models, and pricing inevitably change. A small abstraction layer keeps infrastructure isolated so swapping vendors becomes configuration instead of a refactor.
The Stack Behind Refract: Express, GraphQL, React, Astro — and Why The Stack Behind Refract: Express, GraphQL, React, Astro — and Why
Every boilerplate makes architectural bets, most of them implicit. Here's the honest reasoning behind every stack choice in Refract, from Express and GraphQL to Sequelize and the queue adapters, including which decisions are personal preference rather than objective necessity.
The hidden revenue tax of vendor-coupled SaaS architecture The hidden revenue tax of vendor-coupled SaaS architecture
Vendor coupling isn't just a technical detail, it's a recurring revenue cost. Here's why billing, entitlements, and RBAC break first when provider logic leaks into your domain, and how explicit boundaries turn emergency rewrites into planned maintenance.
Interface-First SaaS. How to Swap Infrastructure Without Rewriting Product Logic Interface-First SaaS. How to Swap Infrastructure Without Rewriting Product Logic
Direct vendor SDK calls feel fast until a provider changes terms and the fix spreads across your codebase. Here's how interface-first architecture keeps billing, RBAC, and delivery paths stable by isolating volatile dependencies behind adapters.