Use Cases

Who it’s for

SaaS marketing sites

• Marketing teams ship new pages quickly without filing tickets
• Product teams update launch messaging without blocking engineering
• Live editing means no separate “preview vs prod” content drift

Agency delivery

• Hand off editable Astro sites to clients
• Keep quality controls through API and schema constraints

Dev-led content ops

• Keep content in source-controlled JSON files
• Add a CMS experience without replacing your Astro architecture
• Use getLiveEntry / getLiveCollection for programmatic data access alongside inline editing

Solo founders

• One file to edit, one attribute to add, one password to set
• Zero schema modeling — ship the page, tag what’s editable, move on
• MIT-licensed, runs on a single $5 VPS

Where it shines

• Marketing sites where copy changes weekly
• Editorial sites where authors need WYSIWYG context
• Client-handoff sites where developers don’t want a help-desk role
• Product-led sites where founders edit headlines themselves

Where to look elsewhere

• Sites with thousands of editorial users (auth model is one shared password)
• Sites that need granular role-based permissions (no users, no roles yet)
• Sites that want a hosted CMS today (Cloud mode is alpha — not live)

Next steps

Quickstart Five minutes to first edit.

Plug-In vs Starter Pick the right adoption path.