Being a Framer partner would make it easy to answer every stack question with Framer. That would also be bad advice. The honest answer depends on three variables: who edits the site after launch, how much custom logic it needs, and how fast you need to move.
When Framer wins
Marketing sites, launch pages, event sites. Your team edits copy without a deploy pipeline, animations ship in days not weeks, and hosting, CDN and forms come standard. For 80 percent of startup websites this is simply the right tool, which is why we invested in the partnership.
When code wins
Product dashboards, anything with wallets or auth, sites where SEO demands full control over rendering and structured data. Framer is a website tool, not an application framework. Pretending otherwise creates expensive rebuilds a year later.
The hybrid we ship most
Framer for the marketing surface, code for the product, one design system across both. Users never notice the seam, teams get the editing speed where it matters, and engineers stop being a bottleneck for copy changes.