← Knowledge Base • platform

Hygraph

A GraphQL-native headless CMS with content federation capabilities for building unified content APIs.

What is Hygraph?

Hygraph, formerly known as GraphCMS, is a GraphQL-native headless content management system. Launched in 2017, it was one of the first CMS platforms built entirely around GraphQL, offering a native experience for developers who prefer this query language over REST.

Hygraph represents “The Federated Content Platform”. It is designed for teams building modern applications that benefit from GraphQL’s flexible querying capabilities. Its standout feature is Content Federation, which allows organisations to aggregate content from multiple sources (databases, APIs, legacy systems) into a unified GraphQL schema.

The platform operates as a SaaS with tiers ranging from free community plans to enterprise deployments with advanced features.

Architecture and Technology

Hygraph is built from the ground up with GraphQL as the primary interface.

Core Components

  • Schema Builder: Visual interface for defining content models
  • GraphQL API: Native GraphQL endpoint with subscriptions
  • Content Federation: Connect external data sources to the schema
  • Asset Management: Media library with transformations
  • Webhooks: Event-driven integrations

GraphQL-Native Features

  • Queries: Fetch exactly the data needed
  • Mutations: Create, update, delete operations
  • Subscriptions: Real-time updates via WebSockets
  • Fragments: Reusable query components
  • Batching: Combine multiple operations efficiently

Content Federation

Hygraph’s federation enables:

  • Connecting external REST or GraphQL APIs
  • Storing remote data references locally
  • Querying unified schema across sources
  • Caching federated content for performance

Typical Use Cases

Hygraph is commonly used for:

  • Enterprise content hubs: Unified content from multiple systems
  • Marketing websites: Structured content with flexible queries
  • E-commerce: Product content alongside editorial content
  • Multi-channel delivery: Single API for web, mobile, and IoT
  • Content aggregation: Combining CMS with external data sources
  • Developer portals: Technical documentation with GraphQL integration

Strengths

  • Native GraphQL: First-class GraphQL with full specification support
  • Content Federation: Unique capability to unify disparate data sources
  • Flexible schema: Rich content modelling with relations and components
  • Real-time subscriptions: Built-in WebSocket support
  • Global CDN: Edge-cached content delivery
  • Granular permissions: Field-level access control
  • Environments: Staging and production content separation

Limitations and Trade-offs

  • GraphQL complexity: Requires GraphQL knowledge,no REST API fallback
  • SaaS only: No self-hosted option
  • Pricing at scale: Costs increase with usage and features
  • Federation complexity: Advanced federation requires careful planning
  • Learning curve: Schema design requires upfront planning
  • Enterprise features gated: Key capabilities require paid tiers

SEO, Performance, and Content Governance

SEO

As headless CMS, SEO is implemented at the frontend:

  • SEO components: Define reusable SEO field groups
  • Structured content: Granular content enables rich snippets
  • Preview: Draft content preview before publishing
  • URL management: Custom UID fields for routing

Performance

  • Global CDN: Content cached at 190+ edge locations
  • Query efficiency: GraphQL allows minimal payloads
  • Caching layers: Edge, application, and database caching
  • Real-time options: Subscriptions for dynamic applications

Content Governance

  • Roles and permissions: Granular, field-level access control
  • Publishing workflows: Draft, review, and publish stages
  • Environments: Separate staging and production
  • Audit logs: Track content changes and user actions
  • Scheduling: Future publication planning

Localisation

  • Locale management: Configure multiple languages
  • Field-level translation: Mark fields as localisable
  • Fallback configuration: Define language fallback chains
  • Content relationship: Link translated entries

Tips and Best Practices

  • Design schema carefully,GraphQL schemas benefit from thoughtful structure
  • Use fragments in queries for maintainable frontend code
  • Leverage components for reusable content patterns
  • Implement caching to manage rate limits and improve performance
  • Consider federation for enterprise integrations from the start
  • Use environments to safely test schema changes

Who Should (and Should Not) Choose Hygraph

Best Fit For

  • Teams with strong GraphQL expertise
  • Enterprise needing to unify multiple content sources
  • Projects requiring real-time content updates
  • Developers preferring GraphQL over REST
  • Complex content models with relationships

Not Ideal For

  • Teams unfamiliar with GraphQL
  • Simple projects where REST CMSs suffice
  • Budget-constrained projects at scale
  • Organisations requiring on-premises deployment
  • Non-technical teams without developer support

Common Alternatives

  • Contentful: REST-first with GraphQL option, larger ecosystem
  • Sanity: Real-time collaboration, GROQ query language
  • Strapi: Open-source with both REST and GraphQL
  • DatoCMS: GraphQL available, simpler interface
  • Hasura: GraphQL engine for direct database access

Hygraph stands out for teams committed to GraphQL and organisations needing to federate content from multiple systems into a unified API.