What is Kirby?

Kirby is a file-based content management system that stores content as text files rather than in a database. Created by Bastian Allgeier in Germany, Kirby has earned a devoted following among designers and developers who appreciate its simplicity, flexibility, and the full control it provides.

Kirby is “The CMS for designers”, designed for professionals who want to build custom websites without the overhead of complex architectures. Its file-based nature makes projects easy to version control, deploy, and maintain.

Licensed per project with a one-time fee, Kirby offers unlimited usage within paid license terms.

Architecture and Technology

Kirby uses a flat-file architecture with content stored as plain text.

Core Components

Content folder: Structured text files (Markdown/YAML)
Panel: Vue.js-based admin interface
Templates: PHP templates for rendering
Blueprints: YAML-based content model definitions
Plugins: PHP-based extensions

Content Storage

Content is stored as text files:

content/
  projects/
    project-1/
      project.txt
      image.jpg
    project-2/
      project.txt

Each folder is a page, each .txt file contains structured content fields.

No Database

Git-friendly content storage
Easy deployment via FTP or Git
No database configuration needed
Content readable without the CMS

Typical Use Cases

Kirby is commonly used for:

Design portfolios: Photographer and designer showcases
Agency websites: Custom client projects
Small business sites: Marketing and brochure sites
Documentation: Project and product docs
Personal sites: Blogs and CVs
Microsites: Campaign and landing pages

Strengths

Beautiful Panel: Elegant, customizable admin interface
File-based: Git-friendly, no database needed
Full flexibility: Complete control over output
Clean architecture: Simple, understandable structure
Blueprints: Powerful, declarative content modelling
One-time license: No recurring fees
Developer experience: Pleasant to work with

Limitations and Trade-offs

Commercial license: Paid license required
File-based limits: Not suitable for very large sites
PHP hosting: Requires PHP server
No REST API: API only via plugin (Kirby QL)
Smaller community: Less resources than WordPress
Manual updates: No automatic CMS updates

SEO, Performance, and Content Governance

SEO

Full control over HTML output. SEO implementation is entirely custom,add exactly what you need.

Performance

No database means fast content retrieval. Static caching possible for production.

Content Governance

Panel permissions for multi-user. Git history serves as content versioning.

Tips and Best Practices

Use blueprints extensively for content modelling
Version control content folder alongside code
Leverage blocks for flexible content areas
Cache aggressively in production
Explore plugins in the official directory
Read the cookbook for common patterns

Who Should (and Should Not) Choose Kirby

Best Fit For

Designers and developers wanting control
Portfolio and small business sites
Teams valuing simplicity
Git-based deployment workflows
Projects with modest content scale

Not Ideal For

Very large content sites
Non-technical content teams alone
Projects needing extensive API
Free CMS requirements
Sites with thousands of pages

Common Alternatives

Statamic: Similar philosophy, Laravel-based
Grav: Open-source flat-file CMS
Craft CMS: Database-driven, similar target audience
ProcessWire: PHP CMS with more features
WordPress: Larger ecosystem, more accessible

Kirby excels for designers and developers who value simplicity, beautiful tools, and complete control.