The Raditor editor: a robot in a cozy sweater, knitting your content

The first CMS that’s actually rad!

Update your content. With style.

Raditor is an agentic content curator. Editor agents watch your sources for signals, draft graph-aware content for every affected site, and ship it wherever you publish: straight to your GitHub or into your existing CMS.

Raditors at work

Signals detected48,912

Suggestions drafted12,704

Pages updated31,586

Locales translated9,143

Bundles shipped7,268

Graphs updated54,027

How it works

Turns hard-to-maintain websites to easy-peasy-to-maintain

Connect

Point Raditor at your sources and publishing targets: GitHub repos, static sites, or your existing CMS. Onboarding drafts purpose and goals for you. Nothing to write.

Radar

Webhooks and scheduled sweeps cluster what happened into evidence-backed signals: releases, merges, the stuff that matters.

Suggest

Your editor agent turns each signal into a suggestion: what happened, what to build, why it matters, and how the site graph changes.

Ship anywhere

Accept, and Raditor publishes to whatever target your site already uses: a GitHub PR of static Markdown, or straight into your existing CMS. Links, sitemap, and locales included.

What makes it rad

◎

Content graph

Pages, sections, links, and locales, continuously reconciled from Git, so every suggestion knows the whole site.

✺

Cross-site fan-out

One signal ripples into coordinated updates across docs, blog, and marketing at once, cross-linked so you see the full picture.

Cadence governance

Daily, weekly, or monthly caps, allowlisted folders, and do-not-write policies. Never a content farm.

“

Evidence-backed

Every draft cites its source: the PR, release, or issue it came from. No invented product behavior.

✴

AI-answer ready

Clean structure, sitemap and llms.txt fragments, citable headings. Fresh content that answer engines actually quote.

➤

Any destination

Works with any CMS or ships plain Markdown directly to your GitHub. Your content stays where you publish. Humans can always edit anything; Raditor adapts.

Open infrastructure, not a walled garden

AGPL-3.0 and self-hostable. API-first with an open event log. Bring your own keys, even bring your own agents: they run through Raditor’s governance, not around it. Your content lives in your stack. Git or CMS, it stays yours.

github.com/raditor-io

AGPL-3.0

Fully open source. Self-host free, forever.

BYOK

Bring your own AI keys. No markup, first-class.

API-first

Everything the UI does, the API does too.

BYO-agent

Run your own agents through Raditor’s rails.