Enterprise support
The open-source MIT core remains the primary path. Start with the public docs, GitHub Discussions, and GitHub Issues whenever your question can be handled in public.
This page describes the private and commercial path for teams that need help beyond the public support surface.
What private support can cover
Section titled “What private support can cover”- Architecture and threat-model review for upload flows.
- Rollout planning across multiple services or frameworks.
- Policy tuning for real traffic and quarantine workflows.
- Review of logging, auditability, and operational needs.
- Prioritization of blockers affecting adoption or production rollout.
What to expect
Section titled “What to expect”- Scope is agreed before work starts.
- Support is async unless another arrangement is made.
- There is no implied SLA or 24/7 response unless explicitly contracted.
- Public bugs, docs fixes, and reproducible feature requests should still go through the public repo when possible.
If you need advanced operational capabilities
Section titled “If you need advanced operational capabilities”Some teams want capabilities beyond the current OSS surface, such as stronger audit trails, review workflows, or deeper observability. Treat those conversations as roadmap and commercial-scoping discussions first, not as currently promised product features.
Contact
Section titled “Contact”- Private or commercial inquiry: pompelmideveloper@yahoo.com
- Purchase or evaluation inquiry: Polar
Include your stack, version, upload profile, timeline, and whether the issue can be reproduced publicly.