Use cases

Who it’s for

SaaS marketing sites

• Marketing teams update copy without filing developer requests
• Static delivery keeps the public site on a CDN; authors edit locally or on staging
• Draft → publish workflow keeps work-in-progress off the live site

Agency delivery

• Hand off editable Astro sites to clients
• Run Caretize on their existing markup instead of rebuilding pages
• Keep quality controls through schemas and API constraints

Developer-managed content

• Keep published content in git — Markdown or a tracked JSON directory; exclude private drafts
• Add a CMS layer without replacing your Astro architecture
• Use getLiveEntry / getLiveCollection when you need programmatic access (server delivery)

Solo founders

• Add bindings by hand or let Caretize tag the site
• Static delivery: no server bill for the public site
• MIT-licensed and self-hosted

Where it shines

• Marketing sites where copy changes weekly
• Editorial sites where authors need editing in the context of the rendered page
• Markdown content-collection sites — edit existing src/content entries’ frontmatter and supported prose in place (Markdown adapter)
• 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 unless an external identity provider and appropriately scalable storage/rate limiting are configured
• Sites that need a built-in user administration screen or cross-editor approval queue. Identity-backed write permissions are available, but a shared review workflow is not.
• Sites that want a hosted CMS today (cloud mode is alpha and no generally available hosted service is included)

Next steps

Caretize CLIAuto-tag an existing Astro site.

Static deliveryCDN deploy without a CMS server.

QuickstartInstall, edit, publish, and preview.

Plug-In vs StarterPick the right adoption path.