UnfoldCMS vs Hygraph

Hygraph (formerly GraphCMS) sells itself on one feature: federated GraphQL across content sources. It's a real differentiator — no other headless CMS does cross-source GraphQL as cleanly. It's also priced like an enterprise data platform, with a Free tier that's a demo and paid tiers that start at $299/month and climb fast.

This page compares UnfoldCMS and Hygraph head-to-head: pricing, the GraphQL story, hosting model, and where each one fits.

TL;DR: Hygraph is a GraphQL-first headless CMS built around content federation — pulling content from multiple sources into a single API. UnfoldCMS is a self-hosted Laravel + React CMS that ships REST and GraphQL endpoints, with a fixed content model and one-time pricing. Hygraph wins if your project depends on federating Hygraph + commerce + DAM + custom microservices into one GraphQL schema. UnfoldCMS wins if you want a headless CMS without the SaaS bill, or if "GraphQL federation" sounds like a problem you don't have.

Quick Comparison

What Hygraph Actually Is

Hygraph started as GraphCMS — the first headless CMS built API-first around GraphQL. The rebrand to Hygraph in 2022 came with a strategic pivot: from "GraphCMS for content" to "Hygraph for content federation." The platform now positions itself as a hub that federates content from multiple sources (your CMS, your commerce platform, your DAM, your custom data) into a single GraphQL schema your frontend can query.

For a specific kind of enterprise customer, this is genuinely useful. If your stack includes Shopify + Algolia + a custom product database + editorial content, and your frontend has to stitch all of that into one query, Hygraph's federation layer saves real work.

For most projects — marketing sites, blogs, product content sites, even small e-commerce — federation is a problem you don't have. You have content. You want a CMS for it. UnfoldCMS is for the "you have content, you want a CMS" case.

The Pricing Reality

Hygraph's pricing has changed multiple times since 2022. The current tiers (hygraph.com/pricing, May 2026) are roughly:

• Free — Real free tier, but with hard limits: 1 project, ~250k API calls/month, 5 locales, basic features. Useful for evaluation, not production.
• Growth — $299/month. Higher API limits, more locales, more roles, role-based permissions.
• Scale — $999/month. Significantly higher limits, advanced features, priority support.
• Enterprise — Custom pricing, typically $2,499+/month with SLAs, custom contracts, dedicated infrastructure.

The number that breaks teams: API call metering. Every preview render, every content fetch, every cache miss counts against your tier. Teams that aggressively cache rarely hit limits. Teams that don't watch their bills carefully and get surprised every month.

"We picked Hygraph for the GraphQL federation. Two years in, we use maybe 10% of that feature and pay $999/month. We could've shipped on Strapi for $0." — paraphrased from r/headlesscms, 2024

UnfoldCMS pricing:

No monthly fees. No per-seat pricing. No API metering. Your viral campaign is your hosting provider's problem to handle, not a renewal conversation with Hygraph sales.

5-year cost comparison (single project, mid-tier usage):

For teams that actually need GraphQL federation, the cost may be justified. For teams that picked Hygraph because it had GraphQL on the homepage, the math stops working at year two.

The GraphQL Question

This is the real reason teams pick Hygraph. The platform is GraphQL-first in a way most competitors aren't — schema is generated from your content model, federation is built in, the GraphQL playground is polished, and the type safety story is strong if you're using TypeScript codegen.

Be honest with yourself: if your project genuinely needs to federate content from Hygraph + commerce + DAM + custom services into a single GraphQL endpoint, Hygraph's federation product is the cleanest implementation in the headless CMS space. That's a real differentiator.

UnfoldCMS exposes GraphQL too — but as one API option alongside REST. It's not federated. It queries the UnfoldCMS database. If you need to combine UnfoldCMS content with Shopify products in a single query, you build a thin GraphQL gateway in front (Apollo, Hasura, or a small Node service). For most projects, this is fine. For projects with 5+ content sources that genuinely need federation, Hygraph saves work.

The trade-off question: do you need federation, or do you need GraphQL? They're different things, priced differently. Most teams need GraphQL. Far fewer need federation.

Where Hygraph Wins

A fair comparison admits where the other side is genuinely better. Hygraph wins in three places:

Content federation. Already covered. Hygraph's federation layer — pulling content from multiple sources into a single schema — has no real competitor in the headless CMS space. If federation is a hard requirement, Hygraph is the right tool.

GraphQL polish. The schema is well-designed, the playground is sharp, the codegen story works, and the type safety with TypeScript is mature. UnfoldCMS's GraphQL is functional but doesn't have the same depth of tooling around it.

Localization at scale. Hygraph supports many locales with stage-based publishing (draft, published, archived per locale). For multi-region marketing teams running 20+ language versions, the localization product is mature. UnfoldCMS does NOT ship multi-language content today. If you need 5+ locales with stage-based publishing, Hygraph is the right tool — UnfoldCMS is for projects with one primary language.

