cerise.

Fast today, ready for tomorrow

One read per article, nothing to run in the browser, and one CMS for several sites.

Oct 27, 20261 min readBehind the scenesEn français

Nail polish bottles in many colours, lined up on a white surface

Three choices make this blog fast.

One read per article. An article from the repository takes a single read in Deno KV, from the nearest copy: about 50 ms, measured in production.

A short memory for the CMS. Payload's articles stay in memory for 60 seconds. If the CMS takes longer than 2.5 seconds, for instance when Cloud Run wakes up, the blog serves the last good copy and finishes the read in the background.

Zero public JavaScript. The browser receives HTML and CSS. It has nothing to download or run before showing the text.

And to grow: a new site needs only a domain in the CMS. Authors keep one place to write, and each site keeps its speed.

Written elsewhere

This post comes from the shared CMS

It is written in Payload, not in cerise's editor. Open a post from the repository instead: there, everything can be edited.

See Payload

Next post

Method

One place for all your content

Your site, your store and your blog can read the same CMS.

Oct 26, 2026 · 1 min read

More to read

← All posts
View the raw textHide the raw text

This is the markdown as Payload keeps it. The page is built from it when it is read.

Three choices make this blog fast.

**One read per article.** An article from the repository takes a single read in Deno KV, from the nearest copy: about 50 ms, measured in production.

**A short memory for the CMS.** Payload's articles stay in memory for 60 seconds. If the CMS takes longer than 2.5 seconds, for instance when Cloud Run wakes up, the blog serves the last good copy and finishes the read in the background.

**Zero public JavaScript.** The browser receives HTML and CSS. It has nothing to download or run before showing the text.

And to grow: a new site needs only a domain in the CMS. Authors keep one place to write, and each site keeps its speed.