The shape of the plans
Every plan on the pricing page counts the same two things: named users inside your organization, and a monthly transfer allowance. Recipients, guest uploaders and Shared Inbox senders are not counted. An agency delivering to forty clients and a studio delivering to two pay for their own people, not for who they deliver to.
| Plan | Price | Per file | Notes |
|---|---|---|---|
| Free | $0 | 10 GB | 3 named users, 1 Shared Inbox, 25 GB of transfer a month. Does not expire. |
| Starter | $99/mo | 100 GB | For a team that sends every week. |
| Professional | $499/mo | No limit | Adds API, CLI, webhooks, SAML SSO, roles and full audit. |
| Business | $1,499/mo | No limit | Adds SCIM and larger allowances. |
| Enterprise | From $2,500/mo | No limit | Deployment and support terms agreed per customer. |
Why not meter the gigabytes or the recipients
Per-gigabyte pricing makes the product more expensive exactly when it is doing its job. A team that moves 50 TB a month is the team that needs a transfer product; charging them per byte turns every large delivery into a cost conversation and pushes people back to shipping drives. Per-recipient pricing does the same to the teams with the most clients. Both models optimise for customers who use the product less.
The transfer allowance on each plan is there so that the infrastructure behind hosted control and support scales with use, and it is published so you can plan for it. It is not metered at a per-gigabyte rate, and exceeding it is a conversation about the next plan rather than a surprise invoice.
The Free plan is not a trial. It has no expiry, and its limits are enough to send real work: a 10 GB master, a folder of any file count within the monthly allowance, a Shared Inbox for a vendor. We would rather you find out on your own files whether the product is worth paying for.