Skip to content

Fyle for game studiosA drive for the files that don’t live in version control

Studios keep code and engine assets in version control, but concept art, audio sessions, design documents, marketing assets and builds often live on a shared drive. Fyle is that drive, with every version kept, branches instead of locks, and agents that work in their own session.

Create an accountSee an agent at work

Not everyone on the team uses version control

Artists, writers, producers and audio designers work in desktop apps, not commits. Their shared folders still need history and a way to handle two people saving the same file.

Agents can now batch-process assets and keep design documents up to date, which means many more writes to shared files.

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
  • 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, so build machines and artists see the same folders.Planned: desktop launch
  • No locks: a save based on an older version becomes a branch for a named reviewer.Planned: desktop launch
  • Review rules by folder or file type, routed to leads.Planned: review
  • Agents run in their own session with access only to the folders you grant, plus an MCP server for remote agents.Planned: agent layer
  • Bring your own S3-compatible storage and dedicated deployments for larger studios.Planned: Enterprise

An agent at work

The agent renames the dialogue files to the studio convention and updates the dialogue spreadsheet. The audio lead edited the sheet while the session ran, so that update becomes a branch.

$ cd ~/Fyle/project-tidewater/audio
$ fyle agent codex --task "Normalise file names in the dialogue folder and update the dialogue sheet"

Session ended · 2 changes
  dialogue/ (96 files renamed)  modified
  dialogue-sheet.xlsx           branched (edited by the audio lead during the session)
Renames landed. 1 branch waiting for review by @audio-lead.
Illustration of a planned workflow. Names are examples; commands and output may change before release.

Unreleased IP

  • Agents can only reach the folders you grant them, with short-lived access, and never a person’s own session (planned).
  • Every version records who made it, from which device, and which agent session.
  • Enterprise: full audit log, opt-in download audit (first download per device) and SIEM export (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 Diversion (sourced comparison)/compare/fyle-vs-diversion
  2. 2.Fyle vs LucidLink (sourced comparison)/compare/fyle-vs-lucidlink
  3. 3.Fyle vs Space (sourced comparison)/compare/fyle-vs-space