If you're running a multi-region product launch with federated content and 20+ locales, Hygraph's feature depth is real. The price is real too.

Where UnfoldCMS Wins

One-time price. This is the biggest one. Hygraph's $299–$2,499+/month bills compound fast. UnfoldCMS Pro at $99 once is one month of Hygraph Growth. The 5-year savings vs Growth alone is roughly $16,900.

Self-hosted ownership. Hygraph is SaaS-only. Your content lives on their servers. UnfoldCMS runs on your infrastructure — your data, your country, your terms. GDPR compliance is a hosting decision, not a vendor's contract clause. Export to standard SQL anytime.

No API metering. Hygraph counts every API request against your tier. UnfoldCMS doesn't meter anything. Your traffic is your hosting provider's concern, not a CMS bill.

Includes a frontend. Hygraph is API-only — you build and host a Next.js, Nuxt, or Astro frontend separately. UnfoldCMS ships with two themed frontends (Aurora, Default) that handle marketing sites, blogs, and product pages out of the box. The headless API is still there if you want it.

Modern stack. Laravel 12 + React 19 + TypeScript + Inertia 2 + shadcn/ui. The admin is built on 50 shadcn/ui components in production — fork-and-modify, not vendor-locked widgets. We covered the broader Laravel + React + shadcn/ui stack story for context.

No vendor lock-in. Leaving Hygraph means rebuilding your content model elsewhere — the schema lives in their dashboard, not your repo. Leaving UnfoldCMS means taking your SQL dump and Blade templates with you. Source-available CMS plus owned database equals exit-friendly architecture.

Developer Experience

Hygraph's developer story is strong if your team is GraphQL-first. The schema is auto-generated, the playground is excellent, and the SDK story for Next.js, Nuxt, and SvelteKit is mature. The friction shows up in three places:

API metering anxiety. Every preview render counts. Every cache miss costs. Teams that don't aggressively cache hit tier limits and get forced upgrades. The mental overhead of "is this query going to surprise us at month-end" is real.

Schema lives in the dashboard. You design content types in Hygraph's UI, not in version-controlled config files. Schema changes happen in production directly unless you're disciplined about staging environments. Teams that want config-as-code for their content schema find this awkward.

No local development. You can't run Hygraph locally. Every dev environment touches the production API (or a staging environment). This is fine for some teams and frustrating for others.

UnfoldCMS runs on your machine. Content model lives in Laravel migrations — version-controlled, reviewable, deployable. Local development uses the same stack as production. We covered the developer-friendly CMS features that drive these trade-offs.

If you're a GraphQL-first team that values federation, Hygraph's DX wins. If you value config-as-code, local dev parity, and no API metering, UnfoldCMS wins.

Who Should Choose Hygraph

• Enterprises federating content from 5+ sources (CMS + commerce + DAM + custom services) into a single GraphQL schema
• Multi-region brands running 20+ locales with stage-based publishing workflows
• Teams with budget for $299–$2,499+/month CMS spend that's already approved
• GraphQL-first stacks where the federation layer saves real engineering work
• Projects where SaaS hosting is a feature, not a constraint

Who Should Choose UnfoldCMS

• Agencies and small businesses paying $299+/month for Hygraph who don't actually use the federation feature
• Developers on PHP/Laravel stacks who want a CMS that fits their existing tools
• Teams that need self-hosted ownership for GDPR or data sovereignty reasons
• Projects where API metering anxiety is a recurring problem
• Anyone running 3+ sites who can't justify $299+/month per project

If you're moving from WordPress and considering Hygraph as the next stop, ask yourself: do you need GraphQL federation across multiple sources, or do you need a CMS with a GraphQL API? Both are valid answers — they cost very different amounts.

For more comparisons, see how UnfoldCMS stacks up vs Contentful (the other enterprise-headless option), vs Sanity, vs Payload, vs Strapi, vs Storyblok, vs Ghost, vs Directus, vs Webflow, or vs WordPress.

Migration: Hygraph → UnfoldCMS

Hygraph-to-UnfoldCMS migration is mechanical for content-driven sites. Hygraph exposes content via the Management API and supports schema export through their CLI. The federation layer doesn't transfer — that's by design, since federation is the feature you're leaving — but the content itself migrates cleanly.

Typical migration steps:

1. Export Hygraph content via the Management API or hygraph schema export
2. Map each Hygraph model to a UnfoldCMS content type — most blogs, pages, and product catalogs map 1:1
3. Convert Hygraph rich-text fields (proprietary structured format) to UnfoldCMS markdown or HTML
4. Import via UnfoldCMS REST API or direct database import
5. Mirror media assets from Hygraph's CDN to UnfoldCMS media library
6. If you used federation, stand up a thin GraphQL gateway (Apollo, Hasura) for any non-CMS sources you still need to combine
7. Set up redirects if URL patterns change

