Choosing a Tech Stack for a Content Site, Tool Site and SaaS

Three layers, three speeds

A content site needs publishing speed. A tool site needs client-side performance. A SaaS needs state, auth and billing. Choosing one architecture for all three usually means overbuilding two of them.

Content site

Static generation or a light CMS, good typography, fast search and an RSS feed. The database only stores posts, categories and series.

Tool site

Client-side processing where possible - images, converters and generators can run in the browser and cost zero server time.

SaaS

Auth, tenancy, payments and a background job queue. Only start this layer when users ask for accounts.

Decision rule

Pick the layer that matches your current revenue signal, not the layer you want to build next quarter.