Stack we do not use.
And why.
Every framework solves a problem. Most marketing sites do not have that problem. Here is what we reject and why.
Next.js for static marketing sites
A 12-page brand site does not need server-side rendering, edge functions, or React hydration. Astro builds a faster site in a fraction of the JavaScript. We use Next where there is genuine app logic, not because it has the trendier docs.
Webflow on critical paths
Drag-and-drop is fine for landing pages. We will not use it for ecommerce checkouts, login flows, or anything a real customer transaction touches. The "no-code" tax shows up the moment you need a custom integration.
Headless WordPress for content sites
Pairing WordPress with Next.js + Vercel for a marketing site doubles the moving parts and the hosting bill. If the editor is the WP admin, the renderer should be WP too. We use headless only when there is a genuine reason for a separate frontend stack.
LLM-everywhere
Claude and Gemini are tools, not a religion. We will not pipe an LLM through your contact form or build an "AI assistant" that has nothing to assist with. AI gets used where it removes a manual step, not where it sounds modern in a pitch.
Microservices for two endpoints
A monolith is correct until it is not. We have shipped twenty-plus production plugins as one cohesive PHP codebase. Splitting that into containers solves an imaginary problem and creates real ones.
Server-rendered frameworks where static would do
If the page does not change per visitor, render it once at build time. This is not new advice. Half the modern web ignores it anyway.
What we do use
Astro for cinematic brand sites. WordPress with custom themes and Elementor Pro when the client needs to self-edit. WooCommerce with custom plugins for stores that move real money. Plain PHP and SQLite for small apps, Postgres when scale demands it. Cloudflare for edge cache and security. Claude and Gemini where they earn it. Telegram for ops bots. Electron for desktop tools. The right tool for the job, every time.
Want to talk about your stack?
If your current build is fighting you, we will tell you whether the framework is the problem or the brief is.
Get an honest take