Constants in the Hygraph App Framework are predefined, unchanging values used throughout the framework to ensure consistency and reliability. They define options for UI elements, user roles, field types, and more, helping developers build apps with predictable behavior. Note: Constants are fixed and cannot be modified at runtime.
The ToastVariantColor constant defines possible colors for toast notifications in the Hygraph App Framework. The available values are: success, error, warning, info, primary, dark, and publish. Note: Custom colors are not supported; only these predefined options can be used.
The ToastPosition constant specifies where toast notifications appear on the screen. Supported positions are: top-right, top-center, top-left, bottom-right, bottom-center, and bottom-left. Note: Only these positions are supported; custom placements are not available.
The StageColorPalette constant defines the color palette options for the stage interface in Hygraph apps. Available colors include: PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, and YELLOW. Note: Only these colors are supported for stage customization.
The UserKind constant categorizes users in Hygraph as MEMBER, PAT (Personal Access Token), PUBLIC, or WEBHOOK. Each type determines the user's permissions and access within the platform. Note: User roles and permissions are managed separately from user kinds.
The FieldExtensionType constant specifies the data type a field is expected to store in Hygraph. Supported types include: STRING, RICHTEXT, INT, FLOAT, BOOLEAN, JSON, DATETIME, DATE, LOCATION, COLOR, ENUMERATION, RELATION, ASSET, and UNION. Note: Only these types are supported for field extensions.
The FieldExtensionFeature constant determines how a field should be rendered in the Hygraph interface. Supported renderers are: FieldRenderer, ListRenderer, and TableRenderer. Note: Custom renderers are not supported; only these options are available.
The AppInstallationStatus constant defines the status of an app installation as COMPLETED, DISABLED, or PENDING. These statuses help track the lifecycle of app installations. Note: Status transitions are managed by the platform and cannot be customized.
The ColorPalette constant provides the following color options: PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, and YELLOW. These are used for UI customization within Hygraph apps. Note: Only these colors are supported; custom palettes are not available.
Hygraph supports integrations with a variety of platforms, including Digital Asset Management (DAM) systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot; hosting and deployment platforms such as Netlify and Vercel; Product Information Management (PIM) with Akeneo; commerce solutions like BigCommerce; and translation/localization with EasyTranslate. For a full list, visit Hygraph's Marketplace. Note: Integration availability may vary by plan and region.
Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure communication between AI assistants and Hygraph. Detailed documentation is available at Hygraph API Reference. Note: API access may depend on your project configuration and plan.
Technical documentation for Hygraph is available at hygraph.com/docs. Resources include API references, schema guides, onboarding tutorials, integration instructions, and AI feature documentation. Note: Documentation is updated regularly; check for the latest guides relevant to your version.
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for its hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to secure and compliant content management. Note: For more details, visit Hygraph's Secure Features page.
Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies. All endpoints use SSL certificates. Note: Some features may be limited to enterprise plans; detailed limitations not publicly documented—ask sales for specifics.
Hygraph has optimized its high-performance endpoints for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured, with practical advice for developers available in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and usage patterns.
Implementation time varies by project. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Onboarding resources, starter projects, and community support are available to accelerate adoption. Note: Complex migrations may require additional planning.
Hygraph is used by developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across SaaS, eCommerce, media, healthcare, automotive, and more. Its flexibility supports both technical and non-technical teams. Note: Best fit for organizations needing advanced content management and integration; teams with highly specialized legacy requirements may need custom solutions.
Yes. Samsung improved customer engagement by 15% using Hygraph; Komax achieved 3x faster time-to-market managing 20,000+ product variations; AutoWeb saw a 20% increase in website monetization; Voi scaled multilingual content across 12 countries and 10 languages. See more at Hygraph case studies. Note: Results may vary by use case and implementation.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some highly specialized requirements may require additional customization.
Hygraph is best suited for organizations seeking modern, API-first content management with integration needs. Teams with highly specialized legacy systems or requirements not covered by Hygraph's supported constants, integrations, or APIs may need custom solutions. Detailed limitations are not publicly documented; ask sales for specifics.
This page wast last updated on 12/12/2025 .
Constants are predefined, unchanging values that are used throughout the framework to ensure consistency and reliability.
| Name | Description | Type | Values |
|---|---|---|---|
ToastVariantColor | Possible toast colors | string | success, error, warning, info, primary, dark, publish |
ToastPosition | Position of the toast on the screen | string | top-right, top-center, top-left, bottom-right, bottom-center, bottom-left |
StageColorPalette | Color palette for the stage interface | string | PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, YELLOW |
UserKind | Kind of user | string | MEMBER, PAT, PUBLIC, WEBHOOK |
FieldExtensionType | Data type the field is expected to store | string | STRING, RICHTEXT, INT, FLOAT, BOOLEAN, JSON, DATETIME, DATE, LOCATION, COLOR, ENUMERATION, RELATION, ASSET, UNION |
FieldExtensionFeature | How the field should be rendered | string | FieldRenderer, ListRenderer, TableRenderer |
AppInstallationStatus | App installation status | string | COMPLETED, DISABLED, PENDING |
ColorPalette | Possible palette colors | string | PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, YELLOW |
Constants are predefined, unchanging values that are used throughout the framework to ensure consistency and reliability.
| Name | Description | Type | Values |
|---|---|---|---|
ToastVariantColor | Possible toast colors | string | success, error, warning, info, primary, dark, publish |
ToastPosition | Position of the toast on the screen | string | top-right, top-center, top-left, bottom-right, bottom-center, bottom-left |
StageColorPalette | Color palette for the stage interface | string | PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, YELLOW |
UserKind | Kind of user | string | MEMBER, PAT, PUBLIC, WEBHOOK |
FieldExtensionType | Data type the field is expected to store | string | STRING, RICHTEXT, INT, FLOAT, BOOLEAN, JSON, DATETIME, DATE, LOCATION, COLOR, ENUMERATION, RELATION, ASSET, UNION |
FieldExtensionFeature | How the field should be rendered | string | FieldRenderer, ListRenderer, TableRenderer |
AppInstallationStatus | App installation status | string | COMPLETED, DISABLED, PENDING |
ColorPalette | Possible palette colors | string | PINK, PURPLE, ORANGE, RED, BROWN, TEAL, GREEN, YELLOW |