SUPPORT
Something is broken, or missing
Bug reports and feature requests. Tell us which platform, which version, and what you expected instead — the version is in the application under About.
Contact
One address, read by the people who build it
There is no ticket queue and no contact form to fill in. Write, and someone who can change the code will answer.
SECURITY
You found something that should not be possible
Use the same address and say “security” in the subject. We will confirm we have it, tell you what we found, and credit you in the release notes unless you would rather we did not.
BUSINESS
Deploying it across a team, or building on it
Volume deployment, a private sync instance, or an integration against the catalog API. Say what you are trying to do rather than which feature you think you need.
Before you write about a bug
Two things make a report answerable on the first reply instead of the fourth: the exact version, and what the application did rather than what it failed to do. If a session is involved, the protocol and the server’s own software matter too — an SFTP transfer against OpenSSH and against a network appliance are not the same code path on either end.
Never send us a password, a private key, or a vault file. We cannot read your vault and we do not want a copy of one. If a reproduction seems to need real credentials, say so and we will find another way.