WHAT IS IT?
StudioCMS is a headless CMS built specifically for Astro. Where a classic CMS runs alongside the site and is consumed through a remote API, StudioCMS installs as an Astro integration (npx astro add studiocms) and lives inside the project, server-side rendered. Content goes into its own database and the admin dashboard is served by the site itself. Worth noting: the project is still on 0.x, and the API shifts between releases.
WHY IS IT INTERESTING?
- An integration, not another service: no second deployment to maintain, no API key between the CMS and the front end. Dashboard, authentication and content routes are generated in the same Astro build as the site.
- Everything goes through plugins: the core stays minimal and features are added as packages. Renderers (
@studiocms/md,mdx,markdoc,html,wysiwyg), OAuth, a Cloudinary image service, a ready-made blog front end, plus an API to write your own, custom dashboard pages included. - Pick your database: libSQL by default (Turso compatible), but PostgreSQL and MySQL work too. Access goes through Kysely, with a migration system shipped to track schema changes.
- Authentication included: native username and password, plus GitHub, Discord, Google and Auth0 through the OAuth plugin. User, role and permission management sits directly in the dashboard.
- Self-hosted and MIT licensed: no SaaS offering forced on you, data stays on the infrastructure you picked. SSR mode also runs on serverless hosts, with full editing capabilities.
USE CASES
- Adding an admin interface to an existing Astro site without standing up a separate CMS
- Marketing site or blog run by non-technical writers, while keeping a custom Astro front end
- Replacing a SaaS headless CMS with a self-hosted stack on the same codebase
- Multi-user Astro projects that need roles and real access control
- SSR content backend on Turso or PostgreSQL, deployed serverless