[Head-to-head comparison]

Hygraph vs Contentful

Hygraph vs Contentful for structured marketing content, comparing a GraphQL schema with entries, preview and an optional Studio canvas.

Kalle Bertell

By Kalle Bertell

Direct answer

Choose Hygraph when a generated GraphQL content API and modular components are the model you want to query. Choose Contentful when structured entries, field locales and scripted content-type migrations matter, with a visual canvas only if Studio is licensed. Both are managed SaaS. Editors become more independent only after preview, roles and any composition tool are actually in place.

Choose Hygraph when

  • A GraphQL-native content API

    Queries and mutations follow the schema, including relations, unions, components and localized fields.

  • Modular components in the model

    Editors choose among block types on a component field without a separate page-canvas license.

  • Preview included on the free plan

    Hobby lists live preview. The frontend still has to serve drafts and allow Hygraph to frame it.

Choose Contentful when

  • Reusable structured entries

    Content types and references let editors reuse an entry across pages and channels once the model is in place.

  • Scripted model migrations

    Developers can move content-type changes with CLI migrations and environment merges instead of editing production by hand.

  • A licensed visual canvas

    Drag-and-drop composition is available with Contentful Studio and registered components, not in the default entry form.

Consider neither when

  • Self-hosted content backend

    Contentful says the platform is not offered for you to host. Hygraph pricing does not describe a self-hosted content API either.

  • Visual pages with no add-on and no frontend work

    Contentful’s canvas needs Studio. Hygraph’s preview needs a draft frontend and, for click-to-edit, the Preview SDK.

  • Custom roles on the smallest plan

    Contentful custom roles require Premium. Hygraph custom roles are listed only on Enterprise.

Criterion-by-criterion comparison

How we evaluate platforms

Marketer autonomy

Both let editors change structured fields, and both keep page assembly behind extra setup. Contentful’s assembly path is Studio. Hygraph’s is modular components plus preview.

Hygraph

Editors fill models and allowed components

Editors add entries, localized fields and modular components the schema already allows. New component types, roles and preview setup stay with developers. Custom permissions are an Enterprise control.

Plan considerations: Hobby includes two standard roles and Growth four. Custom roles, up to 30, are listed only on Enterprise.

View sources (2)

Contentful

Entry editing; page assembly is extra

Editors can update structured fields, references and localized values in the web app. Assembling pages from design-system components depends on Studio setup and the role granted to that editor.

Plan considerations: Free spaces include administrator and editor roles. Custom roles that narrow publishing or locales require Premium.

View sources (3)
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.
  • Contentful Experiences: Describes the drag-and-drop canvas, registered design-system components and field-level locales.
  • Contentful space roles: Lists default roles and states that custom, translator and freelancer roles require Premium.

Choosing between them

Hygraph:

Fits if editors can publish with standard roles and the components already on the model.

Contentful:

Fits if entry editing is the job, or Studio and the role on the plan will cover layout changes.

Decide whether editors must change layout. If they must, check Studio on one side and the component model on the other.

Content modeling

Hygraph generates GraphQL from models, relations, unions and components. Contentful uses content types, fields, references and rich text, with a documented field cap.

Hygraph

GraphQL models, relations, unions and components

The schema builder defines models, components, enumerations, unions and relations, and the Content API follows that schema. A modular component lets editors choose among block types on one field.

Plan considerations: Hobby allows 20 models and 10 components. Growth allows 40 and 20. Taxonomies and variants are Enterprise.

View sources (3)

Contentful

Content types, fields, references and rich text

Teams model entries with up to 50 fields, rich text and references to other entries. The same model can be edited in the web app or changed with the management API and CLI migrations.

Plan considerations: Premium cross-space references allow three reference fields per type and cap how many entries can be linked.

View sources (3)
  • Contentful data model: Defines spaces, content types and up to 50 fields, including rich text and entry references.
  • Contentful references: Describes one-to-one and one-to-many entry references, including Premium cross-space references.
  • Contentful import and export: CLI export and import cover entries, assets, models and roles. Version history is not migrated.

Choosing between them

Hygraph:

Fits when the GraphQL schema, including modular components, is the model other channels will query.

Contentful:

Fits when content types and references, moved with the management API or CLI, are the model you want.

Model one page, one shared entry and one rich text field in both. Keep the shape that duplicates less.

Workflow and governance

Hygraph puts custom workflows and scheduling on Enterprise. Contentful’s workflow count, custom roles and grouped releases depend on the plan, and a Starter space lists workflows as unavailable.

