Skip to content

Fyle for engineering firmsShared calculations, CAD and reports, with every change attributed

Engineering teams pass calculations, CAD files and reports between disciplines and offices. Fyle is a desktop drive for macOS, Windows and Linux where people and AI agents use the same files, and where a change based on an old version is never saved over the current one.

Create an accountSee an agent at work

When the wrong version wins, the cost is high

A calculation or drawing edited from an out-of-date copy can quietly replace the current one. Locking avoids that but slows teams in different offices down.

Agents can now check reports against standards or update spreadsheets, but most drives give them no way to propose a change for an engineer to approve.

How Fyle fits

Fyle is in development. This is what exists today and what is planned, marked on every line.

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
  • 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

  • macOS, Windows and Linux at launch: Finder, File Explorer and a FUSE mount, so analysis tools on Linux see the same files.Planned: desktop launch
  • A save based on an older version becomes a branch; the current calculation stays in place until someone decides.Planned: desktop launch
  • Review rules by folder, for example /calcs/ to the checking engineer.Planned: review
  • Agents run with fyle agent in their own session and land changes per policy.Planned: agent layer
  • SSO, SCIM, full audit log and bring-your-own storage for larger firms.Planned: Enterprise

An agent at work

The agent reads the analysis outputs and rewrites the load-case summary table. The summary sits in /calcs/, which policy protects, so the change becomes a branch for the checking engineer.

$ cd ~/Fyle/projects/bridge-a14
$ fyle agent codex --task "Update the load-case summary from the latest analysis outputs"

Session ended · 2 changes
  notes/load-case-changes.md    new
  calcs/load-case-summary.xlsx  branched (protected folder)
1 file landed. 1 branch waiting for review by @checking-engineers.
Illustration of a planned workflow. Names are examples; commands and output may change before release.

Client confidentiality and records

  • Every committed version is immutable and records its author, so you can show what a document said at a point in time.
  • Enterprise plans include configurable version retention and legal hold (planned).
  • Agents get least-privilege, short-lived access to the folders a person grants, and never a person’s own session (planned).

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

Try Fyle when the drive is ready.

Create an account

Sources

Last checked: . Regulatory points link to the regulator’s own guidance. Competitor facts live on the comparison pages, each with its sources.

  1. 1.Fyle vs Nasuni (sourced comparison)/compare/fyle-vs-nasuni
  2. 2.Fyle vs CTERA (sourced comparison)/compare/fyle-vs-ctera
  3. 3.Fyle vs LucidLink (sourced comparison)/compare/fyle-vs-lucidlink