A friendlier Git client for creative teams

Fast file locking.
A familiar workflow.

Depot Desk is a heavily opinionated Git client for teams working with large, hard-to-merge files. It turns technical Git concepts into clear actions: Check Out, Get Latest and Submit.

Familiar to teams coming from Perforce, Plastic SCM, Vault, Alienbrain and other checkout-style source control systems.

Depot Desk showing a populated Wildwood game repository with familiar workspace folders, file status and details
A real Depot Desk workspaceCurrent alpha interface · Fictional project data

The familiar part stays familiar

Check out. Edit. Submit.

Your team should not need a Git vocabulary lesson before changing an asset. Depot Desk guides the whole job and keeps the technical machinery out of the way.

01

Check Out

Select the files or folders you need. Depot Desk opens them for edit and secures any required locks on the server.

02

Edit in your usual tools

Work in Unreal, Unity, Blender, Adobe apps or any Git-aware application. The Workspace shows which files are open for edit or have been modified.

03

Submit

Group local changes into multiple sets, each with its own name and description. Submit one set or all changes together, sending them to the server and releasing their locks in a single action.

Locking without the ceremony

Locks should feel instant, not administrative.

Depot Desk makes checkout the fast path. Select what you need and carry on—locking happens inside the workflow, with ownership visible in the workspace.

01

Built around Git LFS locks

Use the lock service your Git host already supports, without a separate source-control system.

02

Files or whole folders

Check out a single asset or prepare a larger task without repeating the same action file by file.

03

Ownership stays visible

See your held checkouts and spot files another teammate is already working on.

04

Fast at project scale

Bulk and recursive checkouts are optimised for large folder trees, keeping project-scale work fast.

Opinionated by design

Git underneath. Fewer Git decisions on screen.

Depot Desk does not replace or fork Git. It gives your team a deliberately simpler way to use it.

  • The same UI on every desktopUse one familiar Depot Desk interface on Windows, Linux and macOS.
  • Works alongside other Git clientsShare the same local project with other desktop clients and Git tools built into creative apps.
  • Built on Git and Git LFSYour repository stays ordinary Git, so existing hosting, automation and build systems continue to work.
  • Technical concepts become guided actionsNo routine decisions about staging, pulling, pushing or rebasing.
  • Clear outcomes after every operationSee what changed, what was submitted and what still needs attention.

Private alpha

New client. Established foundations.

Depot Desk's client experience is in private alpha; its source-control foundation is not. It uses Git and Git LFS for repositories, history and large files rather than introducing a new source-control system.

  • The mature foundation and reliability of Git and Git LFS
  • Especially useful for games and creative production
  • Early access in exchange for practical feedback

Request access

Tell us a little about your team. We will reply personally if the current alpha is a useful fit.

Optional, but useful when we choose the first alpha teams.

We will only use these details to contact you about the Depot Desk alpha.

The short version

Questions, answered.

Is Depot Desk really Git?

Yes. It works with ordinary Git repositories and Git LFS. Depot Desk changes the everyday workflow and language, not the repository format underneath.

Who is it for?

Teams that prefer checkout-and-submit source control, especially games and creative teams working with large binary assets that cannot be merged cleanly.

Does every file need a lock?

No. Repositories can use locks only for the file types that need them. Text and code can continue to use normal Git behaviour.

What stage is the product at?

The Depot Desk client is in private alpha, and early testers will directly influence what is refined next. The source control underneath is established Git and Git LFS—not a new repository format or service.