Hygraph

Two stages by default; custom workflows are Enterprise

Projects include draft and published stages. Custom workflows can assign a role to each step and publish from a configured step. The pricing table places those workflows on Enterprise.

Plan considerations: Scheduled publishing is documented as Enterprise only. Growth lists 14 days of version history; Hobby lists none.

View sources (3)

Contentful

Roles and releases depend on the plan

Workflow count depends on the plan, and a Starter space lists workflows as unavailable. Custom roles are Premium, and Launch lists specific paid plans for grouped releases.

Plan considerations: Confirm current plan names. The Launch page still lists Team and Enterprise alongside Lite and Premium.

View sources (4)
  • Contentful workflows: Says workflows are available only on specific plans and limits one workflow to 20 steps.
  • Contentful space roles: Lists default roles and states that custom, translator and freelancer roles require Premium.
  • Contentful pricing: Free column and Starter quotas include two locales, API caps and no Starter workflows.
  • Contentful Launch app: Groups entries into releases and lists Team, Lite, Enterprise and Premium as eligible plans.

Choosing between them

Hygraph:

Fits if two stages are enough, or Enterprise workflow and scheduling are already priced.

Contentful:

Fits if the space plan includes the workflows and release tools you listed, which a free space does not.

Check the current plan name on both pricing pages. Workflow availability is a contract detail, not a default.

Localization and multisite

Both support field locales and cap them on lower plans. Contentful also documents separate entries, types or spaces when markets publish independently.

Hygraph

Per-field locales with a tight plan cap

Localized fields keep translations on the same entry, and locales are configured per environment. The docs describe this field model. They do not describe a separate site product.

Plan considerations: Hobby includes two locales, Growth three and Enterprise up to 80. More locales need an upgrade or add-on.

View sources (3)

Contentful

Field locales, with other structures optional

Field-level locales are built in. Entry, content-type and space copies support independent publishing, and those separated approaches do not get straightforward fallback.

Plan considerations: The free plan lists two locales. Translator roles require Premium, and locale-based publishing is described as an Enterprise-space feature.

View sources (3)

Choosing between them

Hygraph:

Fits when two or three locales, or an Enterprise cap up to 80, covers the languages on one entry.

Contentful:

Fits when field locales are enough, or you are prepared to split entries or spaces and lose straightforward fallback.

Choose the publishing boundary first. A shared entry and an independent market space are different projects.

Developer experience

Hygraph combines the schema builder with Management API permissions. Contentful adds CLI migrations, environment merges and management APIs, and you still own the preview SDK.

Hygraph

Schema builder with a Management API

Developers define the schema in Studio, and the Content API updates with it. Management API permissions also cover schema, environments and webhooks for authorized tokens. Preview remains frontend work.

Plan considerations: Hobby includes one environment and Growth two, so isolated schema testing starts on Growth. Enterprise lists up to ten.

View sources (3)

Contentful

CLI migrations, environments and management APIs

Developers script content-model changes, merge environments and call management APIs. The team still owns the frontend, the Live Preview SDK and any custom editor extensions.

View sources (4)
  • Contentful import and export: CLI export and import cover entries, assets, models and roles. Version history is not migrated.
  • Contentful Merge app: Compares content-type changes between environments and can export a migration script.
  • Contentful API basics: Separates delivery, preview, management, Images and GraphQL APIs, including separate EU hosts.
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.

Choosing between them

Hygraph:

Fits teams that want schema and content API in one managed project, with extra environments from Growth.

Contentful:

Fits teams that want scripted content-type migrations and environment merges as the change process.

Walk through one schema change in each tool, from a branch or environment to production, before you choose.

APIs and extensibility

Hygraph centers GraphQL queries and mutations, plus webhooks. Contentful documents delivery, preview, management and GraphQL APIs, plus webhooks and separate EU hosts.

Hygraph

GraphQL queries, mutations, drafts and webhooks

Clients query and mutate entries through GraphQL, including localized fields and a draft stage when the token allows it. Webhooks can notify your systems on publish and other content actions.

Plan considerations: Hobby allows five webhooks and no remote sources. Uncached limits are 5 requests per second on Hobby and 25 on Growth.

View sources (3)

Contentful

Delivery, preview, management, GraphQL and webhooks

Published content uses the delivery and GraphQL APIs, drafts use the preview API, and the management API plus webhooks cover writes and events. EU customers have separate API hosts.

