Launching today

YunCMS

Launching today

Self-hosted MySQL CMS with RBAC, AI, MCP and Docker

3 followers

Self-hosted MySQL CMS with RBAC, AI, MCP and Docker

3 followers

Visit website

Headless CMS software

YunCMS is an open-source, self-hosted MySQL CMS/backend for teams that want schema-driven content APIs without rebuilding auth, permissions and file handling. It combines a React Studio, REST API, field- and row-level RBAC, local/S3 files, extensions, and backup/update tooling. Run it with npm or the official multi-platform Docker Compose stack. Optional AI and MCP integrations operate under the signed-in user's existing permissions. The 0.1.x line is pre-stable.

Free

Launch tags:API•Open Source•Database

Launch Team / Built With

Maker

📌

Hey Product Hunt! 👋 I’m excited to introduce YunCMS an open-source, self-hosted headless CMS built for developers who want flexibility without unnecessary complexity. We started building YunCMS because we wanted something that feels lightweight and straightforward, but still gives you the building blocks needed for real projects: dynamic collections, APIs, authentication, permissions, file management, extensions, hooks, and custom endpoints. A few things we care about a lot: • Simple self-hosting • Developer-friendly extension system • No vendor lock-in • Flexible data modeling • REST APIs out of the box • A clean admin experience • Easy deployment, including traditional hosting environments YunCMS is still evolving quickly, and this launch is a big opportunity for us to hear from people outside our own team. If you try it, I’d especially love to know: What would make you choose YunCMS over tools like Directus, Strapi, or Payload? Thanks for checking it out every piece of feedback helps us shape what comes next. 🚀

Report

11d ago

Forum Threads

p/yuncms

•

2d ago

What do you verify before trusting a self-hosted CMS in production?

We re launching YunCMS on September 14. It s an open-source, self-hosted MySQL CMS/backend that grew out of watching teams rebuild authentication, permissions, CRUD, file handling and extension plumbing across projects. Now AI tools also need to work with those systems without bypassing permissions.
Before you trust a new self-hosted backend, what do you test first?
My current shortlist:
a backup and restore flow you have actually tested
field- and row-level permissions, including the Public role
session and API-token behavior behind a reverse proxy
file-storage recovery
a predictable, pinned update path
AI and MCP access constrained by the same RBAC as human users
YunCMS is still in the 0.1.x pre-stable line, so this is exactly the kind of feedback we want before claiming maturity.
What would you add to the list, and which item has caused the most pain in a real deployment?

View all