Kirby vs WordPress
| Tagline | File-based CMS with no database required | World's most widely used open-source CMS and blogging engine |
| Category | Blogging & CMS | Blogging & CMS |
| Replaces | Squarespace, WordPress.com, Contentful | WordPress.com, Squarespace, Medium |
| GitHub stars | 1.5k | 21k |
| Language | PHP | PHP |
| License | ⊘ Proprietary | GPL-2.0 |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | yesterday | today |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Kirby
- Commercial per-site license required; cost adds up for agencies managing many sites
- File-based storage does not scale well for high-traffic sites with many content editors writing simultaneously
- No built-in e-commerce, memberships, or newsletter functionality
- Plugin ecosystem is smaller than WordPress; fewer pre-built integrations available
WordPress
- Plugin-heavy setups can become slow without caching layers and optimization expertise
- Security surface area is large; requires regular plugin/core updates and hardening
- The block editor (Gutenberg) has a steeper learning curve than Squarespace's drag-and-drop builder
- Default multisite and headless configurations require significant additional configuration
Bottom line
Choose Kirby if you want the lower-effort setup; choose WordPress for the larger community and ecosystem. WordPress has seen more recent development. Open each guide below for deploy steps and the full feature gap.