Orchard Files

Working files, kept properly

Orchard Files is managed storage for teams that have outgrown a shared drive but do not want to run their own. Continuous sync, versioned history, and an S3-compatible endpoint for the scripts that already exist.

See pricing Read the docs

Sync that stays out of the way

The desktop agent holds one connection open and streams changes as they happen. Large files transfer in chunks and resume where they stopped, so a dropped link costs seconds rather than a restart.

History you can actually use

Every write creates a version. Restore a single file, a folder, or the whole workspace to any point inside your retention window — from the web console or the CLI.

An endpoint, not a silo

The same buckets are reachable over an S3-compatible API. Existing backup jobs, build pipelines and rclone configurations work without modification.

How it fits together

Clients connect to the endpoint nearest them and keep that connection open for the life of the session. Writes land on a replicated primary volume and are versioned on the way in; where the plan includes it, a copy goes off-site overnight.

Desktop, mobile and server clients connect to a regional endpoint over a persistent TLS session; the endpoint writes to a replicated primary volume, a version history and, where the plan includes it, an off-site copy.
A workspace as the agents see it. Nothing in the path is shared with another tenant except the network itself.

Retention, in plain terms

Recent versions are kept in full. Older ones are thinned on a fixed schedule so the history stays useful without growing without bound. The retention window is set per workspace and can be changed at any time; lengthening it applies from that day forward.

Timeline showing every write kept in full for the first 24 hours, one version per day up to 30 days, and one version per week for the remainder of the retention window.
Thinning schedule. Deleted files are held for the full window before they are removed for good.

What you get on every plan

TransportTLS 1.3 only. Older versions are refused, not downgraded.
At restAES-256 per volume, keys held on the storage nodes.
DurabilityErasure coded across three nodes. A nightly copy to a second region is included on Orchard and available on the other plans as an add-on.
Maximum object5 TB, uploaded in resumable parts.
ClientsmacOS, Windows, Linux, iOS, Android, and a static CLI binary.
APIS3-compatible: ListObjects, multipart upload, presigned URLs.
 Figures are per workspace. Limits above the published ones are arranged case by case.
Accounts are opened by request. We are a small operation and we would rather talk to you first than run a signup funnel. Write to hello@orchardfiles.com with a rough idea of your team size and how much you are storing, and we will send back a trial workspace.