[Head-to-head comparison]

Hygraph vs Payload

Hygraph vs Payload for marketing websites, comparing a managed GraphQL studio with a TypeScript CMS you deploy.

Kalle Bertell

By Kalle Bertell

Direct answer

Choose Hygraph when the content API and Studio should be vendor-managed and editors can work from the generated schema. Choose Payload when the team will run the CMS, database and files as a TypeScript application they deploy. Hygraph does not document that self-hosted stack. Payload’s on-page visual editor is an enterprise feature, while Hygraph’s click-to-edit depends on the Preview SDK in your frontend.

Choose Hygraph when

  • No CMS process to operate

    Hygraph runs the API, Studio and asset CDN. You still host the website and the preview frontend.

  • GraphQL from the schema

    Models, relations and components are the Content API, including draft reads for a preview token.

  • Preview documented on Hobby

    The free plan lists live preview. It refreshes on save and needs your frontend to allow framing.

Choose Payload when

  • Self-hosted content storage

    The MIT-licensed app runs on your Node.js host. The database and file storage stay in your operations.

  • Code-defined content models

    Collections, fields and blocks live in the TypeScript config, so schema review happens in the application repository.

  • Drafts you configure

    Versions can store drafts, autosave and a scheduled publish time. Access rules decide who can read those drafts.

Consider neither when

  • A page builder with no engineering

    Hygraph still needs a frontend and preview route. Payload’s admin and blocks come from the config your team ships.

  • Approvals without an enterprise deal

    Hygraph custom workflows are Enterprise. Payload describes publishing approval workflows as an enterprise feature.

  • A standard hosted Payload stack

    Payload’s documented default is to host the app yourself. Enterprise can include vendor hosting, which is a separate contract.

Criterion-by-criterion comparison

How we evaluate platforms

Marketer autonomy

Hygraph editors fill the managed schema. Payload editors use an admin generated from the TypeScript config, and publishing rules are code.

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)

Payload

Admin follows the config developers ship

Editors create and publish documents in the generated admin, including blocks once those blocks exist. Changing fields, validation or who can publish means a config change.

View sources (2)
  • Payload blocks field: Stores mixed blocks, such as a page builder, each with its own schema in config.
  • Payload access control: Documents collection, global and field access functions, including locale-specific checks.

Choosing between them

Hygraph:

Fits if allowed components and roles in Studio cover the edits, with custom permissions on Enterprise.

Payload:

Fits if the admin can expose the blocks you ship, and a config change is an acceptable way to change permissions.

The editor is only as free as the last schema or config release. Plan that release path before launch.

Content modeling

Hygraph defines models in Studio and serves GraphQL. Payload defines collections, relationships and blocks in code, and that config generates the admin and APIs.

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)

Payload

Collections, fields and mixed blocks in code

The config defines collections, globals, relationships and blocks that editors can reorder. That same config generates the admin and the APIs.

View sources (2)
  • Payload blocks field: Stores mixed blocks, such as a page builder, each with its own schema in config.
  • Payload REST API: Generates CRUD routes from collections, including depth, locale and where queries.

Choosing between them

Hygraph:

Fits when editors and developers can share a hosted schema builder and the generated API.

Payload:

Fits when the content model should be reviewed like the rest of the TypeScript application.

Put the schema in the place your team already reviews changes. That is the practical difference here.

Workflow and governance

Hygraph’s custom workflows and scheduling are Enterprise. Payload can enable drafts and scheduled publish in code, and describes approval workflows as enterprise.

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)

Payload

Drafts and access are code; approvals are enterprise

You can enable versions, drafts, autosave and scheduled publish, then restrict drafts with access functions. Approval workflows are described on the enterprise page.

Plan considerations: Localized draft status is documented as beta. Test it before relying on per-locale publishing.

View sources (3)
  • Payload versions: Stores version history, diffs, restore, draft visibility and scheduled publishing when enabled.
  • Payload drafts: Drafts require versions and can autosave or schedule publish and unpublish events.
  • Payload enterprise: Lists visual editing, SSO, publishing workflows and vendor or self-hosted enterprise deployment.

Choosing between them

Hygraph:

Fits if two default stages are enough, or Enterprise workflow and scheduling are in the quote.

Payload:

Fits if code-level draft access and a scheduled time cover the process, without a packaged approval chain.

If you need a named approval chain, ask both vendors to point at the edition that includes it.

Localization and multisite

Hygraph caps locales by plan. Payload lists locales in config, with fallback on by default, and does not state a numeric cap. Per-locale publish is a beta option.

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)

