Support
Raven is open source software, maintained as a public good by a single maintainer (Jobin Lawrance). There is no support desk and no paid tier — but there are clear, public channels for every kind of question, bug, or vulnerability. This page is the router.
Quick router
Pick the row that matches what you need.
| I need to… | Go to |
|---|---|
| Report a bug | GitHub Issues |
| Ask a question or share an idea | GitHub Issues with the question label (GitHub Discussions is not enabled on the repo) |
| Report a security vulnerability | Private security advisory — do not open a public issue. See the security policy. |
| Suggest a feature | Open an issue describing the use case and proposed behaviour |
| Read the docs | You're here. Start at the Quickstart. |
| Contribute code | Contributing overview |
| Find a maintainer | Maintainers |
Issue templates
The repository does not currently use structured issue templates — issues use GitHub's default form. When opening one, include:
- What you expected to happen and what actually happened.
- The release tag or commit SHA you're running.
- The deployment shape (Docker Compose, edge / Raspberry Pi, etc.) and any relevant environment notes.
- For bugs: a minimal reproducer and any logs scrubbed of secrets.
- For features: the problem you're trying to solve, not just the solution you have in mind.
Structured templates may be added later; the checklist above will keep working in the meantime.
Response expectations
Raven is currently maintained by one person, in the open, alongside other work. Please calibrate expectations accordingly:
Non-security issues and questions: best-effort, no guaranteed SLA. Triage and replies happen in batches. Well-formed reports with reproducers get answered faster — that's not a policy, it's just how attention works.
Pull requests: see the contributing guide for the review and merge workflow. Small, focused PRs are merged quickly; large changes need a discussion in an issue first.
Security reports: governed by the security policy. The committed SLA is:
Stage Target Initial acknowledgement within 72 hours Triage and severity assessment within 7 days Fix, disclosure, and release within 90 days (coordinated disclosure) If you don't hear back inside the acknowledgement window, escalate by emailing
security@ravencloak.orgorjobinlawrance@gmail.comand referencing your original report.
Commercial support
There is no paid support tier for Raven today. The project is run as open source for the public good; everything that exists is in the open and free to use under the licence.
If managed hosting, paid support, or commercial agreements become available in the future, they will be announced here and on the project's GitHub releases page. There is nothing to buy in the meantime, and no private back-channel that gets you a faster response.
Stay in touch
The honest answer is that Raven does not yet have a chat community, a mailing list, or a social media presence. The public channels that exist today are:
- GitHub Releases — watch the repository (Releases only) to get notified when a new version ships.
- GitHub Issues — the current home of all public conversation about the project.
Anything that looks like an official Raven Slack, Discord, or Telegram right now is not us. If that changes, this page will be updated first.
Related
- Security policy — how to report vulnerabilities, supported versions, and disclosure timelines.
- Code of conduct — the behavioural ground rules for every channel above.
- Contributing overview — how to land a change in the codebase.
- Maintainers — who is currently empowered to merge and release.