Support
TameFlare offers tiered support based on your plan. All users have access to community support. Paid tiers include direct email support with guaranteed response times.
Support tiers
| Starter (Free) | Pro ($29/mo) | Team ($79/mo) | Enterprise | |
|---|---|---|---|---|
| Channel | GitHub Issues | Dedicated Slack + Email | ||
| Response time | Best effort | 48 hours | 4 hours | Custom SLA |
| Scope | Bug reports, feature requests | Bug reports, configuration help, policy guidance | All Pro support + architecture review, deployment guidance | All Team support + dedicated engineer, on-call |
| Hours | Community hours | Business hours (Mon-Fri) | Business hours (Mon-Fri) | Custom (up to 24/7) |
Community support (all tiers)
GitHub Issues
Report bugs, request features, and ask questions:
- Bug reports - github.com/tameflare/tameflare/issues
- Feature requests - use the "Feature Request" issue template
- Questions - use the "Question" issue template or GitHub Discussions
GitHub Discussions
For longer-form questions, architecture advice, and community conversation:
Documentation
Before opening an issue, check:
- Troubleshooting - common problems and solutions
- Deployment Topology - how components connect
- Security - TLS, credentials, and auth
Email support (Pro and above)
How to contact
Send an email to support@tameflare.com with:
- Your plan tier (Pro / Team / Enterprise)
- TameFlare version (
TameFlare --versionor check the dashboard footer) - Description of the issue
- Steps to reproduce (if applicable)
- Relevant logs (redact any credentials or sensitive data)
What's covered
| Topic | Pro | Team | Enterprise |
|---|---|---|---|
| Bug reports | Yes | Yes | Yes |
| Configuration help | Yes | Yes | Yes |
| Policy writing guidance | Yes | Yes | Yes |
| Architecture review | No | Yes | Yes |
| Deployment guidance | No | Yes | Yes |
| Custom connector development | No | No | Yes |
| On-site / video call | No | No | Yes |
Response time SLA
| Severity | Pro | Team | Enterprise |
|---|---|---|---|
| Critical (system down, kill switch stuck) | 48h | 4h | Custom |
| High (feature broken, data loss risk) | 48h | 8h | Custom |
| Medium (degraded performance, workaround exists) | 72h | 24h | Custom |
| Low (question, feature request) | Best effort | 48h | Custom |
Enterprise support
Enterprise customers receive:
- Dedicated Slack channel - direct access to the engineering team
- Named support engineer - consistent point of contact
- Architecture review - help designing your TameFlare deployment topology
- Custom SLAs - response times tailored to your needs
- Priority bug fixes - critical fixes prioritized for your version
- Professional services - custom connector development, policy migration, training
Contact
For enterprise inquiries: enterprise@tameflare.com
Self-help resources
| Resource | Description |
|---|---|
| Quick Start | Get running in 5 minutes |
| Writing Policies | Policy authoring guide |
| Troubleshooting | Common problems and fixes |
| Connectors | All 8 built-in connectors |
| Security | TLS, credentials, and auth |
| Changelog | What's new in each version |
Reporting security vulnerabilities
Do not report security vulnerabilities via GitHub Issues. Instead, follow the responsible disclosure process in SECURITY.md.
Email: security@tameflare.com
Next steps
- Plans & Pricing - compare tiers and features
- Troubleshooting - solve common issues
- Changelog - latest updates