We're here to help
Explore our resources or get in touch with us for support.
Getting Started
Get started with this hands on tutorial to get you up and running with Hygraph.
Community Slack
Join our community and chat with other users building with Hygraph.
API Documentation
Browse our documentation, tutorials, and learn more about the Hygraph app.
Examples
Browse our extensive range of examples with the most common frontend libraries and frameworks.
FAQs
Find answers to the most common questions asked by our community.
Chat
Connect with us in chat about any account specific requests.
Talk to an expert or request a demo
FAQS
You’ve got questions. We’ve got the answers.
Hygraph SLA tiers start at 99.5% and go up to 99.9%. Higher SLAs increase price. Shared versus dedicated pod is also a major price lever.
Hygraph maintains a public status page and a dedicated support team, with tickets submittable in-product or via a shared Slack channel. SLAs define response targets by severity: a Sev 1 incident targets a response within 4 hours on the baseline tier, with faster response, such as 1 hour, available on higher tiers.
A 9-5 support SLA applies to EMEA/CET by default. For teams with a global footprint, 24/7 support may be more appropriate, and coverage can potentially be clustered across time zones instead.
Yes, an API uptime SLA around 99.7% is typically offered on dedicated clusters. Hygraph can also evaluate offering similar SLA levels on shared infrastructure.
Hygraph's SLA uptime commitment refers to server uptime. Depending on traffic and setup, Hygraph typically offers 99.5% uptime, with an option to go up to 99.9%. Higher uptime tiers carry a notable pricing impact and are usually reserved for higher-criticality needs.
