Hygraph vs Kirby
Hygraph is a closed-source headless CMS that runs on the vendor's cloud. Kirby is a closed-source traditional CMS that you host yourself. The table below sets them side by side on 28 features. They get a different status on 19.
- Hygraph Headless · Closed source · 13 of 28 built in
- Kirby Traditional · Closed source · 11 of 28 built in
Sources checked: Hygraph on 29 Sept 2026, Kirby on 29 Sept 2026. Plans and releases can change after those dates.
WAYF is an official Payload partner and top contributor. Every platform in the table is classified by the same published definitions, and each answer lists the vendor page it came from.
Feature comparison
| Platform | | |
|---|---|---|
| Overview | ||
| What it is | Hosted headless CMS run by Hygraph, formerly GraphCMS. Serves content over a GraphQL API and can pull in data from remote REST and GraphQL sources. | File-based PHP CMS with a configurable editing Panel. Content lives in text files on your own server, under a paid per-site licence. |
| Edition compared The product and release each column describes. | Hygraph SaaS, Hobby, Growth and Enterprise plans SaaS, continuously updated | Kirby 5. Kirby 6 is in alpha. Version 5.6.0, released 16 Sept 2026 |
| Vendor | Hygraph (formerly GraphCMS) hygraph.com | Content Folder GmbH & Co. KG getkirby.com |
| Licence | Closed source Proprietary | Closed source Proprietary, source available |
| Hosting | No self-hosting Vendor cloud Shared regions on every plan. Dedicated clusters on Enterprise. | Self-hosting No vendor cloud |
| Built with | Hosted SaaS with a GraphQL Content API | PHP, Vue for the Panel |
| Database | Managed by Hygraph | Flat files, no database required |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | Free to start Hobby free. Growth from $199 per month. Enterprise on request. | No free option Basic €99 per site if revenue is under €1M. Enterprise €349 per site. Both include 3 years of updates. |
| Content modelling | ||
| Content model in code You define content types in files in your repository, review them like any other code and apply them from there. Imperative migration scripts alone count as limited. | Limited Management SDK applies schema changes from code. No declarative schema files. 2 | Built in Blueprints are YAML files in site/blueprints. 5 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Built in 1 | Not available You edit blueprints as files. The Panel has no schema editor. 5 |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Built in Components in modular fields: 10 on Hobby, 20 on Growth. 1 | Built in Blocks and Layout fields. 6 |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Built in Field-level locales: 2 on Hobby, 3 on Growth, up to 80 on Enterprise. 1 | Built in Multi-language content is built in. 7 |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Built in Resize, crop and format conversion by URL or GraphQL argument. 4 | Built in Thumbs with resize, crop and format conversion. 8 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Not available Content API is GraphQL only. 3 | Built in Authenticated REST API. The official KQL plugin serves headless queries. 910 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Built in 3 | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Built in 5 on Hobby, 10 on Growth. 15 | Not available PHP hooks only. No webhook settings. |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Not available | Built in PHP templates and snippets. |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Built in DRAFT and PUBLISHED stages on every plan. 1 | Built in Page drafts. Kirby 5 stores unsaved changes apart from the live version. 4 |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Paid tier Scheduled publishing on Enterprise. 17 | Not available |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Paid tier 14 days on Growth, up to 365 on Enterprise. None on Hobby. 1 | Not available Kirby 5 keeps the live version and one set of changes. No revision history. 4 |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Built in 1 | Built in Preview view renders unsaved changes, with shareable links. 4 |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Built in Click to Edit via the Hygraph Preview SDK opens the field in Studio. 6 | Not available Preview view compares versions. No click-to-edit. 4 |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Paid tier Custom Workflows, up to 10, on Enterprise. 113 | Not available Fixed page statuses: draft, unlisted, listed. 11 |
| Content releases Editors group changes across several entries and publish them together as one release. | Paid tier Releases on Enterprise. 7 | Not available |
| Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. | Not available Collaborator View shows who else is in an entry. 9 | Not available Content locking stops two editors changing one page at once. 320 |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Paid tier Up to 30 custom roles on Enterprise. Hobby has 2 standard roles, Growth 4. 1 | Built in Roles are user blueprints with permissions. 12 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Not available Permissions scope by model, locale, stage, environment and condition. 8 | Not available Only by loading different blueprints per role in custom code. 13 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Paid tier Enterprise. 1 | Not available No first-party SSO. Community OAuth plugins exist. |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Paid tier Enterprise, 90-day retention. 1 | Not available |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Paid tier Multitenancy on Enterprise. 1 | Not available One site per installation. |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in App Framework for custom fields, sidebars and pages. 12 | Built in Panel plugins add fields, sections, views and areas. 15 |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Hygraph Marketplace. 12 | Built in Official plugin directory at plugins.getkirby.com. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Not available | Plugin or add-on Paid DreamForm plugin by tobimori. 17 |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Not available | Limited Frontend login is built in. Sign-up needs custom code. 14 |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Built in AI Assist on every plan, with a monthly AI token allowance. 110 | Not available No first-party AI. Kirby Copilot is a paid third-party plugin. 18 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Built in Global endpoint at mcp.hygraph.com and per-project endpoints. Also a Claude connector. 111415 | Not available Third-party Kirby MCP plugin by Bruno Meilick. 19 |
Hygraph sources
Checked 29 Sept 2026. Hygraph SaaS, Hobby, Growth and Enterprise plans.
- Hygraph pricing
- Hygraph docs: Management SDK overview
- Hygraph docs: API reference overview
- Hygraph docs: Asset transformations
- Hygraph docs: Webhooks
- Hygraph docs: Click to Edit setup
- Hygraph docs: Content releases
- Hygraph docs: Content permissions
- Hygraph blog: Introducing Collaborator View
- Hygraph blog: AI Assist is now generally available
- Hygraph docs: MCP server
- Hygraph Marketplace: Apps
- Hygraph docs: Content workflows
- Hygraph docs: Set up the MCP server
- Hygraph blog: MCP Connector for Claude (September 2026)
Kirby sources
Checked 29 Sept 2026. Kirby 5. Kirby 6 is in alpha..
- Kirby pricing
- Kirby releases
- Kirby 5 release overview
- Kirby 5: Preview your changes
- Kirby docs: Blueprints
- Kirby docs: Blocks field
- Kirby docs: Languages
- Kirby docs: $file->thumb()
- Kirby docs: REST API
- Kirby Query Language (KQL) plugin
- Kirby docs: Publishing workflow
- Kirby docs: Permissions
- Kirby cookbook: Extending permissions
- Kirby docs: Frontend login
- Kirby docs: Plugin extensions
- Kirby plugin directory
- DreamForm plugin
- Kirby Copilot plugin
- Kirby MCP plugin by Bruno Meilick
- Kirby docs: Content options (locking)
Considering more platforms? Compare Hygraph and Kirby with the rest of your shortlist in the CMS comparison tool.
Where they differ
Hygraph and Kirby get a different status on 19 of the 28 features and the same status on 9. Hygraph has 13 built in on its baseline edition, Kirby has 11. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
- Self-hosting
- Hygraph cannot be self-hosted. Kirby can be self-hosted.
- Vendor cloud
- Hygraph has a vendor-run cloud. Kirby has no vendor-run cloud.
- Free option
- Hygraph has a free option. Kirby has no free option.
Built in on Hygraph, a different answer on Kirby 6
- Content model in the UI Hygraph: Built in. Kirby: Not available.
- GraphQL API Hygraph: Built in. Kirby: Not available.
- Webhooks Hygraph: Built in. Kirby: Not available.
- Visual editing Hygraph: Built in. Kirby: Not available.
- AI writing assistant Hygraph: Built in. Kirby: Not available.
- Official MCP server Hygraph: Built in. Kirby: Not available.
Built in on Kirby, a different answer on Hygraph 4
- Content model in code Hygraph: Limited. Kirby: Built in.
- REST API Hygraph: Not available. Kirby: Built in.
- Renders the website Hygraph: Not available. Kirby: Built in.
- Custom roles Hygraph: Paid tier. Kirby: Built in.
Built in on neither, with different answers 9
- Scheduled publishing Hygraph: Paid tier. Kirby: Not available.
- Version history Hygraph: Paid tier. Kirby: Not available.
- Approval workflows Hygraph: Paid tier. Kirby: Not available.
- Content releases Hygraph: Paid tier. Kirby: Not available.
- Single sign-on Hygraph: Paid tier. Kirby: Not available.
- Audit log Hygraph: Paid tier. Kirby: Not available.
- Multiple sites Hygraph: Paid tier. Kirby: Not available.
- Form builder Hygraph: Not available. Kirby: Plugin or add-on.
- Site member accounts Hygraph: Not available. Kirby: Limited.
More comparisons
Full write-ups with worked examples and costs: Hygraph vs Payload.
Hygraph against other platforms
- Adobe Experience Manager vs Hygraph
- Contentful vs Hygraph
- Contentstack vs Hygraph
- CoreMedia Content Cloud vs Hygraph
- Craft CMS vs Hygraph
- DatoCMS vs Hygraph
- Decap CMS vs Hygraph
- Directus vs Hygraph
- Drupal vs Hygraph
- EmDash vs Hygraph
- FirstSpirit vs Hygraph
- Framer vs Hygraph
- Ghost vs Hygraph
- HubSpot CMS vs Hygraph
- Hygraph vs Instatic
- Hygraph vs Joomla
- Hygraph vs Keystone
- Hygraph vs Liferay DXP
- Hygraph vs Optimizely CMS
- Hygraph vs Payload
- Hygraph vs Prismic
- Hygraph vs Progress Sitefinity
- Hygraph vs Sanity
- Hygraph vs Sitecore
- Hygraph vs Squarespace
- Hygraph vs Statamic
- Hygraph vs Storyblok
- Hygraph vs Strapi
- Hygraph vs TYPO3
- Hygraph vs Umbraco
- Hygraph vs Wagtail
- Hygraph vs Webflow
- Hygraph vs Wix
- Hygraph vs WordPress
- Hygraph vs Xperience by Kentico
Kirby against other platforms
- Adobe Experience Manager vs Kirby
- Contentful vs Kirby
- Contentstack vs Kirby
- CoreMedia Content Cloud vs Kirby
- Craft CMS vs Kirby
- DatoCMS vs Kirby
- Decap CMS vs Kirby
- Directus vs Kirby
- Drupal vs Kirby
- EmDash vs Kirby
- FirstSpirit vs Kirby
- Framer vs Kirby
- Ghost vs Kirby
- HubSpot CMS vs Kirby
- Instatic vs Kirby
- Joomla vs Kirby
- Keystone vs Kirby
- Kirby vs Liferay DXP
- Kirby vs Optimizely CMS
- Kirby vs Payload
- Kirby vs Prismic
- Kirby vs Progress Sitefinity
- Kirby vs Sanity
- Kirby vs Sitecore
- Kirby vs Squarespace
- Kirby vs Statamic
- Kirby vs Storyblok
- Kirby vs Strapi
- Kirby vs TYPO3
- Kirby vs Umbraco
- Kirby vs Wagtail
- Kirby vs Webflow
- Kirby vs Wix
- Kirby vs WordPress
- Xperience by Kentico vs Kirby
Open the CMS comparison tool to put up to six platforms in one table.
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.