Docs
Guides, recipes, and the full Hot Chocolate and Fusion reference.
GraphQL help
Get unblocked, on your timeline.
Use the documentation and open community for everyday questions, bring a defined technical problem to an advisory engagement, or choose a support plan for ongoing production coverage.
Three paths
Choose the help that matches your situation.
Community for open questions, advisory for getting unstuck on a defined problem, support for teams that depend on GraphQL in production.
Community
Ask public questions and learn from other ChilliCream users.
Free
- Public Slack channel
- Open GitHub discussions
- Searchable history
- Best-effort responses
Advisory
Bring a GraphQL problem to an expert and get clear direction.
20h
increments
- Architecture and schema design
- Troubleshooting and review
- Hot Chocolate and Fusion expertise
- Agreed package of hours
Support
Ongoing coverage for teams running GraphQL in production.
From $450
per month
- Private channel on paid plans
- Defined incident allowances
- Published response times
- Coverage options by plan
First stop
Try the self-serve resources before you ask.
Most questions have already been answered. Five places to look before you reach out.
FAQ
Answers to common questions.
Where should I start?
Start with the docs, GitHub, or community Slack when the question can be handled in public and does not need a response guarantee. Choose advisory for a defined technical problem or review. Choose a support plan when your production team needs ongoing channels, incident allowances, and response terms.
What response time can I expect on Slack?
Community Slack is best effort and does not include a response guarantee. If response terms matter to your team, compare the paid support plans and choose the incident coverage that matches your production needs.
When should we choose advisory instead of a support plan?
Advisory fits a scoped question, architecture review, troubleshooting need, or implementation. A support plan fits ongoing production coverage with plan-specific channels, incident allowances, and response times. Teams can also use both.
How do I escalate something urgent in production?
Use the channels and escalation process defined in your support agreement. Without a paid support plan, community channels remain best effort and should not be treated as an incident-response commitment.
Can ChilliCream help us design a schema or migration?
Schema design, reviews, Fusion rollout planning, and migration guidance can be scoped as advisory work. For an implementation, discuss a contracting engagement with defined deliverables and milestones.
Is the community Slack the right place for bug reports?
Slack is good for triage and reproductions. Once a bug is confirmed, please file it on GitHub so it gets a tracking issue, a label, and a place to land the fix.
Still not sure where to start?
Explore advisory for a scoped GraphQL problem or compare support plans when your production team needs ongoing channels and response terms. If we are not the right help, we will say so.