Stack · 17
Not sure where to start? Answer five questions and get a stack built out of these entries, with what each pick costs you.
Filter by kind
You design, publish and edit the whole site in one place, without a developer.
Design a site visually and publish it without a developer. The safe answer for a marketing site a team has to edit every week.
Visual builder, hosted, CMS collections, growing AI features
FitsCovers design, content and hosting in one bill. You do not add a separate CMS or host next to it.
The fastest way from a design to a live page. Best when the site is small, looks matter most, and one person owns it.
Visual builder, React under the hood, hosted
FitsSame slot as Webflow. Pick one of the two, running both splits your content in half.
You describe the marketing site you want and it builds and runs it. New, and the clearest example of where AI site building is going.
Agentic build-and-operate builder, ploy.ai, seeded June 2026
FitsAn alternative to Webflow and Framer, not something you bolt onto them.
The tool that writes and changes the code for you, and the place you connect the rest of the stack into.
Anthropic's coding assistant. It reads the whole project, makes the change and runs the checks, from your terminal or inside your editor.
Terminal and IDE agent, MCP client, takes skills and plugins
FitsTakes the same slot as Codex, Cursor and Copilot, so pick one. It works on a site you hold the code for, which means it has nothing to do on a Webflow or Framer site.
OpenAI's coding assistant. The same job as Claude Code, reached from the terminal, your editor, or handed off to run in the cloud.
CLI, IDE extension and cloud agent, MCP client, on a ChatGPT plan
FitsSame slot as Claude Code, Cursor and Copilot. The reason to pick it is usually that the team is already on ChatGPT, since that is where the plan lives.
An editor with the assistant built into it. You watch the change land next to the code instead of reading about it in a terminal.
VS Code-based editor with an in-editor agent, MCP client
FitsSame slot as Claude Code, Codex and Copilot. It suits someone who wants to see the code while it changes, rather than approve work a terminal reports back.
The assistant inside the editor your team already uses, and inside the pull requests where changes get reviewed.
In-editor completion and agent, pull request review, MCP client
FitsSame slot as Claude Code, Codex and Cursor. It is the one that changes least about how a team already works, because it arrives in the editor and the review they have.
Where the words and images live, so the same content can appear on a site, in an app and in an email.
Where your content lives when the same words have to appear on a site, in an app and in an email. Editors get a clean interface, developers get an API.
Headless CMS, structured content, GROQ queries, real-time studio
FitsSits behind a framework like Astro or Next.js and needs a host such as Vercel. Redundant if you are on Webflow or Framer.
A CMS that lives inside your own codebase, so an AI assistant can read and change your content model the same way it changes your code.
TypeScript-native CMS, runs in your Next.js app, own database
FitsLives inside your own Next.js app and needs a database. Takes the same slot as Sanity or Storyblok.
A CMS built for marketing teams that want to arrange page sections themselves without asking for a deploy.
Headless CMS with visual editor, component-based blocks
FitsSame slot as Sanity, with more of the page layout handed to editors. Feeds any framework, hosted anywhere.
You write the code, the framework turns it into pages that load fast.
For content-heavy sites that need to load fast: docs, blogs, marketing sites with hundreds of pages.
Static-first framework, ships almost no JavaScript by default
FitsPulls content from Sanity or Storyblok and deploys to Vercel. Needs someone who writes code.
Where the site actually runs once it is built, and how a change gets published.
Where the site actually runs. Push a change, get a preview link to share, publish when it looks right.
Hosting and CI for Next.js and friends, edge network, previews
FitsRuns sites built with Astro, Next.js or Payload, straight from GitHub. Not needed with Webflow, Framer or Ploy, which host for you.
You show a change to a share of your visitors, keep it if more of them buy or sign up, and drop it if they do not.
Show a change to part of your traffic and keep it only if more people buy. It also records what visitors do on the page, so you know what to test next.
A/B testing, heatmaps, session recordings and surveys in one platform
FitsThe all-in-one of this row: you do not add a separate heatmap or survey tool beside it. Same owner as AB Tasty since the two joined forces in 2026, so pick one of them, not both.
Testing plus personalisation: show a different page to a different audience, not just variant A and variant B, and release changes behind a switch.
Web and feature experimentation, personalisation, e-merchandising
FitsSame owner as VWO since the two joined forces in 2026, and the slots overlap. AB Tasty leans personalisation and merchandising, VWO leans research into why a page loses people.
You describe the experiment in a sentence and it builds it. The most AI-native option in this row, and a European company if that matters to you.
Prompt-built web and feature experiments, French company
FitsTakes the same slot as VWO, AB Tasty or Optimizely. The reason to pick it is the prompt-based setup and how much of the product an assistant can reach, not the feature list. Kai, the assistant built into the product, carries the same tool set as the MCP server without a connection step, so the AI route works before you have wired anything up.
The enterprise name in testing. Pick it when experiments have to run across a large site, several teams, and the code as well as the page.
Web and feature experimentation inside a larger marketing platform
FitsHeavier than the other three and priced for large teams. It sits next to your analytics rather than replacing it, and it is the one here whose assistant connection this library has checked end to end.
Where every change is recorded and reviewed before a visitor sees it.
The record of every change to the site, and the place AI tools do their work before anything reaches visitors.
Version control, pull request previews, Actions for automation
FitsSits under everything you code, and is what Vercel deploys from. Webflow and Framer sites never touch it.
