How to get help.
The fastest path depends on what you’re doing. Integration questions go to docs. Bugs, feature requests, account, billing, and production-impacting issues go to email.
- General questions + account: support@rungate.dev
- Security: security@rungate.dev
- Bugs + feature requests: support@rungate.dev
- Status: /status
Channels
Documentation
Setup guides, API reference, integration patterns, policy examples, troubleshooting.
Open docsAgent-native reference
If you’re an AI agent, start here. Code examples, OpenAPI, FAQ, evaluation prompts.
Open /agentsBug reports + feature requests
Email with steps to reproduce, expected vs. observed behavior, and (if applicable) the agent scenario the request unblocks.
support@rungate.devAccount, billing, production incidents. For security-specific issues use the security address.
support@rungate.devResponse times
Targets, not guarantees. SLA-backed response times are available on Enterprise.
| Tier | First response | Channels |
|---|---|---|
| Free | Best effort | Email, community |
| Pro | 2 business days | |
| Growth | 8 business hours | Email + shared Slack |
| Enterprise | Per SLA (custom) | Dedicated channel + named contact |
Feature requests
Email support@rungate.dev with the subject line “Feature request”. If you can articulate the agent scenario it unblocks — not just “it would be nice if” — the request moves faster. We prioritize by weighted impact across dogfood use, customer commitments, and category-defining scope.
Incident reporting
Production-impacting issues: email support@rungate.dev with “INCIDENT” in the subject line plus your organization ID. Include: timestamp, run IDs affected, expected vs. observed behavior, and impact scope. Security issues: security@rungate.dev — see the security page for disclosure policy.