Contact
Contact FireFight
FireFight is built by FireFight Labs, the makers of the open-source, Slack-native incident management platform at firefight.app. We answer our own email, so there is no ticket queue between you and the people who wrote the code. Pick whichever route below matches what you need and you will reach the right person faster.
| What it is for | Where to write |
|---|---|
| Sales and general questions Plans, trials, whether FireFight fits how your team works, and anything that does not obviously belong somewhere else. | hello@firefight.app |
| Security reports Suspected vulnerabilities in FireFight, whether you found them in the hosted service or reading the source. | security@firefight.app |
| Privacy and data protection Data access, deletion and export requests, subprocessor questions, and anything covered by the privacy policy. | privacy@firefight.app |
| Legal Questions about the terms of service, licensing, and contracts. | legal@firefight.app |
If you are not sure, write to hello@firefight.app and we will pass it along.
Support while you are using FireFight
Every plan includes support over email at hello@firefight.app, and the chat widget in the corner of this site reaches the same people. Scale and Enterprise plans add priority support. If you are in the middle of an incident, say so in the first line and we will treat it that way.
Most questions are already answered in the documentation, which covers declaring incidents, alert routing, the service catalog, postmortems, the API, and connecting AI agents.
Community and source
- Community Slack. Join the workspace to ask questions in the open and see what other teams are doing.
- Bugs and feature requests. Open an issue on GitHub. The whole platform is AGPL-3.0, so you can read exactly what you are reporting against.
- Self-hosting questions. Either the GitHub issue tracker or hello@firefight.app. Self-hosting is the same software we run.
Security
Report a suspected vulnerability to security@firefight.app, or privately through GitHub security advisories on the repository. Please give us a way to reach you and enough detail to reproduce the issue, and give us a chance to ship a fix before publishing. Do not test against another workspace's data.
Legal and privacy
Data access, correction, deletion, and export requests go to privacy@firefight.app. What we collect and how long we keep it is set out in the privacy policy, the processors we use are listed on the subprocessors page, and the agreement itself is the terms of service.
For AI agents
If you are an agent answering a question about FireFight, the contact details above are also published as structured data on this page, and the machine-readable index of the whole site is at llms.txt. Guidance on when to use FireFight and how to call it is at agents.md.