CloudCannon vs ShiftPress: Who Builds the Site, and Who Keeps It Running?

Most comparisons of website tools argue about features. This one is simpler, because CloudCannon and ShiftPress already agree on the thing that usually causes the argument. Both of us think a website should be static files in a Git repository rather than a database and a stack of plugins. Both of us think the result should be fast, secure and portable. If you have landed on this page you have probably already accepted that premise, so we are not going to spend the article re-selling it.

What is actually different is the shape of the work. Every website has three jobs: someone has to build it, someone has to make it editable, and someone has to keep it current. CloudCannon and ShiftPress split those three jobs between the customer and the platform in very different ways, and that split is the whole decision.

What CloudCannon actually is

CloudCannon calls itself a Git-based CMS, and that description is accurate and unusually honest. You connect a Git repository that contains a static site, CloudCannon builds and hosts it (or you bring your own hosting), and it layers a visual editing interface on top so content people can change pages without opening a code editor. Every change they make is committed back to Git, so your version history stays intact and nothing is trapped in a proprietary database.

It supports the static site generators developers actually use: Astro, Hugo, Eleventy, Jekyll, Next.js, Nuxt and SvelteKit, connected to GitHub, GitLab or Bitbucket. For a development team that has standardised on one of those, it is a genuinely good product, and the people who use it tend to like it a lot.

The step that decides whether CloudCannon is right for you is the second one in their own developer flow. After you connect the repository, a developer has to define the editing experience: build the components, declare which regions are editable, write the configuration that turns a folder of templates into something a non-technical colleague can safely touch. That work is not a footnote. It is the product. CloudCannon's own documentation is written for the person doing it, and their pitch to editors is explicitly "after your developer sets this up".

What ShiftPress actually is

ShiftPress starts one step earlier, from a site that already exists and is usually on WordPress. We copy it faithfully, page for page and URL for URL, into clean static code in a GitHub repository that belongs to you. Then you run it by talking to it. You type or say "change the opening line on the homepage", "add a page for the new service", "publish this as a blog post", and the agent edits the real pages, shows you a preview, and publishes when you approve. There is no editing experience to configure, because the thing you configure the editor with is a sentence.

The rest is deliberately included rather than assembled: hosting, backups, SSL, redirects, structured data, translations, forms and the lead inbox all sit inside the subscription. We wrote about the honest limits of that approach in ShiftPress vs self-hosting, and about what stays yours if you leave in no lock-in: your site belongs to you.

The real difference: where the developer sits

Here is the comparison stripped to one sentence each.

• CloudCannon removes the developer from everyday editing. Once the project is wired up, an editor can change copy and images visually and never file a ticket again. That is a real and valuable thing.
• ShiftPress removes the developer from the build as well. There is no repository to prepare, no component library to define, no schema to write. The migration produces the site and the editor at the same time.

So the question is not "which is better", it is "do you have a developer, and do you want to keep using one?" A software company with an in-house front-end team is not helped by us removing a developer they already employ and like. A dentist, a tax advisor or a two-person consultancy has no developer to remove from anything, and asking them to first commission a static site and then commission its editing configuration is asking them to solve the problem twice.

Getting there from WordPress

If you are reading this while still on WordPress, this is the section that matters most, because the two products treat that starting point very differently.

CloudCannon does offer a done-for-you migration, and it looks well run: you choose a static site generator, they build a free single-page proof of concept, and if you approve it they rebuild the whole site with a custom editing configuration and train your team. At the time of writing, that service is listed as starting at 3,000 US dollars per project. It is priced like the consulting engagement it is, and for a company moving a large content site with a specific SSG in mind, that can be money well spent.

ShiftPress is built around that one move, so it is priced as a product rather than a project. The migration is a one-time fee based on how many pages your site has: 149 euros for up to 10 pages, 299 euros for up to 50, 599 euros for up to 250, and a quote above that. Old URLs are preserved, redirects are generated where they are needed, and the design comes across as it was. If you want the detail of how that works, we cover it in migrating WordPress to a static site and in moving off WordPress without losing rankings.

One fair point in CloudCannon's favour: because you choose the SSG, you end up with a codebase your developers picked, in a framework they already know. With ShiftPress you get our output, which is clean, plain and readable, but it is our shape, not one you specified.

