Contact & Support
Get help with SLOzy through the following channels.
GitHub
- Issue Tracker: github.com/philyuchkoff/slozy/issues Report bugs, request features, or track development progress.
- Discussions: github.com/philyuchkoff/slozy/discussions Ask questions, share configurations, and discuss best practices with the community.
Email
For commercial support, security issues, and sales inquiries:
- Support: support@slozy.net
- Sales: sales@slozy.net
- Security: security@slozy.net
Response times:
| Plan | Response Time | Hours |
|---|---|---|
| Free | 72 hours | Business hours |
| Standard | 24 hours | Business hours |
| Pro | 4 hours | 24/7 |
Community
- Slack: Join the #help channel (invite link available on the SLOzy website)
- Live Chat: Available 24/7 on slozy.net for Pro customers
Resources
- Documentation: slozy.net/docs
- Status Page: status.slozy.net — Check platform availability
- API Reference: Full API documentation in the API section
Filing a Good Bug Report
When submitting a GitHub issue, include:
- Environment: SLOzy version, deployment method (Docker/K8s/native), PostgreSQL version
- Steps to reproduce: Clear, numbered steps
- Expected behavior: What should happen
- Actual behavior: What actually happens
- Logs: Relevant application logs with timestamps (enable
LOG_LEVEL=debug) - Configuration: Relevant .env settings (redact secrets)
Security Vulnerabilities
For security vulnerabilities, do not open a public GitHub issue. Email security@slozy.net directly. We aim to acknowledge receipt within 24 hours and provide a fix timeline within 72 hours.