CMS Comparison: Rezilienz Vs. the World
Rezilienz is a Content Management System that sits at the intersection of several established CMS categories. This table maps how it compares to "Pure Headless" SaaS, "Modern Publishing" platforms, and "Classic Static" generators.
| Feature | Rezilienz | Strapi / Contentful | Ghost | Hugo / Jekyll |
|---|---|---|---|---|
| Data Source | Flat Markdown/YAML | Database (SQL/Cloud) | Database (SQL) | Flat Markdown files |
| Rendering | Hybrid (Dynamic + Static) | Pure API / Headless | Decoupled Hybrid | Pure Static Build |
| Admin UI | Built-in (Wizard v3) | Built-in (Generic) | Built-in (Polished) | None (needs 3rd party) |
| Privacy | "Antisocial" (Local-only) | Cloud-dependent (mostly) | Variable (CDNs/Tracking) | Excellent (but basic) |
| Headless? | Yes (Decoupled API) | Yes (API-First) | Yes (Decoupled) | No (Output is the head) |
| Best For | Editorial & AI Agents | General Purpose Apps | Newsletters & Blogs | High-perf Static Sites |
Architectural Deep Dive
1. The "Antisocial-Friendly" (Resilient) Edge
Unlike modern SaaS CMSs or even standard self-hosted platforms, Rezilienz is built for a less brittle web.
- Resilience: It is "antisocial" by choice—it doesn't rely on the global internet to function. If Cloudflare goes down or the LAN is isolated, Rezilienz keeps working.
- Zero Forced Dependencies: No calls to Google Fonts or telemetry. The base software is a clean, local-first environment.
- Separation of Concerns: While the foundation is self-contained, users can opt-in to external services (CDNs, Ads, etc.) at the frontend layer. The software provides the independent base; you choose the external connections.
2. The Hybrid Build Strategy
While Rezilienz provides a dynamic PHP-driven head (useful for real-time previews and AI content negotiation), it also includes a Static Site Generator (SSG) in its DNA.
cli-tools/generate-static.php: This allows Rezilienz to cross over into Hugo/Jekyll territory.- Security: You can run the Rezilienz Admin on a private, local machine and simply push the
dist/folder to a public static host. This "Air-gapped" publishing model is far more secure than traditional CMSs.
3. vs. Ghost (Modern Publishing)
Ghost is a beautiful, professional publishing platform, but it is ultimately a database-driven system.
- Rezilienz prioritizes the Content File as the single source of truth.
- While Ghost is better for monetization and memberships, Rezilienz is better for technical editorial work where you need the content to be portable, searchable, and manageable via standard filesystem tools.
4. vs. Hugo / Jekyll (SSGs)
Rezilienz gives you the "Static" benefits of Hugo (speed, security, portability) but adds the "Wizard" experience.
- In the Hugo world, you usually lose the ability to have a rich, web-based editor unless you integrate a separate tool like Decap CMS.
- Rezilienz builds the editor directly into the workflow, making it a cohesive "CMS for Static Sites."
TL;DR: Rezilienz is for the user who wants Contentful's UI, Hugo's speed, and absolute privacy.