We’re here to help

OroQ Support Guide

Pick the right lane and we’ll respond with clear SLA expectations, from feature asks to incident response.

Open Discussions View on GitHub
Service status: Operational · Best-effort OSS support
Scroll for contact options

Contact matrix

Choose the path that matches your request type.

Questions
General & onboarding
GitHub Discussions
Community + maintainer follow-up in 5 business days.
Product
Feature suggestions
Feature Request issue
Reviewed in quarterly roadmap planning.
Quality
Bug reports
Bug Report issue template
Triage in 3 business days; schedule by severity.
Production
Incident escalation
Priority bug + operations@cyberheroez.co.uk
Ack in 1 business day; status updates until resolved.
Security
Responsible disclosure
Security Advisory or dipesh@cyberheroez.co.uk
Initial response within 48 hours; coordinated disclosure.

Operational commitments

Best-effort timelines you can plan around.

Maintenance releases
At least once per quarter.
Critical hotfixes
Within 3 business days after confirmation.
Docs alongside changes
Whenever UI/behaviour changes ship, docs update too.

Response matrix

How we acknowledge and ship fixes based on severity.

P1 · Critical
  • Ack: within 1 business day
  • Fix: hotfix planned in 3 business days
  • Channel: priority bug + email
P2 · Major
  • Ack: within 3 business days
  • Fix: targeted in next release
  • Channel: bug report
P3 · Minor
  • Ack: within 5 business days
  • Fix: scheduled when bandwidth permits
  • Channel: bug/feature request

Self-service resources

Quick links to unblock yourself fast.

Product overview
Features, benefits, and positioning.
Privacy policy
Data handling and on-device guarantees.
Security policy
Vulnerability reporting and disclosure.
Deployment guide
Rollout steps, packaging, enterprise tips.

Need a bespoke support agreement? Fork the repository or open a discussion to coordinate sponsorship/commercial support.