# Fyle for enterprise

**A governed file layer for people and agents, on your own storage**

Large engineering, design, media and research organisations are starting to run many agents against shared files. Fyle’s Enterprise plan is built for that: the coordinator runs on top of your own storage, every agent has scoped credentials, and review rules decide who approves what.

## Agents multiply the writes; governance has to keep up

Each agent is another writer on shared files. Locks stall them, last-write-wins loses work, and conflicted copies pile up without an owner.

Security teams need agents to authenticate like any other client, with least privilege and an audit trail they can export.

## How Fyle fits

Available now:

- Organisations with roles: owner, admin, billing, member and viewer. (Available now)
- Two-factor sign-in with an authenticator app, which an organisation can require for everyone. (Available now)
- Organisation security policies: maximum session age, idle time-out and how often desktop devices must sign in again. (Available now)
- Device sign-in for the desktop app and CLI: approve a short code in the browser, with no password typed into a terminal. (Available now)

Planned:

- Bring your own S3-compatible storage, checked by an automated compatibility suite before activation. (Planned: Enterprise)
- Region-locked workspaces covering content, metadata, indexes, logs and backups; UK-only via your UK bucket and a UK-hosted coordinator. (Planned: Enterprise)
- SSO (SAML and OIDC) with enforced sign-in, and SCIM provisioning. (Planned: Enterprise)
- Review rules in a CODEOWNERS-style file, escalation, and auto-resolve rules such as agents always branch. (Planned: review)
- Full audit log, opt-in download audit, SIEM export, configurable retention and legal hold. (Planned: Enterprise)
- Deployment: Fyle-hosted dedicated, in your cloud account, or on-premises. (Planned: Enterprise)

## An agent at work

The agent edits the runbooks that mention the old endpoint. Policy requires review for all agent changes in this workspace, so every edit becomes a branch, grouped as one session for the owning team to approve.

```
$ cd ~/Fyle/platform/runbooks
$ fyle agent codex --task "Update every runbook that references the old alerting endpoint"

Session ended · 3 changes
  alerts/paging.md      branched (policy: review all agent changes)
  alerts/escalation.md  branched (policy: review all agent changes)
  db/failover.md        branched (policy: review all agent changes)
3 branches waiting for review by @sre, as one session.
```

Illustration of a planned workflow. Names are examples; commands and output may change before release.

## Security, residency and compliance

- Agents are untrusted clients: scoped, short-lived grants on the same authorisation path as the desktop drive.
- Every row of data belongs to an organisation, so policies, audit and billing apply per organisation.
- Fyle has no certifications yet. Cyber Essentials Plus, then ISO 27001 or SOC 2, are on the Enterprise roadmap.
- Fyle plans to publish a data processing agreement and its subprocessors. Enterprise is sold on custom annual contracts.

Not legal advice. Fyle features mentioned here are planned unless marked available now.

## Related comparisons

- [Fyle vs Egnyte](https://fyle.sh/compare/fyle-vs-egnyte)
- [Fyle vs Nasuni](https://fyle.sh/compare/fyle-vs-nasuni)
- [Fyle vs CTERA](https://fyle.sh/compare/fyle-vs-ctera)

## Sources

Last checked: October 2026.

1. [ICO: UK GDPR guidance and resources](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/)
2. [ICO: contracts and liabilities between controllers and processors](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/contracts-and-liabilities-between-controllers-and-processors-multi/)
3. [Fyle vs Egnyte (sourced comparison)](https://fyle.sh/compare/fyle-vs-egnyte)
4. [Fyle vs Nasuni (sourced comparison)](https://fyle.sh/compare/fyle-vs-nasuni)
5. [Fyle vs CTERA (sourced comparison)](https://fyle.sh/compare/fyle-vs-ctera)