Skip to content

Fyle for architecture practicesLarge project files, every app, and agents that can’t overwrite a model

Practices work with large models, drawing sets and photos that many people open from the desktop. Fyle is a desktop drive that streams files when they are opened, keeps every version, and turns a clashing save into a branch for the right person to review.

Create an accountSee an agent at work

Big files, many hands, and binaries that can’t be merged

Models and drawings are binary files: two edits can’t be merged line by line, so most drives fall back to locks or conflicted copies. Locks stall work when someone forgets to release them.

AI tools are starting to help with schedules, specifications and document checks. They need the same project files people use, without the risk of silently replacing a model someone else is working on.

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

  • Projects mount in Finder and File Explorer on macOS and Windows; files download when opened and stay cached.Planned: desktop launch
  • No locks: a save based on an older version becomes a branch, and the current model stays in place.Planned: desktop launch
  • Review rules by file type or folder, for example *.rvt to the BIM team. Reviewers compare versions side by side and keep current, take the branch or keep both.Planned: review
  • Agents work in their own session folder, so their changes are recorded separately and land per policy.Planned: agent layer
  • Bring your own S3-compatible storage for practices that need data in their own account.Planned: Enterprise

An agent at work

The agent reads the schedule export and the specification, writes a list of mismatches and proposes corrections to the schedule spreadsheet. A technologist updated that spreadsheet during the session, so the proposal becomes a branch.

$ cd ~/Fyle/projects/riverside-library
$ fyle agent claude --task "Check the door schedule against the specification and list mismatches"

Session ended · 2 changes
  checks/door-schedule-mismatches.md  new
  schedules/doors.xlsx                branched (edited by a technologist during the session)
1 file landed. 1 branch waiting for review by @bim-team.
Illustration of a planned workflow. Names are examples; commands and output may change before release.

Client confidentiality and ownership of the work

  • Every version records who made it and from which device or agent session, which helps when you need to show how a drawing changed.
  • Agents only see the projects you grant them, with short-lived access (planned).
  • Project data that includes personal data, such as residents’ details, falls under UK GDPR. UK-only workspaces are planned for Enterprise.

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.ICO: UK GDPR guidance and resourcesico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/
  2. 2.Fyle vs LucidLink (sourced comparison)/compare/fyle-vs-lucidlink
  3. 3.Fyle vs Egnyte (sourced comparison)/compare/fyle-vs-egnyte
  4. 4.Fyle vs Nasuni (sourced comparison)/compare/fyle-vs-nasuni