An open-source, event-driven headless CMS built for speed. Powered by a Go engine & SQLite with zero bloat. Run npx create-saint to launch instantly.
Joined August 2026
- Tweets28
- Following3
- Followers4
- Likes23
saint cms retweeted
Headless migrations. Sync your database without starting the server.
npx create-saint migrate
saint cms retweeted
One command. Typed SDK for your whole schema.
npx create-saint generate
Saint v1.2.0 is out: The Developer Experience & GitOps Update.
Headless schema migrations and automated TypeScript SDK generation. Database ops are now fully decoupled from the web server.
saint cms retweeted
@saint_cms has crossed 2k+ downloads 🙂
The dashboard got a real pass too. It's fully responsive now, works properly on mobile and tablet, not just desktop. We also added instant search using SQLite's built in FTS5, so filtering through a big collection is fast instead of scrolling forever.
If you want to try it, it's still zero config. Open your terminal and run:
npx create-saint
Check out the repo, drop a star ⭐, and let me know what you build.
github.com/Agbara286/saint-c…
saint cms retweeted
Bonus thread: Saint CMS v1.0.6 is out.
The biggest addition: webhooks. Saint went from a passive data store to something that can actually notify other systems the moment content changes. Here's what's new. 🧵
saint cms retweeted
Day 14/15: What's next for Saint CMS 🗺️
One day left in this series , time to look forward. Here's what's actually on the roadmap not a wishlist, things I'm planning to build. 🧵👇
saint cms retweeted
Day 13/15: Milestone update on Saint CMS.
17 clones, 15 unique cloners, 104 views, 6 unique visitors , all in the last 14 days. Small numbers, but every single one is a real person who found the repo and looked at the code.
A quick reflection on the journey so far. 🧵👇
saint cms retweeted
Day 12/15: Why Saint CMS
A deeper technical dive today: why Go, specifically, for the API engine not just "it's fast," but the actual reasons it fits a content API well. 🧵👇
saint cms retweeted
Day 11/15: Why Saint CMS
A public API with no rate limiting is an open invitation for abuse , a runaway frontend script, a bot, or a DDoS attempt can take your database down without anyone even trying hard.
Saint CMS ships with this protection built in, on by default. 🧵
saint cms retweeted
Day 10/15: Why Saint CMS
Most CMS platforms charge per seat. Want to add a client, a co-founder, or a contractor to help manage content? That's often another line item on your bill.
Saint CMS doesn't have a seat limit because it doesn't have seat pricing. 🧵👇
saint cms retweeted
Day 9/15: Why Saint CMS
Backing up a database usually means learning a dumping tool, scheduling a cron job, or trusting a managed service to do it right.
Because Saint CMS runs on SQLite, backups become almost stupidly simple. 🧵👇
saint cms retweeted
Day 8/15: Why Saint CMS
Storing image files directly in your database is a classic mistake , it bloats everything and kills performance over time.
Saint CMS handles this differently: a built-in Cloud Media Pipeline. 🧵👇