Open source · MIT licensed

Your ideas.
Your SEO.
Your publishing system.

A self-hosted foundation that turns editorial direction into searchable articles on your own domain—with Next.js, Supabase and optional AI.

Fork on GitHub

The source is free. Hosting, databases and optional providers may have their own costs.

010203

Why useful content compounds after you publish it

A focused editorial system connects what your audience asks, what your product knows and what search engines can understand.

Next.js 16Supabase + RLSSchema.orgIdempotent cronOwn domain

From direction to publication,
without surrendering control.

The template brings the moving parts into one repository. You choose the editorial rules and integrations; the system handles the repeatable plumbing.

01

Define

Set your brand, audience, tone, seed topics, internal links and CTA in one typed profile.

02

Generate

Use local topics or connect a text provider only after you define credentials and budget.

03

Store

Supabase keeps articles and execution state. RLS exposes only published content.

04

Publish

Next.js renders article pages, metadata and structured data directly on your domain.

Infrastructure you can inspect.
Decisions only you can make.

No closed dashboard sits between you and your publishing workflow. Every important setting lives in code you own.

Read the setup guide
Brand

Name, domain, narrative and conversion path.

Editorial

Audience, tone, keywords and internal links.

Operations

Schedule, credentials and provider limits.

Approval

Keep review human-controlled where your context requires it.

DAILY PUBLICATION CLAIMINTERACTIVE SIMULATION · NO JOB IS RUN
REQUESTPOST /api/blog/generate
GUARDDaily claim acquired
OUTCOMEOne article may publish
CLAIMED First execution owns today's slot.

The workflow can continue after reserving the date. A later call cannot claim the same schedule twice.

DUPLICATES0

This browser model explains the published guardrail contract. It does not contact Supabase, a cron route or any AI provider.

Daily claim

Idempotent execution prevents the same schedule from publishing twice.

RLS

Published only

Public database reads are restricted to articles already marked as published.

0

Credentials included

The repository ships without provider keys or production data.

Free source does not mean invisible infrastructure.

Cloning is free and triggers no provider. A complete installation still needs your own deployment, Supabase project and—only if enabled—AI or Search Console credentials.

Source codeFree
LicenseMIT
Hosting & databaseYour account
AI integrationsOptional

THE REPOSITORY IS THE PRODUCT.

Build a publishing system
that belongs to you.