View sources (2)
  • Contentful API basics: Separates delivery, preview, management, Images and GraphQL APIs, including separate EU hosts.
  • Contentful webhooks: Webhooks call a public endpoint for selected content events from the web app or management API.

Choosing between them

Hygraph:

Fits clients that will use the generated Content API, including a draft token for preview.

Contentful:

Fits when you need the split between delivery, preview and management APIs, including the EU hosts.

Call the draft and published endpoints you will use in production and compare tokens, hosts and limits.

Hosting and operations

Both vendors run the content platform and leave the website to you. Hygraph names EU, US and APAC on lower plans. Contentful documents US or EU residency on AWS.

Hygraph

Managed API and Studio in shared regions

Hygraph operates the content API, Studio and asset CDN. Hobby and Growth list three shared regions: EU, US and APAC. Your team still hosts the website and its preview frontend.

Plan considerations: Enterprise lists more shared regions and dedicated clusters. The pricing page does not describe a self-hosted content API.

View sources (2)

Contentful

Managed AWS platform; frontend stays with you

Contentful runs the content APIs, editor and CDN on AWS, with US or EU residency options. Your team still hosts the website, builds and application runtime.

View sources (1)

Choosing between them

Hygraph:

Fits when one of Hygraph’s shared regions is the residency you need for the API, Studio and assets.

Contentful:

Fits when Contentful’s US or EU AWS regions, with separate EU API hosts, match the residency review.

Put the required region in the decision. Do not assume the default region is the one you need.

Security and governance

Hygraph states SOC 2 Type 2 and ISO 27001 certified infrastructure, with SSO and audit logs on Enterprise. Contentful documents ISO 27001 and SOC 2, with SSO and custom roles varying by plan.

Hygraph

SOC 2 Type 2; advanced controls are Enterprise

Hygraph states SOC 2 Type 2 and GDPR compliance, with hosting on ISO 27001 certified infrastructure. SSO, custom permissions, audit logs and an uptime SLA are listed with Enterprise.

Plan considerations: Disaster-recovery backups exist on all plans. In-app one-click recovery is an Enterprise add-on, and audit log retention there is 90 days.

View sources (3)

Contentful

ISO 27001 and SOC 2; controls vary by plan

Documented assurance includes ISO/IEC 27001:2022, SOC 2 Type 2, encryption and daily backups on AWS. Confirm SSO, SCIM, embargoed assets and the uptime SLA on the plan you will buy.

Plan considerations: Custom roles are Premium. EU residency is a documented customer option with separate API hosts, not the default US regions.

View sources (3)

Choosing between them

Hygraph:

Fits if the stated assurance is enough and Enterprise SSO, audit logs and the SLA are quoted when required.

Contentful:

Fits if ISO 27001 and SOC 2 Type 2 match the review, after you confirm SSO, SCIM and the uptime SLA on the plan.

Ask both vendors for the report and the control list that apply to the region and plan you will use.

Pricing and cost drivers

Hygraph prices Hobby and Growth by entries, seats and API use, and counts assets as entries. Contentful prices spaces, users and API calls, and licenses Studio separately.

Hygraph

Free Hobby, then seats, entries and API use

Hobby is free, with 1,000 entries, three seats and hard API and traffic caps. Growth starts at $199 per month and can bill overages. Uploaded assets also count toward the entry limit.

Plan considerations: Growth overages are USD 0.20 per 10,000 API operations and per 1 GB of asset traffic. Hobby blocks further use instead.

View sources (1)

Contentful

Spaces, users, API calls and add-on products

Free includes one Starter space, 10 users and hard API and bandwidth caps. Lite raises the user cap and can add one space; Premium prices spaces and users by contract, and Studio is licensed separately.

Plan considerations: Starter spaces list 25 content types, two environments, 10,000 records, two locales and no workflows. Confirm current overages before you budget.

View sources (3)

Choosing between them

Hygraph:

Fits if the entry cap, with assets included, and the Growth overage rate match the forecast.

Contentful:

Fits if the space and user plan covers the project, and Studio is either unnecessary or budgeted on its own.

Add Studio, locales and overages to the Contentful number before comparing it with Growth.

Migration and exit

Hygraph’s documented outbound path is the Content API. Contentful’s CLI can export and import entries, assets and content types, and version history starts fresh.

Hygraph

Read content out through the Content API

Hygraph documents offsite copies by querying the Content API. Relations, locales, assets and the frontend that renders them still need a separate transfer. In-app restore is a recovery tool, not an exit format.

Plan considerations: Growth keeps 14 days of version history and Enterprise up to a year, so older versions may be unavailable.

