Sales
Rolling our products out across a team, private instances, pricing and partnerships.
Contact
Talk to the studio
Sales for organisations, support for anything that breaks, and a phone when writing is too slow. Every one of them reaches the people who build the software — there is no ticket queue and no form to fill in.
Support
Bugs, feature requests and security reports, answered by the people who wrote the code.
Phone
To talk to the studio directly.
Which address for what
Two inboxes, so a rollout question is never queued behind a bug report, and the other way round.
business
Rolling it out across a team, or a private instance
Volume deployment, a shared catalog with rights per folder, a private sync instance, or an integration with the systems you already run. Say how many people, what policy you work under, and what you are trying to do rather than which feature you think you need.
sales@bursusofts.com
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.
support@bursusofts.com
security
You found something that should not be possible
Write to support and put “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.
support@bursusofts.comBefore 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.