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 ($20/mo) | Team ($49/mo) | Enterprise | |---|---|---|---|---| | Channel | GitHub Issues | Email | Email | 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:

GitHub Discussions

For longer-form questions, architecture advice, and community conversation:

Documentation

Before opening an issue, check:

Email support (Pro and above)

How to contact

Send an email to support@tameflare.com with:

  1. Your plan tier (Pro / Team / Enterprise)
  2. TameFlare version (TameFlare --version or check the dashboard footer)
  3. Description of the issue
  4. Steps to reproduce (if applicable)
  5. 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 | | Your First Policy | Step-by-step policy tutorial | | Troubleshooting | Common problems and fixes | | Failure Modes | Behavior under failure conditions | | Environment Variables | Complete env var reference | | API Reference | Full API documentation | | 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