Contact
Tell us what you are trying to do
The useful conversations start with the constraint, not the feature list: how many devices, what you are replacing, and what has to be true before you could deploy it.
General and sales
Evaluating it, pricing a supported arrangement, or asking whether it fits what you have.
[email protected]Security reports
Send it here first. We will confirm receipt, agree a timeline with you, and credit you unless you would rather we did not.
[email protected]Bugs and questions
Anything reproducible is better as an issue, where the answer stays findable for the next person.
GitHub issuesDisclosure
How we handle a security report
- We confirm receipt and tell you whether we can reproduce it, rather than going quiet while we work.
- We agree a disclosure date with you. If a fix is going to take longer than expected, you hear that from us before the date, not after it.
- We publish the fix and the reasoning. Both forks are public, so the patch is visible whether or not we write about it, which means we would rather write about it.
- Please do not test against somebody else’s deployment. A local one takes an afternoon to stand up, and the self-hosting guide is written for exactly that.