CloudCannon Pricing Overview

Generous hosting tier Customizable and powerful editing experience Tons of features related to (re)building sites based upon commits, timers, and API hooks. The form integrations are killer too!

Prices have increased, but it's still a good value for the money. I'm also not aware of the improvements their making to support more platforms -- first-class BridgetownRB support would be stellar!

It makes it easy for me to customize the editing experience for my clients and build websites quick in my favorite static site frameworks. I'm able to keep support costs low and maintain a number of support contracts with must customers.

I love CloudCannon because of how easy it is to customize their CMS. New features are constantly being added, and even though things break every now and then, the helpfulness of their customer support means you never have to worry.

The support documentation isn't always up to date, and the recent price increase was substantial. In my opinion, client access to the CMS could be more flexible: I'd love to be able to grant access to, say, DNS settings for some clients.

A cost-effective, scalable way to host client websites built on Jekyll & JAMstack technology.

Static site performance, optimizations. Client editing experience. Super easy version control integration.

We don't use it for anything except static sites - no dislikes.

Cost-effective, simple, performant static site hosting.

Cloudcannon is so feature rich and easy to use. I love how it automatically integrates with Github and the builds are super fast. I used to have to wait several minutes on my old CMS for a build, and on cloudcannon its done in a minute or two. I also like that I can commit several edited pages at one time and not have to make a commit every time I edit a single page.

I don't like that it currently doesn't save files locally on cloudcannon. I lost my internet connection once, and I lost some edits I was working on. Support was great in helping me, and the CEO Mike told me he was adding it to their roadmap for adding that functionality to their software.

Our old CMS decided to "sunset" their platform, leaving us with no option but to switch CMS's, which was actually great because Cloudcannon is a far superior product and the same price. The CEO Mike helped us through every stage of our migration. I even had a call with one of their Client Specialists where he asked me questions about how my experience was with the product and how they could make it better. That kind of dedication towards customer service is a big tell tale sign of a great company with great people in management.

CloudCannon gives quite a bit more control to stakeholders than a headless CMS would, but doesn't require that they learn HTML/CSS. It also lets devs write code using the tools they know best. It's great when you've got custom requirements, a team of reasonably capable stakeholders, and a good dev. Unless I were using a stock template and on a project with no special or custom requirements, I'd pick CloudCannon over any of the site builders or headless CMSs any day. The dev and support team are also super capable. Any time I ran into issues, they worked with me to resolve them quickly. I believe I was the first person to use AlpineJS with CloudCannon, so we got to investigate and solve some novel bugs together with that. I'm a huge fan of CloudCannon.

Site building on file-save can be a little bit slow, especially when you're making a bunch of little changes. I think they're still coming into their own in terms of documentation and in terms of finding the balance between convention and configuration. I don't see any of these as meaningful impediments. The dev team has a really ambitious road map in front of them, and they do a great job of listening to and acting on feedback.

CloudCannon provides a clickable WYSIWYG interface for editing static sites (e.g. those built with Hugo, Jekyll or Eleventy). It slots neatly between Wordpress/Squarespace (and other block-based site-builders) and tools like Ghost (or other headless CMSs), and lets stakeholders immediately see the effect of their changes, and lets devs go at full speed. There's also the Bookshop component framework, which enables some really dynamic page-building. I've found this is the sweet spot - my stakeholders can make changes to content (and sometimes layout) without needing to know coding, without needing to involve me, and without fear of breaking things. I can empower my stakeholders and focus on doing my best work. We have far, far less back-and-forth, I'm no longer a bottleneck, and things just work.

The simple CMS for our clients to use together with an extensive framework to build functionality for most website needs. Also, the reliability of the website hosting is always a priority and I think CloudCannon has had an excellent track record for us.

The main downside with CloudCannon for us are definitely the pricing, so for the smaller sites it can be a bit expensive but for larger sites it is not that big of a problem.

The main issue CloudCannon is solving for us is making it easy for our clients to edit their own websites without having to contact us. Other than that I would say that it also makes it more convenient to update everything in the editor when you use components in CloudCannon.

The editor is great and with the use of cloudcannons bookshop components, we can extend the functionality of the editor infinitely. The awesome team behind cloudcannon is a big plus as well.

The integration steps can be a bit tricky when using custom bookshop components. This could be easier if the documentation was a bit more in-depth. It would also be really good if there was one included external editor per project so that we don't need to charge our smallest clients for a entire editor account.

Cloudcannon helps us give our clients a customized editing experience that fits their needs. We have tried multiple editors/CMS:s before and cloudcannon is at another level.

I like that someone else has set up the account for me. The layout looks clean but...

I have no idea to customize further. The help articles aren't friendly for someone who's clueless about developing. It's very easy to be disorganized with files on here, which can definitely be attributed to user error, but I have no help from CloudCannon. I do not feel support from CloudCannon's resources.

CloudCannon hosts my team's website, and we need a website. I do wish it was easier for non developers to use. We have to contract out to ask questions like why the build is failing and how we can fix it. It would be great to have automation to help a user like me know what I may need to fix and HOW to fix it. If you take a look at our current account, a build has been failing for 3 weeks, and we still haven't figured out why.