Framer vs. code in 2026: what we ship, and why.

Theo Lindqvist

Head of Web

Sep 18, 2026

We build most marketing sites in Framer and most products in code. Here’s the line we draw, and the three questions that decide it.

Every few months someone asks us whether no-code is “ready.” The honest answer is that it stopped being a question a while ago. The real question is who will be editing the thing in eighteen months — and how much it costs them every time they do.

The marketing site is a living document

A marketing site changes weekly: new campaigns, new case studies, a pricing tweak at 11pm before a launch. If every change needs a developer, it either doesn’t happen or it happens badly. Framer puts the pen back in the marketer’s hand without handing them a loaded gun.

The best stack is the one your team will still enjoy using after we leave.

Where we still write code

Products are a different animal. Authentication, state, complex data and performance budgets belong in a real codebase with tests. There we design the system in Figma, hand it to engineers with tokens and specs, and stay on through QA.

Halcyon’s booking flow runs on their existing engine; everything around it lives in Framer and is edited by the front-desk team.

Three questions that decide it

Who edits it? How often does it change? What happens if it breaks at 2am? Answer those honestly and the tool picks itself. Most of the time, for us, it’s both — Framer on the outside, code at the core.

Written by