Payload

Field locales in config, with fallback

Locales are listed in the Payload config and enabled per field. Fallback is on by default, and the docs state no limit on how many locales you add.

Plan considerations: Per-locale publish status is a beta option and is off unless you enable it.

View sources (1)
  • Payload localization: Configures locales in code, with fallback on by default and no documented locale cap.

Choosing between them

Hygraph:

Fits a small, known locale set that stays inside Hobby, Growth or a funded Enterprise cap.

Payload:

Fits when you will add locales in config and can test the beta if each locale must publish alone.

Treat Payload’s missing cap as flexibility you must operate, and Hygraph’s cap as a limit you must buy past.

Developer experience

Hygraph is a managed project. Payload is one TypeScript app for the admin, API and data, including migrations and deployment.

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)

Payload

One TypeScript app for admin, API and data

Developers own the Next.js app, config, migrations and deployment. Editors inherit the admin that config generates, including custom components the team chooses to build.

View sources (2)
  • Payload production deployment: Says Payload runs anywhere Next.js runs, and that you still provide a database and file storage.
  • Payload REST API: Generates CRUD routes from collections, including depth, locale and where queries.

Choosing between them

Hygraph:

Fits teams that want Studio and the Content API without running the CMS process.

Payload:

Fits teams that already operate Next.js and want the CMS config in that application.

Choose Payload if owning the app is the point. Choose Hygraph if operating a CMS process is the cost you want to remove.

APIs and extensibility

Hygraph exposes a GraphQL Content API and webhooks. Payload generates REST, GraphQL and a local API from the same config.

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)

Payload

REST, GraphQL and a local API from one config

Collections generate REST routes and a GraphQL endpoint. Queries can filter, select fields and populate relationships to the depth you request.

View sources (2)
  • Payload REST API: Generates CRUD routes from collections, including depth, locale and where queries.
  • Payload GraphQL API: Exposes a GraphQL API from the same config, by default at /api/graphql.

Choosing between them

Hygraph:

Fits external clients that should use the hosted GraphQL API, including draft tokens for preview.

Payload:

Fits application code that can call the local API in-process as well as REST or GraphQL.

If the website and CMS are one codebase, Payload’s local API matters. If they are separate, Hygraph’s hosted API does.

Hosting and operations

Hygraph operates the content platform in named cloud regions. Payload deploys wherever Next.js runs, and the database, files and email stay yours unless an enterprise host is contracted.

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)

Payload

You run the app, database and files

Payload deploys anywhere Next.js runs, including Vercel or your own servers. The database, permanent file storage and email provider remain your responsibility.

Plan considerations: Enterprise agreements can include Payload hosting. The documented default is to host the app yourself.

View sources (2)
  • Payload production deployment: Says Payload runs anywhere Next.js runs, and that you still provide a database and file storage.
  • Payload get started: States the MIT license, self-hosting on Node.js, and enterprise SSO, hosting and visual editing.

Choosing between them

Hygraph:

Fits when EU, US or APAC shared infrastructure, or an Enterprise region, is the residency model.

Payload:

Fits when the team will run the app, database and permanent file storage, or has an enterprise hosting contract.

A requirement to operate the database decides this criterion before the editor features do.

Security and governance

Hygraph states SOC 2 Type 2 and gates SSO and audit logs on Enterprise. Payload documents app-level auth and access control, with SSO as enterprise and compliance following your host.

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)

Payload

App-level controls; compliance follows your host

Payload documents HttpOnly cookie auth, CSRF checks and field-level access in the app you deploy. SSO is enterprise, and a SOC report depends on the host you choose.

View sources (2)
  • Payload security: Describes HttpOnly cookie auth, field access control, CSRF checks and enterprise SSO.
  • Payload SSO: Describes SAML and OAuth 2.0 sign-in as an enterprise feature.

Choosing between them

Hygraph:

Fits if you need the vendor’s SOC 2 statement and will buy Enterprise for SSO or audit logs.

Payload:

Fits if your own host’s compliance is the assurance model and app-level access control is enough.

Decide whether the compliance boundary is the vendor or your infrastructure. The products answer that differently.

Pricing and cost drivers

Hygraph sells plans with entry, seat and API caps. Payload’s CMS is MIT-licensed, so the cost is hosting plus any enterprise features you add.

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)

Payload

MIT app; you pay hosting and enterprise extras

