Skip to content
FraiseQL v2.0.0-alpha

Getting Support

Need help with FraiseQL? There are several ways to get support depending on your question or issue.

Quick Questions and Discussion

Section titled “Quick Questions and Discussion”

Discord Community

Section titled “Discord Community”

The fastest way to get answers and connect with other FraiseQL users.

  • URL: discord.gg/fraiseql
  • Channels:
    • #general — General discussion and announcements
    • #help — Questions and troubleshooting
    • #show-and-tell — Share your projects
    • #announcements — Important updates
  • Response Time: Usually within minutes during business hours
  • Best for: Quick questions, real-time discussion, community interaction

GitHub Discussions

Section titled “GitHub Discussions”

For longer-form discussions and feature requests.

  • URL: github.com/fraiseql/fraiseql/discussions
  • Categories: Ideas and Feature Requests, Q&A, Show and Tell, General
  • Response Time: 1-3 days typically
  • Best for: Feature requests, architectural questions, detailed technical discussions

Bug Reports and Issues

Section titled “Bug Reports and Issues”

GitHub Issues

Section titled “GitHub Issues”

Report bugs and request features on GitHub.

  • URL: github.com/fraiseql/fraiseql/issues
  • Before reporting, check if your issue already exists
  • Include:
    • FraiseQL version
    • Python/Node/Go version
    • Database and version
    • Minimal reproducible example
    • Expected behavior
    • Actual behavior
    • Error message or traceback

Response Time: Critical bugs prioritized; others within 1 week

Commercial Support

Section titled “Commercial Support”

For enterprise support, SLAs, and dedicated assistance:

  • Email: support@fraiseql.dev
  • Services:
    • Priority issue resolution
    • Architecture consultation
    • Custom integration support
    • Training and onboarding
    • SLA guarantees (1-4 hour response)
    • Dedicated support contact
  • Best for: Production deployments, critical issues, team training

Choosing the Right Channel

Section titled “Choosing the Right Channel”
Question TypeBest ChannelResponse Time
Quick questionDiscord #helpMinutes
Bug reportGitHub Issues1 week
Feature ideaGitHub Discussions1-3 days
Urgent production issuesupport@fraiseql.dev1-4 hours
Architecture adviceGitHub Discussions1-3 days
Show and tellDiscord #show-and-tellVaries
Security issuesecurity@fraiseql.devSame day
Documentation problemGitHub Issues + Discord1-7 days
Deployment helpsupport@fraiseql.dev1-4 hours
Performance optimizationDiscord or DiscussionsVaries

Reporting Security Issues

Section titled “Reporting Security Issues”

Instead:

  1. Email security@fraiseql.dev
  2. Include:
    • Vulnerability description
    • Affected FraiseQL versions
    • Steps to reproduce (if possible)
    • Potential impact
  3. We will acknowledge within 24 hours and work on a fix

For more details, see our Security Policy.

What to Include When Asking for Help

Section titled “What to Include When Asking for Help”

For General Questions

Section titled “For General Questions”
  • What you’re trying to achieve
  • What you’ve already tried
  • Any error messages or unexpected behavior
  • FraiseQL version and language SDK version

For Bug Reports

Section titled “For Bug Reports”
  • FraiseQL version: fraiseql --version
  • SDK version (Python, TypeScript, etc.)
  • Database: PostgreSQL/MySQL/SQLite/SQL Server
  • Database version
  • Minimal reproducible example (code that reproduces the issue)
  • Full error message and traceback
  • Expected behavior vs actual behavior
  • Environment: Docker/Kubernetes/Local/Production

For Performance Issues

Section titled “For Performance Issues”
  • Current performance metrics (latency, throughput)
  • Expected performance
  • Database statistics (table sizes, index status)
  • Query or operation that’s slow
  • Deployment environment (machine specs, Docker limits, etc.)

For Deployment Issues

Section titled “For Deployment Issues”
  • Platform (AWS/GCP/Azure/Kubernetes/Docker)
  • Deployment method
  • Configuration details (relevant environment variables, without secrets)
  • Error messages and logs

Etiquette Guidelines

Section titled “Etiquette Guidelines”
  1. Search first — your question may already be answered
  2. Be specific — vague questions get vague answers
  3. Be respectful — we’re all volunteers or working in our spare time
  4. Share code properly — use code blocks or GitHub gists
  5. Avoid cross-posting — ask in one place, wait for response
  6. Update others — if you solve your own problem, share the solution
  7. Say thanks — a simple “thanks!” goes a long way

Documentation and Self-Service Resources

Section titled “Documentation and Self-Service Resources”

Status and Roadmap

Section titled “Status and Roadmap”

Thank you for being part of the FraiseQL community!