[Head-to-head comparison]
Hygraph vs Strapi
Hygraph vs Strapi for marketing websites, comparing a managed GraphQL studio with an open-core CMS you can host.
By Kalle Bertell
Direct answer
Choose Hygraph when the vendor should run the content API and Studio, and the plan’s locale and workflow limits are acceptable. Choose Strapi when the team will own a Node.js CMS, on its own servers or on Strapi Cloud, including locales on the free plan. Hygraph does not document a self-hosted content API. Strapi’s updating live preview is paid, while Hygraph’s preview refreshes on save.
Choose Hygraph when
A vendor-run content API
Hygraph operates the API, Studio and asset CDN. The website and the draft preview route stay with you.
GraphQL as the content model
The schema builder produces the Content API, including relations, unions and modular components.
Preview without a CMS license
Hobby lists live preview. It refreshes on save and still needs your frontend to serve drafts.
Choose Strapi when
A CMS the team can host
Community is MIT-licensed. You can run it yourself, or deploy the same project to Strapi Cloud.
Locales on the free plan
Internationalization is a Community feature, and the pricing page lists unlimited locales on the CMS plans.
Content types in the admin
The Content-type Builder creates collection types, components and dynamic zones editors then fill.
Consider neither when
A visual page canvas by default
Hygraph’s setup guide describes a form and an iframe. Strapi’s live, as-you-type preview needs Growth or Enterprise.
Review workflows on the free tier
Hygraph custom workflows are Enterprise. Strapi review workflows and audit logs are Enterprise too.
No operator and no SaaS budget
Strapi still needs someone to run the project. Hygraph’s useful limits sit behind Hobby caps or a paid plan.
Criterion-by-criterion comparison
Marketer autonomy
Editors in both products fill structures developers control. Strapi uses the content type and roles. Hygraph uses the model, components and plan roles.
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.
Strapi
Editors fill types; layout follows the model
Editors manage entries, components and dynamic zones in the Content Manager. Adding a section type or a permission still happens in the content-type and role settings developers control.
View sources (2)
- Strapi Content-type Builder: Creates collection and single types, with draft-and-publish and internationalization settings.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits if modular components and localized fields cover the edits, with custom permissions left for Enterprise.
Fits if dynamic zones are enough and the team accepts that new section types are a content-model change.
List edits that must not need a deploy. Both products will still send new component types back to development.
Content modeling
Hygraph is a GraphQL schema of models and components. Strapi is collection types, components and dynamic zones in a Node project you own.
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.
Strapi
Collection types, components and dynamic zones
The Content-type Builder defines collection types, single types, components and repeatable dynamic zones. Saving a type requires at least one configured field.
View sources (1)
- Strapi Content-type Builder: Creates collection and single types, with draft-and-publish and internationalization settings.
Choosing between them
Fits when the content API should be generated and hosted with the schema.
Fits when the content types should live in a project you can run yourself or on Strapi Cloud.
Model the same page and a shared component in both, then see which team is supposed to change it later.
Workflow and governance
Both keep review workflows on Enterprise. Strapi includes drafts and custom roles on Community. Hygraph starts with two stages and standard roles.
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.
Strapi
Drafts and roles free; reviews are Enterprise
Community includes draft and publish, RBAC and API tokens. Releases and content history start on Growth. Review workflows and audit logs are Enterprise.
Plan considerations: Growth history is 14 days. Enterprise history is documented as 30 days, extendable to 90.
View sources (1)
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits if two stages cover publishing until an Enterprise workflow is funded.
Fits if Community drafts and roles are enough, and review workflows can wait for Enterprise.
Do not buy either product for an approval chain unless that chain is in the edition you will run.
Localization and multisite
Strapi includes locales on every CMS plan, including Community. Hygraph caps Hobby at two locales and Growth at three.
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.
Strapi
Locales on every plan, including Community
Turn internationalization on for a content type, then for individual fields. The pricing page lists unlimited locales on Community, Growth and Enterprise.
View sources (2)
- Strapi internationalization: Enables locales per content type and field on the free Community plan.
- Strapi CMS pricing: Lists the free MIT Community plan, Growth at $45 per month, and Enterprise review workflows.
Choosing between them
Fits only when the market count stays inside the plan, or Enterprise’s higher cap is funded.
Fits when each content type should be localized without a locale cap on the CMS plan.
Count locales first. This is the clearest reason to prefer Strapi for a multilingual site on a small plan.
Developer experience
Hygraph is a managed project with a schema builder and Management API. Strapi is a Node.js project, admin and CLI that you operate.
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.
Strapi
Node project, admin builder and a CLI
Developers own the Strapi project and can model in the admin or extend it in code. The same project runs self-hosted or on Strapi Cloud.
View sources (2)
- Strapi Content-type Builder: Creates collection and single types, with draft-and-publish and internationalization settings.
- Strapi Cloud fundamentals: Describes Strapi Cloud as hosting for an existing project, not a different CMS.
Choosing between them
Fits teams that do not want to host or upgrade the CMS process.
Fits teams that want the CMS in their repository and will run it themselves or on Strapi Cloud.
Ask who patches the CMS. If the answer is your team, Strapi matches that. If it is the vendor, Hygraph does.
APIs and extensibility
Hygraph’s API is the generated GraphQL API, plus webhooks. Strapi exposes REST and GraphQL for the content types on every CMS plan.
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.
Strapi
REST and GraphQL on every CMS plan
REST and the GraphQL plugin read and write content types, including locale and draft status. The features table includes both APIs on Community.
View sources (3)
- Strapi REST API: Documents REST reads and writes, including locale and draft status parameters.
- Strapi GraphQL API: The GraphQL plugin queries and mutates content types with filters, sort and pagination.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits when GraphQL mutations, draft tokens and webhooks are the integration style you want.
Fits when REST and GraphQL should follow content types you host, including locale and draft status.
Pick the API your frontends already call. Do not add a second query style without a reason.
Hosting and operations
Hygraph runs the content platform in shared regions. Strapi can be self-hosted, or the same project can be deployed to Strapi Cloud.
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.
Strapi
Self-host the project, or use Strapi Cloud
You can operate the Node.js app and database, or deploy that project to Strapi Cloud. Cloud plans meter hosting resources and do not include Growth or Enterprise CMS features.
View sources (2)
- Strapi Cloud fundamentals: Describes Strapi Cloud as hosting for an existing project, not a different CMS.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits when a managed API, Studio and asset CDN in EU, US or APAC is what you want to operate.
Fits when you will run the Node.js app and database, or pay Strapi Cloud to host that project.
If the content database must sit on your infrastructure, this comparison already has a direction.
Security and governance
Hygraph states SOC 2 Type 2, with SSO and audit logs on Enterprise. Strapi includes RBAC everywhere, and puts SSO, audit logs and the SOC 2 report on paid editions.
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.
Strapi
RBAC everywhere; SSO and audit logs are paid
Community includes role-based access. SSO is a Growth add-on and included on Enterprise. Audit logs and the SOC 2 report are Enterprise items on the pricing page.
Plan considerations: Self-hosted data residency is yours. Strapi Cloud regions and backups follow the Cloud plan.
View sources (2)
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
- Strapi CMS pricing: Lists the free MIT Community plan, Growth at $45 per month, and Enterprise review workflows.
Choosing between them
Fits if the vendor’s SOC 2 statement is the baseline and Enterprise controls are quoted where required.
Fits if you will own residency by self-hosting, or accept Cloud regions, and buy SSO only if you need it.
Write down residency, SSO and audit logs separately. The two products assign them to different editions.
Pricing and cost drivers
Hygraph’s free tier is capped by entries, seats and API use, then Growth starts at $199. Strapi Community is free, and Cloud is a separate bill from the CMS license.
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.
Strapi
Free Community, then CMS and Cloud bills
Community is free under MIT, with unlimited entries on the CMS pricing page. Growth starts at $45 per month before user charges, and Strapi Cloud is a separate hosting invoice.
View sources (2)
- Strapi CMS pricing: Lists the free MIT Community plan, Growth at $45 per month, and Enterprise review workflows.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits if Hobby’s caps hold, or a single Growth subscription is simpler than a CMS license plus hosting.
Fits if the team can run Community, and will budget Growth or Enterprise only for the paid CMS features.
Add the Cloud invoice, or your own hosting, to Strapi before comparing it with Hygraph’s plan price.
Migration and exit
Hygraph content leaves through the Content API. Strapi’s CLI can transfer content, files and schemas between matching instances, excluding users and tokens.
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.
Strapi
Transfer content between matching Strapi instances
The CLI can export, import or stream content, files and schemas. A transfer requires matching schemas, and it does not move admin users or API tokens.
View sources (2)
- Strapi data transfer: Streams content, files and schemas between instances. Admin users and API tokens are excluded.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits if a GraphQL copy of entries is enough and you do not need a matching-instance transfer.
Fits if you want a CLI export or transfer between Strapi projects that already share a schema.
Try the exit you claim you will use. A transfer tool and a query export are not interchangeable.
Marketing website fit
Hygraph fits structured pages once preview is connected. Strapi fits dynamic zones when the frontend renders them, with live preview only on a paid CMS license.
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.
Strapi
Fits structured pages when preview is funded
Dynamic zones let editors place components that the frontend already renders. Seeing those changes live in the admin depends on a Growth or Enterprise Live Preview license.
View sources (2)
- Strapi Content-type Builder: Creates collection and single types, with draft-and-publish and internationalization settings.
- Strapi preview: Preview is configured for every plan. Live Preview requires Growth or Enterprise.
Choosing between them
Fits campaign sections modeled as modular components, reviewed in a draft iframe after save.
Fits if editors can work from a preview URL, or you will fund Live Preview for updates while typing.
Choose the preview behavior editors asked for, then confirm it is in the edition you can pay for.
Visual editing and preview
Hygraph’s preview refreshes on save and is listed on Hobby. Strapi can open a preview URL on every plan, and charges for live updates as editors type.
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.
Strapi
Preview URL on every plan; live updates are paid
Preview opens the frontend from the Content Manager after you set a client URL. Live Preview, which refreshes as the entry changes, is a Growth and Enterprise feature.
View sources (2)
- Strapi preview: Preview is configured for every plan. Live Preview requires Growth or Enterprise.
- Strapi features and plans: Separates Community, Growth and Enterprise features from Strapi Cloud hosting plans.
Choosing between them
Fits if a saved-draft iframe is acceptable and you will add the Preview SDK only where click-to-edit matters.
Fits if a configured preview URL is enough, or a Growth or Enterprise license will pay for Live Preview.
Decide whether preview must update while typing. That single requirement moves the Strapi license.
Recommendations by use case
[Marketing website]
Match the preview you can fund
Choose Hygraph if a save-to-refresh preview is enough. Choose Strapi if you will own the app and only need a preview URL, or you will buy Live Preview.
[Structured content platform]
Choose who runs the API
Choose Hygraph for a managed GraphQL API. Choose Strapi when the content types and API should live in a project you operate.
[Multilingual multisite]
Prefer Strapi for many locales
Strapi lists locales on Community. Hygraph’s lower plans stop at two or three. Choose Hygraph only if that cap, or Enterprise, is acceptable.
[Ecommerce]
Keep the catalog next to the CMS you will operate
Choose Hygraph to query product content and, from Growth, a remote source. Choose Strapi when the catalog content should live in the app you host.
[Enterprise governance]
Validate the edition
Review workflows are Enterprise on both. Strapi also gates audit logs there. Compare SSO and history on the edition you will run.
[Small team]
Count operators, not only seats
Hygraph removes the CMS process from your team and caps the free project. Strapi is free to run if someone will operate Node.js, the database and upgrades.
[Self hosted control]
Choose Strapi when the database must be yours
Strapi can run on your infrastructure. Hygraph’s pricing page does not describe a self-hosted content API.