The CMS is MIT-licensed and free to run. Budget the Node.js host, database and storage, and ask sales if you need SSO, visual editing or Payload-operated hosting.

View sources (2)
  • Payload get started: States the MIT license, self-hosting on Node.js, and enterprise SSO, hosting and visual editing.
  • Payload enterprise: Lists visual editing, SSO, publishing workflows and vendor or self-hosted enterprise deployment.

Choosing between them

Hygraph:

Fits if a predictable Hobby or Growth bill, including overages, is easier than operating the stack.

Payload:

Fits if you can fund the Node host, database and storage, and will ask sales only for enterprise extras.

Compare Hygraph’s plan with the hosting bill plus the enterprise features you would actually turn on.

Migration and exit

Hygraph content is copied out through the Content API. Payload content already lives in the database you operate, and REST can read it from a running app.

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)

Payload

Content stays in the database you operate

Leaving means exporting the database you already run and replacing the admin, hooks and API usage in the application. REST can also read documents out of a running app.

View sources (2)
  • Payload production deployment: Says Payload runs anywhere Next.js runs, and that you still provide a database and file storage.
  • Payload REST API: Generates CRUD routes from collections, including depth, locale and where queries.

Choosing between them

Hygraph:

Fits if a GraphQL export is an acceptable copy and you accept that assets and the frontend move separately.

Payload:

Fits if leaving means exporting a database you already run and replacing the admin and hooks in the app.

The easier exit is the database you operate. Take that seriously if leaving the vendor is a requirement.

Marketing website fit

Hygraph fits structured pages after preview is connected. Payload fits when the team will keep owning the app, blocks and iframe preview.

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.

Payload

Fits when the team will own the stack

Blocks and live preview can support campaign pages after the frontend URL and block components exist. The team keeps owning that app after launch.

View sources (2)
  • Payload blocks field: Stores mixed blocks, such as a page builder, each with its own schema in config.
  • Payload live preview: Renders the frontend in an iframe and sends document changes with window.postMessage.

Choosing between them

Hygraph:

Fits campaign sections as modular components, reviewed after save in the draft frontend.

Payload:

Fits when blocks and a configured live-preview URL are enough, and the team will keep running that app.

Choose the operating model first. The page editor will not compensate for a stack nobody can maintain.

Visual editing and preview

Hygraph loads your frontend beside the form and can add click-to-edit through its SDK. Payload’s open product uses an iframe preview, and names on-page visual editing as enterprise.

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.

Payload

Iframe preview; visual editing is enterprise

Live preview loads your frontend in the admin and posts each change to that frame. The separate visual editor is named as an enterprise feature, not as part of the MIT app.

Plan considerations: The open-source website template lists Live Preview. Enterprise materials add on-page visual editing.

View sources (3)
  • Payload live preview: Renders the frontend in an iframe and sends document changes with window.postMessage.
  • Payload get started: States the MIT license, self-hosting on Node.js, and enterprise SSO, hosting and visual editing.
  • Payload enterprise: Lists visual editing, SSO, publishing workflows and vendor or self-hosted enterprise deployment.

Choosing between them

Hygraph:

Fits if save-based preview, plus SDK click-to-edit where you tag fields, is the editing experience you want.

Payload:

Fits if an iframe preview is enough, or an enterprise agreement will include the on-page visual editor.

Do not treat either visual layer as included until you have seen it on the edition you will run.

Recommendations by use case

[Marketing website]

Choose the stack you will run

Choose Hygraph if a managed Studio and draft preview are enough. Choose Payload if the marketing site and CMS should be one app you deploy.

[Structured content platform]

Match where the model lives

Choose Hygraph for a hosted GraphQL schema. Choose Payload when collections and blocks should be TypeScript in the app repository.

[Multilingual multisite]

Cap versus config

Choose Hygraph if the plan’s locale cap is enough. Choose Payload if you will manage locales in config and test per-locale publishing before relying on it.

[Ecommerce]

Keep commerce beside the system you operate

Choose Hygraph to query content and federate a remote source from Growth. Choose Payload when product content should live in the database you run.

[Enterprise governance]

Validate the agreement

Approval workflows are an enterprise topic on both sides. Compare SSO, audit and hosting promises in the contract, not in the open feature list.

[Small team]

Be honest about operations

Hygraph Hobby suits a small project inside its caps if nobody will run a CMS server. Payload suits a small team that already deploys and maintains Node.js.

[Self hosted control]

Choose Payload when you must run it

Payload’s default is your app, database and files. Hygraph does not document a self-hosted content API.