Grav VS Kirby

Compare Grav vs Kirby and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Grav Kirby
84 56
14,283 1,195
0.4% 2.9%
8.6 9.9
6 days ago 5 days ago
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of Grav. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-03.
  • Ask HN: What products other than Obsidian share the file over app philosophy?
    6 projects | | 3 Apr 2024
    There are flat-file CMSes (content management systems) like Grav:

    I guess, in some vague/broad sense, config-as-code systems also implement something similar? Maybe even OpenAPI schemas could count to some degree...?

    In the old days, the "semantic web" movement was an attempt to make more webpages both human- and machine-readable indefinitely by tagging them with proper schema: Even Google was on board for a while, but I guess it never saw much uptake. As far as I can tell it's basically dead now, both because of non-semantic HTML (everything as a React div), general laziness, and LLMs being able to parse things loosely.


    Side thoughts...

    Philosophically, I don't know that capturing raw data alone as files is really sufficient to capture the nuances of any particular experience, or the overall zeitgeist of an era. You can archive Geocities pages, but that doesn't really capture the novelty and indie-ness of that era. Similarly, you can save TikTok videos, but absent the cultural environment that created them (and a faithful recreation of the recommendation algorithm), they wouldn't really show future archaeologists how teenagers today lived.

    I worked for a natural history museum for a while, and while we were there, one of the interesting questions (well, to me anyway) was whether our web content was in and of itself worth preserving as a cultural artifact -- both so that future generations can see what exhibits were interesting/apropos for the cultures of our times, but also so they could see how our generation found out about those exhibitions to begin with (who knows what the Web will morph into 50 years later). It wasn't enough to simply save the HTML of our web pages, both because they tie into various other APIs and databases (like zoological collections) and because some were interactive experiences, like games designed to be played with a mouse (before phones were popular), or phone chatbots with some of our specimens. To really capture the experience authentically would've required emulating not just our tech stacks and devices, among other things.

    Like for the earlier Geocities example, sure you could just save the old HTML and render it with a modern browser, but that's not the same as something like , which emulates the whole OS and browser too. And that still isn't the same as having to sit in front of a tiny CRT and wait minutes for everything to download over a 14.4k modem, only to be interrupted when mom had to make a call.

    I guess that's a longwinded of critiquing "file over app": It only makes sense for things that are originally files/documents to begin with. Much of our lives now are not flat docs but "experiences" that take much more thought and effort to archive. If the goal is truly to preserve that posterity, it's not enough to just archive their raw data, but to develop ways to record and later emulate entire experiences, both technological and cultural. It ain't easy!

  • Soupault: A static website management tool
    10 projects | | 22 Mar 2024
  • Grav is a modern open-source flat-file CMS
    3 projects | | 16 Jul 2023
  • Grav – A Modern Flat-File CMS Using PHP and Markdown
    1 project | | 9 Jul 2023
  • It Took Me a Decade to Find the Perfect Personal Website Stack – Ghost+Fathom
    14 projects | | 9 Jul 2023
    I took a more traditional approach, focusing on something that's "good enough", which in my case was a cheap VPS and an install of Grav:

    Some optional customization for page templates/fonts/CSS, some CI so I can build and deploy it inside of a Docker container, Matomo for analytics that respect privacy (which I already use elsewhere) and some additional web server configuration to hide anything interesting behind an additional login and I'm good. Maybe backups and uptime monitoring if I'm feeling brave, which is what most sites should also have (so copy + paste there).

    All of that for under 100 euros per year (could also pay half of that if I didn't host anything else on the server), the blog has actually survived getting on the front page of HN once or twice and requires relatively little maintenance, at least a bit less than a proper install of WordPress, due to its larger surface area.

    The best thing is that it's simple enough for me to understand how it works, to be able to move it anywhere as needed and use more or less plain Markdown for writing the blog posts. Here's a quick example of a recent post:

    Now all that's left is to find motivation to write more, but at least 90% of my time doesn't go into tinkering with custom fancy solutions, no matter how much I'd love that. Then again, nothing wrong with the alternatives either: 400 euros might be perfectly worth it for some, whereas working with static site generators or even custom CMSes would be a fun experience for others!

  • Grav: Modern, open-source, flat-file CMS
    1 project | | 6 Jul 2023
  • Is it possible to convert a WordPress site into a static site that can still be easily edited?
    1 project | /r/Wordpress | 6 Jul 2023
    I'd check out Grav.
  • Gravity - A new, open source DNS/DHCP server with Adblocking and inbuilt config replication
    7 projects | /r/selfhosted | 29 Jun 2023
    Also, there is a CMS called Grav. Both Gravity and Grav use a very similar (but not identical) font for their logo.
  • Mercredi Tech - 2023-06-28
    1 project | /r/france | 28 Jun 2023
  • website with unlimited pages ??
    1 project | /r/webdev | 27 May 2023
    I would use a flat file cms like


Posts with mentions or reviews of Kirby. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-21.

What are some alternatives?

When comparing Grav and Kirby you can also consider the following projects:

Pico - Pico is a stupidly simple, blazing fast, flat file CMS.

WordPress - WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to and patches to instead.

october - Self-hosted CMS platform based on the Laravel PHP Framework.

Next.js - The React Framework

Bolt - Bolt is a simple CMS written in PHP. It is based on Silex and Symfony components, uses Twig and either SQLite, MySQL or PostgreSQL.

ProcessWire - ProcessWire 3.x is a friendly and powerful open source CMS with a strong API.

Bludit - Simple, Fast, Secure, Flat-File CMS

Textpattern - A flexible, elegant, fast and easy-to-use content management system written in PHP.

Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.

GetSimple CMS - GetSimple CMS