[Head-to-head comparison]
Hygraph vs Storyblok
Hygraph vs Storyblok for marketing sites that need either a GraphQL content API or a built-in visual page editor.
By Kalle Bertell
Direct answer
Choose Hygraph when marketing content should live as GraphQL entries, relations and components, with editors working in Studio and a draft preview you connect. Choose Storyblok when editors should assemble campaign pages from approved blocks in the embedded visual editor. Both products keep the content backend vendor-managed. The choice is whether page composition is built into the editor or rendered by your frontend.
Choose Hygraph when
GraphQL content for many channels
Models and relations become one Content API. Editors still work in the entry form rather than an embedded page canvas.
Modular components you define
Editors stack the component types the schema allows. A new block type is a schema change, not a canvas setting.
A few locales on one entry
Translations sit on localized fields. Hobby and Growth cap that set at two or three locales.
Choose Storyblok when
Visual page composition
Editors assemble approved blocks in the embedded editor. Developers still define those blocks and connect the preview.
Folder or space localization
Field, folder and space options can keep a shared translation model or give a market its own space.
Campaign pages in the editor
The marketing fit depends on visual composition, provided the block library stays maintained.
Consider neither when
Self-hosted content backend
Both profiles describe a managed content platform. Neither describes running that backend on your own servers.
No one to own the frontend
Both still need a website, a preview integration and components your team maintains after launch.
Governance you have not funded
Custom workflows, finer roles and higher controls depend on the plan in both products. Match the contract first.
Criterion-by-criterion comparison
Marketer autonomy
Storyblok editors compose governed blocks. Hygraph editors fill models and the components those models already allow.
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)
- Hygraph content modeling: Modular components let editors choose blocks that already exist on the field.
- Hygraph plans and pricing: Lists two standard roles on Hobby, four on Growth, and custom roles only on Enterprise.
Storyblok
Visual composition from governed blocks
Editors assemble approved blocks without changing frontend code; their independence depends on the component library and validation rules.
View sources (2)
- Storyblok Visual Editor: Documents embedded preview, click-to-edit and live editing, including HTTPS and iframe/CSP requirements.
- Storyblok content modeling: Explains fields, blocks and stories, plus schema management through the UI, API and CLI.
Choosing between them
Fits teams that will stay inside a schema and accept that new block types are developer work.
Fits teams that want to arrange approved blocks without changing frontend code, within the library you maintain.
List the page changes editors must make alone, then see which product covers them without a new release.
Content modeling
Both use reusable structures. Hygraph generates GraphQL from models and components. Storyblok uses fields, blocks and stories.
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)
- Hygraph platform overview: The schema builder supports scalars, relations, unions, enumerations, components and remote sources.
- Hygraph content modeling: Components are reusable field groups, and modular components support page-building blocks.
- Hygraph plans and pricing: Lists model and component caps, with taxonomies and variants on Enterprise.
Storyblok
Reusable content built from fields, blocks and stories
Reusable schemas can be managed in the UI or automated through the Management API and CLI.
View sources (1)
- Storyblok content modeling: Explains fields, blocks and stories, plus schema management through the UI, API and CLI.
Choosing between them
Fits when relations, unions and modular components should be the content API other channels query.
Fits when stories and nestable blocks are the page model editors are expected to assemble.
Model one shared campaign and one reusable promo in both schemas before choosing the authoring shape.
Workflow and governance
Both gate advanced workflow. Hygraph keeps custom workflows on Enterprise. Storyblok’s custom workflows and roles depend on the plan.
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)
- Hygraph plans and pricing: Lists two stages on lower plans, custom workflows on Enterprise, and 14-day history on Growth.
- Hygraph content workflows: A workflow step can restrict the role and publish to a chosen stage.
- Hygraph scheduled publishing: Scheduled publishing and releases are documented as an Enterprise feature.
Storyblok
Useful defaults; advanced controls are tiered
A default three-stage workflow is documented; custom workflows, roles, pipelines and retention depend on the selected plan.
Plan considerations: Governance and environment features depend on your plan and contract; confirm which capabilities are included.
View sources (3)
- Storyblok workflows: Documents the default publishing stages, with assignees, roles, dates and notifications.
- Storyblok roles: Details role-based permissions for content, schemas, assets, languages, workflows and releases.
- Storyblok pricing: Lists space-based plans and limits for seats, API requests, traffic, content, assets, locales and governance.
Choosing between them
Fits if two stages are enough, or Enterprise is already budgeted for approval steps and scheduling.
Fits if the documented three-stage workflow matches the team and the contract covers any custom roles.
Write down the stages, roles and schedule you require, then match them to the plan you will buy.
Localization and multisite
Hygraph localizes fields, with two or three locales on lower plans. Storyblok also offers folder and space separation.
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)
- Hygraph field localization: A field can be localized so editors translate it on the same entry.
- Hygraph localization API: Locales are configured per environment and can be queried or mutated.
- Hygraph plans and pricing: Lists two, three or up to 80 locales depending on the plan.
Storyblok
Field, folder and space localization
Combine translated fields, market-specific folders and separate spaces to balance shared content with regional independence.
View sources (1)
- Storyblok internationalization: Explains field-, folder- and space-level localization and how each approach affects publishing.
Choosing between them
Fits a small set of languages on one entry, until the locale cap forces an upgrade.
Fits when some markets share fields and others publish from their own folder or space.
Map how independently each market publishes, then see whether field locales or separate spaces match that boundary.
Developer experience
Hygraph centers a generated GraphQL API. Storyblok adds framework-agnostic APIs and schema tooling. Both need a preview integration.
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)
- Hygraph content modeling: Schema changes in the project define the models and components the API exposes.
- Hygraph Management API permissions: Management API permissions cover schema, environments, roles and webhooks for tokens.
- Hygraph plans and pricing: Lists one environment on Hobby, two on Growth and up to ten on Enterprise.
Storyblok
Framework-agnostic APIs plus schema tooling
Component-based models and API/CLI tooling support schema automation and version control; preview still needs frontend integration.
View sources (3)
- Storyblok content modeling: Explains fields, blocks and stories, plus schema management through the UI, API and CLI.
- Overview of Storyblok APIs: Describes REST delivery and management, GraphQL delivery and the Image Service API.
- Storyblok Visual Editor: Documents embedded preview, click-to-edit and live editing, including HTTPS and iframe/CSP requirements.
Choosing between them
Fits teams that want the schema and the Content API to stay in one managed project.
Fits teams that want Management API and CLI schema automation beside a component-based frontend.
Decide whether schema changes should live in Studio and the Management API, or in the CLI workflow you already run.
APIs and extensibility
Hygraph’s primary API is GraphQL, with webhooks. Storyblok documents REST, GraphQL, a management API, images and webhooks.
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)
- Hygraph localization API: The Content API can query and mutate localized entries, including by locale.
- Hygraph webhook events: Webhooks can fire on create, update, publish, unpublish and other content actions.
- Hygraph plans and pricing: Lists webhook, remote-source and uncached request limits for each plan.
Storyblok
REST, GraphQL, management, images and webhooks
Use delivery and management APIs, an image service and event webhooks; REST remains the broadest documented API surface.
View sources (2)
- Overview of Storyblok APIs: Describes REST delivery and management, GraphQL delivery and the Image Service API.
- Storyblok webhooks: Documents event webhooks and the paid-plan requirement for webhook signing secrets.
Choosing between them
Fits clients that will query and mutate content through the generated GraphQL API.
Fits when you also need the broader REST surface and the documented image service.
Prototype the queries and the publish webhook the site needs, including draft reads and the rate limit on the plan.
Hosting and operations
Both vendors run the content platform, and you still host the website. Hygraph’s lower plans list EU, US and APAC shared regions.
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)
- Hygraph plans and pricing: Lists EU, US and APAC shared regions on Hobby and Growth, plus dedicated options on Enterprise.
- Hygraph platform overview: Hygraph delivers modeled content through its API, with the frontend remaining yours.
Storyblok
Managed delivery with CDN and regions
Storyblok runs the content platform and CloudFront delivery with region-specific endpoints; your team still owns frontend hosting, builds and runtime operations.
View sources (2)
- Storyblok Content Delivery API: Describes REST JSON delivery, CloudFront caching and region-specific API endpoints.
- Storyblok Trust Center: Documents AWS hosting, regional residency options, ISO 27001 and platform reliability controls.
Choosing between them
Fits when a managed GraphQL API in one of those shared regions is an acceptable content host.
Fits when managed delivery with the documented CDN and region endpoints matches the operating model.
Confirm the content-API region you need, and keep website hosting with the team that already runs the site.
Security and governance
Both document managed security and put SSO, finer access and SLAs behind the plan or the contract.
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)
- Hygraph security features: States SOC 2 Type 2, GDPR and hosting on ISO 27001 certified infrastructure, plus SSO and audit logs.
- Hygraph plans and pricing: Lists SSO, audit logs and an uptime SLA with Enterprise, with 90-day audit retention.
- Hygraph backup recovery: Disaster-recovery backups cover all plans. One-click restore is an Enterprise add-on.
Storyblok
Managed security; advanced controls vary by plan
Documented protections include AWS infrastructure, residency options and ISO 27001; SSO, access controls, backups and SLAs vary by plan or contract.
View sources (3)
- Storyblok Trust Center: Documents AWS hosting, regional residency options, ISO 27001 and platform reliability controls.
- Storyblok roles: Details role-based permissions for content, schemas, assets, languages, workflows and releases.
- Storyblok pricing: Lists space-based plans and limits for seats, API requests, traffic, content, assets, locales and governance.
Choosing between them
Fits if SOC 2 Type 2 covers the review for now, and Enterprise controls are either waiting or already quoted.
Fits if the profile’s ISO 27001 and residency statements match the review, after you confirm SSO and backups.
Send one security questionnaire for the plan you will sign, and compare the answers before you treat either as approved.
Pricing and cost drivers
Hygraph has a free Hobby tier and Growth from $199. Storyblok prices per space, with seats, traffic and locale limits.
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)
- Hygraph plans and pricing: Lists Hobby and Growth caps, the $199 starting price, asset entries and overage rates.
Storyblok
Space plans with seat, usage and locale limits
Budget per space for included seats, requests, traffic, content, assets and locales; extra capacity and advanced controls can increase total cost.
Plan considerations: Check current pricing in your billing currency, including fair-use terms and contract-specific allowances.
View sources (1)
- Storyblok pricing: Lists space-based plans and limits for seats, API requests, traffic, content, assets, locales and governance.
Choosing between them
Fits a project that stays inside Hobby’s entry, seat and locale caps, or a Growth budget you have already modeled.
Fits when the space plan’s seats, requests and locales cover the sites you will actually launch.
Price the first year with entries, API traffic, seats and locales, including overages, before comparing the sticker prices.
Migration and exit
Hygraph content can be read out through the Content API. Storyblok documents APIs plus JSON or XML export, and assets need a separate plan.
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)
- Hygraph backup recovery: Says content can be exported offsite through the Content API, separate from in-app restore.
- Hygraph plans and pricing: Lists version-history retention of 14 days on Growth and up to a year on Enterprise.
Storyblok
APIs and JSON/XML export; plan for assets
APIs and CLI tooling support content and schema migration; separately plan the transfer of asset files, references, translations and application code.
View sources (3)
- Storyblok Management API: stories: Documents programmatic content management and JSON/XML story import and export.
- Storyblok CMS migration: Explains programmatic content and asset migration, including CLI dry-run guidance.
- Storyblok backups: Documents S3 backups on eligible plans and exclusions, including actual asset files.
Choosing between them
Fits if a GraphQL export of entries, relations and locales is an acceptable exit, without depending on old versions.
Fits if CLI or API export of content and schema is the path, with asset files transferred on purpose.
Export a sample of entries, assets and one localized page from each product and try to rebuild it elsewhere.
Marketing website fit
Storyblok targets visual page composition. Hygraph fits structured pages after you connect preview and render the components.
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.
Storyblok
Visual page composition from reusable components
Campaign and marketing teams benefit from visual composition, provided the component library stays flexible and well maintained.
View sources (2)
- Storyblok Visual Editor: Documents embedded preview, click-to-edit and live editing, including HTTPS and iframe/CSP requirements.
- Storyblok content modeling: Explains fields, blocks and stories, plus schema management through the UI, API and CLI.
Choosing between them
Fits marketing sites whose editors can work in the form when the preview shows the saved draft.
Fits campaign teams that should compose pages visually from a block library someone keeps current.
Give editors one real landing-page task in both products and keep the one they can finish without a developer.
Visual editing and preview
Storyblok embeds the page editor. Hygraph shows your frontend beside the form and refreshes it 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.
Storyblok
Embedded visual editor with click-to-edit
Editors work in the embedded frontend; setup requires an HTTPS preview URL and compatible iframe and content-security settings.
View sources (1)
- Storyblok Visual Editor: Documents embedded preview, click-to-edit and live editing, including HTTPS and iframe/CSP requirements.
Choosing between them
Fits when a draft iframe, and click-to-edit if you add the SDK, is enough after the preview route exists.
Fits when editors should click into the page in the embedded editor, once the preview URL and blocks exist.
Build one campaign page in each editor and note who maintains the blocks or the preview attributes after launch.
Recommendations by use case
[Marketing website]
Start with Storyblok
Use Storyblok when editors compose campaign pages from blocks. Choose Hygraph when the page is structured entries and a connected draft preview is enough.
[Structured content platform]
Favor Hygraph’s Content API
Choose Hygraph when other channels should query the same GraphQL models. Choose Storyblok when the content is mainly pages built from blocks.
[Multilingual multisite]
Match the publishing boundary
Choose Storyblok when markets need their own folders or spaces. Choose Hygraph when a few field locales on one entry are enough.
[Ecommerce]
Query content, or compose pages
Choose Hygraph when product content should be GraphQL entries. Remote sources start on Growth. Choose Storyblok when the job is campaign pages.
[Enterprise governance]
Validate the contract
Both put custom workflows, finer roles and SLAs on higher plans. Compare the controls in the quote rather than the default project.
[Small team]
Choose the editor you can sustain
Storyblok is the lighter editing model if the block library stays small. Hygraph Hobby still needs a preview frontend and stays inside its caps.
[Self hosted control]
Choose neither for a private backend
Neither profile describes a content API you install yourself. Use a self-hosted CMS if that requirement is mandatory.