Why another CMS?

Because a five-page site shouldn't take an afternoon of removing things.

You know how it goes. A client needs a small site. You install a big CMS, then spend the afternoon removing things: comments, widgets, the emoji script. Then you add things back as plugins: one for SEO, one for forms, one for images, one for security, and one for the cookie banner the others made necessary. A year later half of them want a paid upgrade.

Boxlet CMS does the handful of things a small site needs, does them properly, and does them out of the box. That's all it tries to do.

A cookie scan of demo.boxletcms.org: no cookies are set before consent, with 0 necessary, preference, analytical, marketing and other cookies.

Checked, not promised

We scanned the demo for cookies before consent: none, in any category. PageSpeed gave it 100 on a computer and 99 on a phone, on 12 October 2026. Accessibility, best practices and SEO were 100 on both.

Fair questions

Is Boxlet GDPR compliant?

Boxlet is built not to collect personal data about visitors. Whether a site complies depends on the whole site, though: if you embed a Google Map or a Vimeo video, that provider's rules apply. We're a CMS, not your lawyer.

Can I add plugins?

No. That's on purpose. What a small site needs is built in.

Can clients log in and edit?

There's one administrator. If a client edits their own site, they're the administrator.

Is it ready?

This is a release candidate for v0.1. From v0.1 on, updates keep your site as it is: no fresh install between versions.

What does it cost?

Nothing. It's MIT licensed.

See for yourself

The demo is a real Boxlet site, an arts centre in an old printing works.