The short answer
Pick the platform that fits the people who will run the site, not the one with the loudest fans. Four questions settle most cases: who edits, how custom the site needs to be, who should host it, and whether you want to own the code. Answer them from your brief and the choice usually becomes obvious.
This chapter does not rank platforms. Each one is the right answer for someone. The facts about each come from the vendors' own docs, linked inline, so you can check them. Where we give an opinion, we say it is ours.
What each platform is
A quick description of the four platforms buyers ask us about most, in the vendors' terms.
| Platform | What it is | Where the site runs |
|---|---|---|
| Webflow | A visual builder where design, CMS and hosting live in one product. Content editors can change copy, media and CMS content in a simpler view without touching the design (Webflow help). | Webflow hosting, on a Site plan for a custom domain (Webflow help) |
| Astro with Sanity | Astro describes itself as a web framework for building content-driven websites like blogs and marketing sites (Astro docs). Sanity Studio is an open-source editing app where developers define the content model (Sanity docs), and the content is stored in Sanity's Content Lake (Sanity docs). | Any host Astro supports. Its deploy guides cover many, including Netlify, Vercel and Cloudflare (Astro docs) |
| Framer | A visual site builder with a CMS and on-page editing, which lets owners and collaborators update content from the published site (Framer help). | Framer hosting, which Framer says runs on AWS and is served through a worldwide CDN (Framer help) |
| WordPress | An open-source publishing system built on PHP and MariaDB and licensed under the GPLv2 (WordPress.org). | Any host you choose that runs it |
Two of these are hosted products, where the vendor runs the servers. One is a framework, where your site is code that you deploy. WordPress is software you install, or pay a host to run. That difference matters more than any feature list.
The questions that decide
Take your brief from chapter 1 and answer these in order. Stop when one of them settles it.
- Who edits, and what do they change? A marketer who wants to change a section's layout needs different tools from one who only changes words.
- How custom is the site? Standard marketing pages suit visual builders well. Calculators, logins, unusual data or heavy integrations push toward code.
- Who should host it? A hosted product means one bill and no servers to run. Your own hosting means more control, and someone has to own it.
- Do you need to own the code? Some companies need the site in their own repository for security or policy reasons. Others never want to see code.
- Who will look after it in two years? A platform your team, or a partner you trust, can support is worth more than a slightly better one nobody can.
Notice what is not on the list: which platform is "fastest" or "best for SEO". A well-built site on any of these can be fast and easy to find. A badly built one on any of them can be slow and hard to crawl. Build quality beats platform choice on both counts.
Decision rules
These are our rules of thumb, based on how we choose for our own projects. They are a starting point for a conversation, not a law.
Decision rule If your marketing team wants to build and change pages visually, and the site is mostly marketing pages and a blog, start with Webflow.
Decision rule If you want the code in your own repository, the fastest possible pages, or a site that pulls content from several systems, start with Astro and a headless CMS such as Sanity.
Decision rule If the site is small, design-led and motion-heavy, and one designer will run it, look hard at Framer.
Decision rule If you already run WordPress well, with a team that knows it and plugins you depend on, the case for moving has to be specific. Write down what is broken before you plan a move.
If two rules fit, go back to question 1. Who edits is almost always the tie breaker.
Lock-in and leaving later
Every platform makes leaving easier or harder in its own way. Ask about it before you start, not when you want to go.
- Webflow. On paid Workspace plans you can export a site's HTML, CSS, JavaScript and assets. Webflow says the export does not include CMS content, and that forms and site search do not work on exported sites (Webflow help). CMS items can be exported as CSV files from the CMS panel (Webflow help).
- Astro with Sanity. The site is code, so it lives wherever the repository lives. Content sits in Sanity as structured data, which you query through its APIs.
- Framer and WordPress. Ask your builder to show you how content and pages would leave, in writing, for the version you will use.
Lock-in is not always bad. A hosted builder trades some freedom for less to run. The point is to choose it knowingly. If leaving would be hard, make sure everything else in this guide, especially ownership in chapter 5, is in your name.
When not to change platform
A redesign does not have to mean a new platform. Moving costs money and carries search risk, because every URL needs a plan. It is worth it when the platform is the problem, not when the design is.
| The complaint | Usually a platform problem? | Try first |
|---|---|---|
| The site looks dated | No | A redesign on the same platform |
| Our team cannot edit without a developer | Sometimes | Check whether the build, not the platform, is the blocker |
| Plugins keep breaking after updates | Often | List the plugins and what each one does |
| Pages are slow | Sometimes | Measure first. Images and scripts are common causes on any platform |
| We need features the platform cannot do | Yes | Confirm with the vendor's docs, then plan the move |
For a side by side look at specific pairs, see our comparisons: Webflow vs WordPress, Webflow vs Astro, Webflow vs Framer and Framer vs Astro.
Where Kookies stands
We are a Webflow Premium Partner and we also build in Astro with Sanity and in Framer. So we have a view, and you should weigh it like any seller's. We recommend Webflow most often for marketing teams that want to edit visually, and Astro with Sanity when code ownership, speed or many content sources matter. We say so on the first call, along with the reason.
Whoever you ask, a good answer to "which platform?" comes with a reason tied to your brief. If the answer is the same platform for every client, the advice is about the seller, not about you.