View sources (2)

Contentful

CLI export and import; history is not copied

The CLI can export entries, assets, content types, roles, tags and webhooks, then import them into another space. Version history starts fresh, and your frontend, URLs and preview code still need a separate plan.

Plan considerations: Drafts are excluded unless include-drafts is set. Embargoed assets need the download and upload options.

View sources (1)

Choosing between them

Hygraph:

Fits if querying the content out, including relations and locales, is a sufficient exit plan.

Contentful:

Fits if a CLI export between spaces is the copy you want, knowing drafts and history need explicit handling.

Export one space or project sample, including an asset and a draft, and see what each tool actually writes.

Marketing website fit

Both fit structured marketing sites when preview is funded. Contentful adds a visual canvas only with Studio. Hygraph stays with components and a draft iframe.

Hygraph

Structured pages once a preview is connected

Modular components can represent campaign sections, and Live Preview shows the draft frontend after save. The website must render that schema and allow Hygraph to embed it. The setup guide does not describe a freeform canvas.

View sources (2)
  • Hygraph content modeling: Modular components are described for composing pages from blocks such as a hero or feature list.
  • Hygraph live preview: Live Preview shows the draft frontend beside the entry after the editor saves.

Contentful

Fits structured sites when preview is funded

Marketing pages work when entries, references and a preview URL match the design system. Visual composition is practical only after Studio components and roles are set up.

View sources (3)
  • Contentful data model: Defines spaces, content types and up to 50 fields, including rich text and entry references.
  • Contentful live preview: Side-by-side preview needs a content preview; live updates and inspector mode need the SDK.
  • Contentful Experiences: Describes the drag-and-drop canvas, registered design-system components and field-level locales.

Choosing between them

Hygraph:

Fits pages that can be modular components and a preview that refreshes after save.

Contentful:

Fits structured entries now, and visual composition later only if Studio components and roles are set up.

If editors must drag sections around, trial Studio against Hygraph’s component field before you call either one a page builder.

Visual editing and preview

Both can show a draft preview after integration. Contentful’s drag-and-drop canvas needs Studio. Hygraph’s click-to-edit needs the Preview SDK, and the iframe refreshes on save.

Hygraph

Side-by-side preview that refreshes on save

Live Preview loads your frontend beside the entry and refreshes after a save. Click-to-edit needs the Preview SDK and field attributes. Updates while typing stay off unless that option is enabled.

Plan considerations: Each model needs a Preview widget, a draft token and frame-ancestor headers that allow Hygraph.

View sources (2)
  • Hygraph live preview: Live Preview is an iframe that refreshes on save and needs a draft-stage token.
  • Hygraph click to edit: Click-to-edit needs the Preview SDK and data attributes, and live typing updates are optional.

Contentful

Live preview; visual canvas needs Studio

Side-by-side preview works after a preview URL is configured. Live updates, click-to-field editing and drag-and-drop Experiences need the relevant SDK, and Experiences also need a Studio license.

Plan considerations: A Studio license enables Experiences in up to three spaces unless additional spaces are purchased.

View sources (3)

Choosing between them

Hygraph:

Fits when a side-by-side draft preview is enough and you do not need a separate canvas license.

Contentful:

Fits when you will integrate the Live Preview SDK and, if you need a canvas, fund Studio.

Prototype the preview before you compare canvases. The default editor in both products is still a structured form.

Recommendations by use case

[Marketing website]

Start from the editing surface

Choose Hygraph when components and a draft preview are enough. Choose Contentful when entries fit the model and Studio is funded for layout.

[Structured content platform]

Favor the API you will query

Choose Hygraph for a generated GraphQL schema. Choose Contentful when content types, references and the delivery API are the standard you want.

[Multilingual multisite]

Match how markets publish

Choose either for field locales inside the plan cap. Choose Contentful if markets must publish from separate spaces, and accept the fallback limit.

[Ecommerce]

Link the catalog you will query

Choose Hygraph when product content is GraphQL and a remote source is available on the plan. Choose Contentful when linked entries across the delivery API are the model.

[Enterprise governance]

Validate the contract

Custom roles, workflows and SLAs are plan-specific on both. Compare the quote for the space or project you will run.

[Small team]

Stay inside the free caps

Hygraph Hobby and a Contentful Starter space are both narrow. Pick the one whose entry, locale and role limits match the first site, and budget the upgrade early.

[Self hosted control]

Choose neither for a private backend

Both are managed platforms. A requirement to host the content API yourself points away from this pair.