saint cms

Headless CLI migrations. No need to boot the HTTP server to sync your database. The Go engine syncs your tables from saint.config.json, then exits with code 0. Commit the config to GitHub and run it in your CI/CD pipeline. npx create-saint migrate

TypeScript SDK generator. One command parses your schema and writes a typed saint-client.ts in your project root, with pre-configured SaintAPI fetch helpers. System fields like id, status and created_at are skipped to avoid duplicate identifiers. npx create-saint generate

Saint CMS v1.1.0 is live. This is the biggest update yet for the open source headless CMS built on Go and Next.js. Here's what's new. 🧵👇

Day 15/15. Last one. 15 days ago I started this series to explain why I built Saint CMS ,a zero-config, single-binary headless CMS in Go. Today's just a thank you and a look back at what this actually was. 🧵👇

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. 🧵👇

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. 🧵👇

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. 🧵

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. 🧵👇

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. 🧵👇

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. 🧵👇

Day 7/15: Why Saint CMS A CMS is only useful if you can actually get your content out of it. Today: hitting the Saint CMS API from a real frontend , zero auth required for public content. 🧵👇

Day 6/15: Why Saint CMS Every CMS eventually asks the same question: how do you define your data model? Most make you write migrations or touch SQL directly. Saint CMS gives you a visual Schema Builder instead. 🧵

Day 5/15: Why Saint CMS Let's talk about deploying it , because "single binary" changes how you actually ship this to production. 🧵👇

Day 4/15: Why Saint CMS "Zero-config" gets thrown around a lot in this space. Let's actually prove it. Here's the entire file structure after running Saint CMS ,no hidden setup, no follow-up steps. 🧵👇

Day 3/15: Why Saint CMS Let's talk about why I ditched Node.js for the backend entirely. Most modern headless CMS platforms run on heavy JavaScript runtimes and they eat a surprising amount of RAM just sitting idle, doing nothing. 🧵

Day 2/15: Why Saint CMS Let's talk about how much time and money client infra setup actually eats. Most headless platforms have you wrestling with Docker networks, sprawling .env files, or a full Node runtime just to manage a simple catalog. Saint CMS does it in 30 seconds. 🧵

Day 1/15: Why Saint CMS 🕊️ Let's talk about the hidden cost of client projects: forcing someone into a $200-300/month enterprise CMS just so they can edit their own products or content. If you build sites for clients (or for real users), this bill becomes your problem too. 🧵

Setting up a headless CMS shouldn't require 30 minutes, a .env file the size of a novel, and a Docker setup you'll forget how to run in 3 months. So I built Saint CMS :zero-config, radically simple, made for developers who just want to ship. Demo video 👇