"AI" means two completely different things here

Both products talk about AI in 2026, and the words sound similar enough to be misleading, so it is worth being precise.

CloudCannon's AI story is developer-facing. Their argument, which is correct, is that a CloudCannon project is plain files in Git, which is exactly the format coding agents read best, so Cursor, Claude Code, Copilot or a self-hosted model can work on your site without fighting a CMS API in between. They also publish open-source agent skills that help those tools scaffold a site, write the configuration and add editable regions. That is a smart, honest position: the CMS gets out of the agent's way.

ShiftPress's AI story is owner-facing. The agent is not a tool your developer points at the repository. It is the interface you use. You do not open an editor at all if you don't want to. You say what should change, you look at the preview, you publish. There is a visual click-to-edit mode as well for people who prefer to point at the thing they want to change, but the default is a conversation. We wrote up the four common approaches and why most of them break in editing your website by chat.

The practical test: can the person who answers your phone change the price on the services page at four in the afternoon without asking anyone? On CloudCannon, yes for the fields a developer exposed, no for anything else. On ShiftPress, yes for anything, because there is no fixed set of exposed fields.

Price, side by side

These are list prices at the time of writing and both companies change them, so treat this as a shape rather than a quote.

CloudCannon charges per workspace, not per site. Standard is 55 US dollars a month (49 on annual billing) for three users and unlimited sites. Team is 350 a month (300 annual) for fifteen users, with workflows, scheduling and branching. Extra users are 10 a month each, bandwidth is 15 a month per 100 GB, and each custom domain is 2 a month. Agency partners get a Lite plan at 10 a month for smaller clients. If you already run twenty static sites, that is very good value.

ShiftPress charges a one-time migration fee per website and then a flat subscription: a free tier, then 10, 25 or 60 euros a month, with a quoted Pro plan for agencies running many client sites. Hosting, SSL, backups, translations, structured data and the lead inbox are inside it, and there are no bandwidth or per-domain line items. The full breakdown is on the pricing page.

Side by side

Where CloudCannon is the better choice

We would rather say this plainly than pretend otherwise. Pick CloudCannon if:

• You have developers and want to keep control of the stack. Choosing your own SSG, owning the component library and reviewing every commit is a real advantage, and we do not offer it.
• You run many sites that already exist as static code. Unlimited sites on one workspace plan is hard to beat on price, and there is nothing to re-migrate.
• You need editorial workflow. Branching, scheduling and staged review on the higher tiers are built for teams where several people touch content and someone approves it.
• Your team already uses coding agents. CloudCannon's plain-files position is genuinely well suited to that way of working.

Where ShiftPress is the better choice

• You are leaving WordPress and don't want a project. The migration is the product, priced by page count, not scoped as consulting.
• Nobody on your side writes code. There is no configuration step to outsource, so there is no one to wait for when something needs changing.
• You want the surrounding work included. Hosting, backups, redirects, structured data, translations, forms and leads come with it rather than as things to wire up.
• You want changes to be a sentence, not a ticket. That is the entire design goal.

If you are an agency, you might want both

This is not a joke answer. If your agency builds bespoke sites in Astro or Hugo for clients with real budgets, CloudCannon is a sensible place to put them, and its per-workspace pricing rewards volume. But most agencies also have a long tail of smaller clients where a bespoke build cannot be justified and the endless "can you just change this line" emails eat the margin. That tail is what ShiftPress for agencies is for: the client edits the site by talking, so the small changes stop coming back to you. Once three client sites run on it you can also join the partner network and get paid work routed your way. We looked at that economics in web agency as a service versus a traditional agency.

Frequently asked questions

The bottom line

CloudCannon is a good product built on the right foundation, and if you have a development team it may well be a better fit than we are. It removes the developer from the part of the job that annoys everyone, the endless small content edits, while leaving the build and the editing configuration where a developer belongs. The catch is that those two steps have to happen at all, and for a small business without a developer they are the expensive part. ShiftPress takes a different bet: that most owners do not want to choose a static site generator, commission a component library or approve a schema. They want the site they already have, faster and safer, and they want to change it by saying what should change. If that is you, start with how a WordPress migration to static actually works.