Hygraph vs Contentful

Strong content types with references. Lacks native union fields, workarounds need multiple reference fields.

GraphQL-native schema with union types and polymorphic relations. Content Federation adds external data sources.

Content types can reference each other for reuse but there's no native block primitive. Rich Text embedded entries help.

Component models embed across content types. Schema-first reuse is straightforward for GraphQL-experienced developers.

Built-in validators for required, range, size, and regex. Custom validators need a UI extension to configure.

Basic required, unique, and regex validators. Advanced custom validation is limited compared to alternatives.

The web app is polished and familiar, editors with any CMS background can publish independently without developer help.

The editor is functional but complex. Editors need to understand GraphQL-style relationships before working efficiently.

Live preview requires developer config of the Preview API. No out-of-the-box visual editor available.

Preview via configurable URLs. No live preview panel, editors see changes after saving. Developer setup required.

Draft and published states built in. Tasks and comments need Teams+ plans. Approval chains require external tooling.

Custom content stages are configurable. Approval workflows with notifications are available on paid plans.

Media Library handles uploads, tagging, and image API transforms. No native AI cropping or focal points.

Handles uploads and basic transforms via the built-in API. Less capable than alternatives.

No simultaneous editing, last save wins. Conflicts between concurrent editors are not surfaced in real time.

Presence indicators show concurrent editors. Live sync available but less polished.

Roles support content type and tag-based access. Field-level permissions need Contentful Apps or higher plans.

The most granular here, field, locale, content stage, and model-level access designed for complex enterprise orgs.

Multi-locale is a core feature, every field localizes independently with locale-specific publishing states.

Multi-locale is first-class with field-level variants, locale-specific publishing, and multi-region API delivery.

Fallback is configurable in space settings and honored by the Delivery API when a translation is missing.

Native fallback configured in project settings with API-level enforcement. GraphQL returns fallback values automatically.

Comprehensive REST and GraphQL docs with a playground, official SDKs in JS, Python, and PHP, with TypeScript support.

Excellent GraphQL docs with a live playground, schema introspection, and generated TypeScript types.

Official Next.js and Astro starters for all major frameworks. The npm package is mature and well-documented.

Good framework examples. GraphQL-first means any client works easily, less framework tooling than alternatives.

The CMA supports migrations, bulk ops, and content type management. contentful-migration CLI is production-grade.

Full schema management via GraphQL mutations, types, relations, and fields all programmatically creatable.

Environment branching is a flagship feature. Each space supports multiple environments with full content promotion.

Branch schema and content for testing, then promote. Less polished than DatoCMS's one-click sandbox workflow.

Content via Fastly CDN with sub 100ms API response times. Images via Fastly Image Optimizer.

Global CDN with multi-region data residency on Enterprise. API performance is strong globally, especially for GraphQL.

Fully managed SaaS with zero infrastructure to configure or maintain. Scales transparently with usage.

Fully managed SaaS with zero infrastructure to configure or maintain.

Largest CMS marketplace, apps for Shopify, Salesforce, Cloudinary, and Imgix. Enterprise integrations are solid.

Focused on e-commerce, frameworks, and enterprise tools.

Active forums and a certification program. Less community content than others but strong enterprise support.

Enterprise-niche community. Active Discord with responsive support but fewer tutorials and third-party resources.