Powered By Cloudflare

BLUO CMS is powered by Cloudflare with 100% uptime as stated by Cloudflare.

May 13, 2022
Powered By Cloudflare
Alt Text: Powered By Cloudflare

100 Uptime

BLUOCMS is powered by Cloudflare with 100% uptimeas stated by Cloudflare.

Quote: "1.1 100% Uptime. The Service will serve Customer Content 100% of the time without qualification." - Stated by Cloudflare.


Cloudflare is one of the fastest CDNand BLUO uses Cloudflare workersto server all websites, so even if BLUO server is not working your website will always be working.

BLUO Architecture

BLUO never hosts your website directly. When you publish an article we create an optimized version of the article (html, css, js, images...) and we upload the files to Cloudflare to KV Store. Then we use Cloudflare workers to serve the static assets.

Comparison With Wordpress And Other Similar CMS

When a visitor goes to your wordpress website, even if uses Cloudflare, it will hit the cache or will hit your Wordpress server. If Wordpress is down, visitors might not be able to see certain pages. Also Wordpress generates the optimized html, js and images only when the visitors arrives (BLUO generates these files when you press publish) so the Wordpress server needs some time to generate all these files, which can be much slower. If there is an error during the rendering, it will show the error to the end users.

Can My Website Be Hacked?

With BLUO your website cannot be hacked as it is with Wordpress because Cloudflare Workers only servers content that has been generated already. Forget about Wordpress viruses and focus on content.

What Is KV Store?

Quote: "Workers KV is a global, low-latency, key-value data store. It stores data in a small number of centralized data centers, then caches that data in Cloudflare’s data centers after access. KV supports exceptionally high read volumes with low latency, making it possible to build highly dynamic APIs and websites that respond as quickly as a cached static file would. While reads are periodically revalidated in the background, requests which are not in cache and need to hit the centralized back end can see high latencies."