Hygraph logo

[Platform profile]

Hygraph for marketing websites

Hygraph for structured GraphQL content, field locales, live preview and marketing website delivery.

Managed SaaS Proprietary Official website
Kalle Bertell

By Kalle Bertell

Direct answer

Hygraph suits teams that model marketing content as GraphQL entries, relations and components, and can connect a draft preview. Editors work in a managed Studio, while your team still hosts the website. Consider another platform when the content API must run on your infrastructure, or when custom approval workflows are required without an Enterprise plan.

Good fit

  • Reusable GraphQL entries

    Models, relations and components are exposed through one Content API, so the same entries can feed more than one site or channel.

    View sources (1)
  • Modular page sections

    A modular component lets editors pick from a defined set of blocks on one field, without a separate model for every page layout.

    View sources (1)
  • Translations on each field

    Editors add locales on the same entry and translate individual fields, instead of copying the whole content type for each language.

    View sources (1)

Consider alternatives

  • Self-hosted content storage

    Pricing lists shared or dedicated cloud regions. It does not describe installing the content API and Studio on your own servers.

    View sources (1)
  • Custom approval workflows

    Hobby and Growth include two stages and no custom workflows. Role-based approval steps are listed on Enterprise.

    View sources (2)
  • More than three locales

    Hobby includes two locales and Growth three. A market set above that cap means an Enterprise quota, up to 80.

    View sources (1)

Evidence by criterion

How we evaluate platforms

Visual editing and preview

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.

Marketer autonomy

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)

Content modeling

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)

Workflow and governance

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)

Localization and multisite

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)

Developer experience

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)

APIs and extensibility

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)

Hosting and operations

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)

Security and governance

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)

Pricing and cost drivers

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)

Migration and exit

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)

Marketing website fit

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.

Team takeaways

For content teams

Content teams create entries, fill localized fields and place modular components in Studio. A draft preview appears after the preview URL exists, and it refreshes when they save. What they can publish follows the role, and custom approval steps require Enterprise.

For developers

Developers shape models in the schema builder, and authorized tokens can manage schema and webhooks through the Management API. The team still owns the website, draft preview route and iframe headers. Hygraph runs the content API, Studio and asset CDN in a chosen region.