Ferry for EnterpriseComing soon
The controls your
security team will ask for.
Ferry starts from a strong position: the people who run it cannot read what is sent. Enterprise adds the governance around it, so a whole organisation can use it with confidence.
Talk to us early
Tell us what your organisation needs. What we hear decides what we build first.
What we are planning
Governance without giving up privacy.
Single sign-on
Sign in with your identity provider, with SAML or OpenID Connect, and remove access in one place.
Audit logs and exports
A record of who sent, opened and removed what, that your security team can export.
Retention policies
Set how long files may be held, for the whole organisation, and enforce it.
Admin console
Manage members, storage and limits from one place, with provisioning from your directory.
Data location
Choose where held files are stored, for organisations that have to keep data in a region.
Security review
Answers to your questionnaire, a data processing agreement, and a clear list of subprocessors.
Custom limits and invoicing
Storage and file sizes that fit your work, with an invoice instead of a card.
Priority support
A named contact and a response you can plan around.
These are plans, not shipped features. They can change, and they are not a commitment to a date.
Questions
Before you get in touch
Is Ferry for Enterprise available now?
Not yet. We are talking to organisations about what they need first, and the list on this page is where those conversations start.
Does Ferry have SOC 2 or ISO 27001 certification?
Not today. If your organisation requires one, tell us. It helps us decide what to do first.
Can we use Ferry now?
Direct sends need no account and no approval. Personal accounts are opening to a few people at a time. Both are described on the pricing page.
Where can we read how Ferry protects files?
On the security page, and in the open source code that it describes.