Sitely CMS.

One back office for the content, mail and AI of every site I run. Mostly that's Niro3D, Lucky Auto, Drivora and many others of mine.

Role
Own product · design, build, run
When
2026 – now
Kind
Product
SvelteKitSvelte 5TypeScriptPostgreSQLRedis
sitely.cz
Sitely CMS demo: the overview of a sample site

Why it exists

Every site I ran grew its own mailer, its own contact form and its own way of calling an AI model. At one point there were six mailers. Sitely CMS is the one place they all moved to, so a new site starts with all of it on day one.

What it does

Content

Pages, lists and translations, edited in one back office. Each site reads them through a versioned API.

Mail and forms

Every contact form, reply and newsletter goes through one queue and one sender.

AI

A site asks for a role, like "write" or "edit an image", never a model. The gateway picks the model and owns the retries.

Sitely CMS demo: the content list with each page's Czech, English and German status

The content list: every page with its Czech, English and German status.

How it's made

I drew every screen in pen.dev before it was built, with all of its states: empty, loading, failed and full. A check refuses a screen that has no drawing. AI agents build it, one task each, and one full check decides what ships.

How I build →

What I'd do differently

Start with the shared services. I built the sites first, and each one grew its own copy of mail and AI before they moved into one place.