Most projects with under 5,000 entries migrate in a half-day. Hygraph projects with deep federation, custom field types, and many locales take longer.

Migration Service

If you'd rather not do it yourself, we offer two options:

Migration Starter — $149 A 30-minute call to map your Hygraph schema to UnfoldCMS content types, plus a written migration plan you can hand to a developer or follow yourself. Includes federation-replacement architecture advice if you were using that feature.

Migration Concierge — $499 Done-for-you migration of one project: up to 10,000 entries, all media assets, content model mapping, rich-text conversion, and a post-migration review call. You provide Hygraph API access; we deliver a live UnfoldCMS installation.

Both services include a 30-day guarantee — if something doesn't transfer cleanly, we fix it.

Trust Block

Who this is for: Developers and teams paying $299–$2,499+/month for Hygraph who don't actually need GraphQL federation and want self-hosted ownership without the recurring bill.

What it replaces: Hygraph Growth ($299/mo), Scale ($999/mo), or Enterprise ($2,499+/mo).

What it costs: UnfoldCMS Pro license — $99 one-time. Agency tier ($999 one-time) for unlimited domains.

What happens after you buy:

1. Download the installer and run composer install — live in under 5 minutes on any PHP host
2. Map your Hygraph models to UnfoldCMS content types via the migration guide or book the Migration Starter call
3. Point your frontend at the UnfoldCMS REST or GraphQL API — same headless pattern, different endpoint

FAQ

Is UnfoldCMS GraphQL-first like Hygraph? UnfoldCMS exposes GraphQL but isn't GraphQL-first the way Hygraph is. The primary API is REST; GraphQL is one option alongside it. If your stack is built entirely around GraphQL with a federation layer, Hygraph's product is more mature. If you just need a GraphQL endpoint for your CMS content, UnfoldCMS handles that fine.

Can I self-host Hygraph? No. Hygraph is SaaS-only — content lives on their servers. There is no self-hosted option. UnfoldCMS runs on your hardware, in your country, under your control.

What is GraphQL federation and do I need it? Federation means combining multiple GraphQL APIs into a single schema your frontend can query. If your site pulls from a CMS + commerce + DAM + custom services and you want one GraphQL endpoint for the frontend, federation saves work. Most projects (single content source, marketing sites, blogs, product content) don't need it. If you're not sure if you need it, you probably don't.

How does Hygraph pricing compare for an agency running 5 client sites? Hygraph charges per project. Five projects on Growth tier is $1,495/month minimum — $17,940/year. UnfoldCMS Agency is $999 once for unlimited domains plus your hosting. Over 5 years, the difference is meaningful.

What about API call metering? Hygraph meters every API request against your tier. UnfoldCMS doesn't meter anything — your traffic is your hosting provider's concern. For sites with significant preview rendering, cache misses, or build pipelines that hit the CMS, the difference adds up.

Is the localization story comparable? Hygraph has more mature localization at large scale (20+ locales with stage-based publishing). UnfoldCMS does NOT ship multi-language content today. For any locale-count project, Hygraph leads — UnfoldCMS is for projects with one primary language.

What happens to my content if I cancel Hygraph? Hygraph supports content export but the schema and federation configuration live in their dashboard — you lose those when you leave. With UnfoldCMS, your content lives in your database. Export to SQL anytime, take it anywhere.

Is UnfoldCMS open source? UnfoldCMS is source-available under a commercial license — full source, modify and self-host without restriction, but it's not OSS in the MIT sense. Hygraph is closed-source proprietary SaaS. Neither is fully open source like Strapi or Ghost.

Methodology

Hygraph pricing data is from hygraph.com/pricing as of May 2026. Tier limits, API call caps, and per-project pricing reference Hygraph's published pricing page and community discussions on r/headlesscms, Hacker News, and Indie Hackers (2023–2025). Federation feature analysis is based on Hygraph's product documentation. UnfoldCMS pricing is from /pricing. Feature comparison is based on direct product testing of both platforms and review of each vendor's official documentation.

Try UnfoldCMS

If UnfoldCMS sounds like the right fit, the live demo takes about 90 seconds — browse the admin, edit a post, switch themes without installing anything. Pricing is one-time and all tiers include the full source. Questions about migrating from Hygraph? Contact us — we'll scope it honestly before you commit, including the federation-replacement conversation if that applies.

If Hygraph is the right answer for your project, that's a fine call too. Both products serve different audiences.

Looking at other options? See how UnfoldCMS compares to Contentful, vs Sanity, vs Payload, vs Strapi, vs Storyblok, vs Ghost, vs Directus, vs Webflow, or vs WordPress.

Related: CMS for SaaS marketing sites, migrating from Contentful, or browse all CMS comparison guides.