Compare

Not every “drive for agents” is the same product.

A dozen products now describe themselves as storage for AI agents. They are solving at least five separate problems, and the one you have decides which of them is even a candidate.

This page is our reading of the field, including where AgentDrive is the wrong answer. Everything stated about another product is what its own public documentation said on 2026-09-09, linked so you can check it. Products change; this page is dated for that reason.

Five problems, one name

Work out which one you have.

01
A disk for the sandbox
The container your agent runs in disappears, and everything it wrote goes with it.
A POSIX filesystem, usually over FUSE, that several sandboxes mount at once. The agent uses ordinary paths; nothing above it knows a file was written.
Choose one of these if the consumer of the bytes is another process. They are built for terabytes, parallel runs and fast reads, and they are better at that than we are.
Archil · Blaxel Agent Drive · Amulet · smolfs · Turso AgentFS
02
A link a person can open
The agent produced something for a human, and the human is being handed a raw file.
The agent publishes; the product returns a URL that renders. Access is a property of the link and the reader's identity.
This is the category AgentDrive is in. Choose a lighter one if what you need is a document you can send someone, and there is no second system that has to read the same bytes back under a permission model.
Workplane · display.dev
03
A layer over storage you already have
The files are already in S3, Drive, Box or SharePoint, and you are not moving them.
A gateway that mounts, indexes or gates existing buckets and folders, then exposes them to agents over MCP with policy in front.
Choose one of these if the corpus already exists somewhere with an owner, a retention policy and an audit trail you are not allowed to duplicate.
Fastio · Mirage · Pidrive · Suprbox
04
Git, addressed to agents
The agent is writing code, and code wants branches, diffs and merges.
Git semantics behind an API shaped for machine callers rather than for a developer at a terminal.
Choose this if the artifact is a repository. Our versions are linear and immutable — good for “what did this look like last Tuesday”, wrong for “merge these two attempts”.
coregit
05
A workspace on your own machine
One developer wants their agent to stop forgetting things between sessions.
An open-source CLI or MCP server over local SQLite and disk, with an optional cloud backend.
Choose one of these while the answer to “who else needs to read this” is nobody. They install in a minute and cost nothing.
Sayou · agent-fs

Where AgentDrive differs

The rows worth arguing about, in both directions.

The AgentDrive column is our published /v0 contract, not a roadmap. The other columns describe the shape of a category rather than any one company, because a category can be summarised and a competitor cannot. The last four rows are ones we lose.

Capability by category, as documented on 2026-09-09.
Capability	AgentDrive	Sandbox filesystems	Artifact publishing	Storage front-ends	Git for agents
Grants per principal, per folderWho may read this is a property of the drive, not of who holds a link.	Yes	Varies by product	Varies by product	Varies by product	Varies by product
Public, or shared with a named personThe same artifact goes to one colleague, to anyone holding a link, or to the public — without copying it somewhere else.	Yes	No	Yes	Varies by product	No
A link that renders for a personThe reader opens a page, not a download.	Yes	No	Yes	Varies by product	No
Agent output rendered on an isolated originAn agent writes HTML. On a shared origin, that HTML runs next to your session.	Yes	No	No	No	No
Audience-bound token, checked against a local grantA credential minted for one service cannot be replayed at another.	Yes	No	No	Varies by product	No
An idempotency key on every writeAn agent that retries a timeout does not create the file twice.	Yes	No	No	No	Varies by product
Compare-and-set on every updateTwo agents editing one artifact cannot silently overwrite each other.	Yes	No	Varies by product	Varies by product	Yes
A change feed to resume fromA follower that was offline catches up without rescanning the drive.	Yes	No	No	Varies by product	Varies by product
Delete is recoverableAn agent deleting the wrong folder is a Tuesday, not an incident.	Yes	No	Varies by product	Varies by product	Yes
POSIX mountThe agent writes to a path and no API is involved.	No	Yes	No	Varies by product	Varies by product
Branch and mergeTwo attempts at the same work reconcile into one.	No	Varies by product	No	No	Yes
Semantic searchFinding the file by what it means rather than the words in it.	No	No	No	Varies by product	Varies by product
Fronts storage you already ownThe corpus stays in the bucket that has the retention policy.	No	Yes	No	Yes	No

●yes · ◐ varies by product · ○ no · as documented on 2026-09-09

What AgentDrive does not do

Seven reasons to close this tab and use something else.

There is no mount: AgentDrive is an HTTP API and an MCP server. If your agent needs to run a build over a directory, mount one of the filesystems above and hand the result here.
Search is lexical: Words, phrases, negation and OR over names, metadata and text. It will not find a document by meaning, and it does not read inside binaries.
Versions are a line, not a tree: Every write appends an immutable version you can restore as head. There is no branching and no merge.
Sharing by name reaches your workspace: A drive, folder or artifact can be granted to a teammate by name or email address, but the address has to belong to someone already in the workspace — outside it, the answer is to invite them, not to share. For a reader who will never be a member, the route is a share link or a public one.
No comments yet: A reader can open a rendered artifact and read it. Saying something back about it happens somewhere else.
Inline uploads stop at 15 MB: Larger files go through a direct upload session to object storage instead.
The contract is still beta: The /v0 surface is marked beta in the OpenAPI we serve, and it can still change before we call it stable. Pin what you build against it.

The field

Everything we looked at.

Read down Choose it when and stop at the line that describes what you are doing. Everything here comes from the page linked on each product; a question one does not answer publicly is left unanswered rather than guessed at.

When to choose each product and when not to, as documented on 2026-09-09.
Product	Choose it when	Look elsewhere if	Availability
AgentDrive	People and agents both need the same artifact, and who may read it has to be a property of the drive rather than of who holds the link.	Your agent needs a directory to run a build in, or the artifact is a repository that has to branch and merge.	Beta, no waitlist
A disk for the sandbox
Archil	Agents work over data already in S3, GCS or NFS at a size you will not copy, and you want it as an ordinary mount.	What the agent produces is a document for a person to read.	Published pricing and SLA
Blaxel Agent Drive	Several sandboxes need one shared working directory with concurrent writes.	You need version history, or you are outside the one region it runs in.	Private preview, one region
Amulet	Parallel runs need to fork a large dataset without copying it, then reconcile.	You need a documented access model today.	Private beta
smolfs	You want volumes that survive a run, in your own infrastructure, with no vendor in the path.	More than one person needs governed access to the same files.	Open source, Apache-2.0
Turso AgentFS	You want one agent's files, state and tool-call log in a single file you can copy and replay.	Several agents or people need the same workspace at once.	Open source
A link a person can open
Workplane	An agent should publish a readable page that colleagues comment on, today, at no cost.	Another system has to read the same bytes back under a permission model.	Free for individuals
display.dev	Agent-written pages should sit behind your company SSO, with outside reviewers let in one at a time.	You need an API surface for agents beyond publishing and republishing.	Free tier, paid from €15/month
A layer over storage you already have
Fastio	The corpus is already in Drive, Dropbox, Box or OneDrive, and it is staying there.	The artifact is created by the agent rather than found by it.	Trial, paid from $29/month
Mirage	Agents need one namespace over many services, with a policy engine deciding each command.	You want somewhere durable to put things rather than a gateway to reach them.	Not documented
Pidrive	You want an S3 bucket as a mount and the ordinary Unix tools, quickly.	You need version history or a permission model.	Free tier, paid tiers published
Suprbox	The problem is what an agent may read from storage you already have.	You need somewhere for what the agent produces to go.	Not documented
Git, addressed to agents
coregit	The artifact is a repository, and agents commit and merge at machine rate.	The artifact is a document a person opens.	Free tier, pay-per-use above it
A workspace on your own machine
Sayou	One developer wants an agent's markdown workspace versioned between sessions.	The work has to be shared with anyone else.	Open source
agent-fs	One agent needs a searchable local store, including SQL over stored tabular files.	Several principals need access decided per resource.	Open source, MIT

A disk for the sandbox

Archil
A serverless filesystem that turns a bucket into a mount.
How an agent reaches it
POSIX mount over FUSE, S3 API, SDKs
Whose bytes
Fronts your buckets
Versioning
Versioned disks, branches, checkpoints
Access model
Layered per-customer and per-agent policies
What a person opens
Web console with version history
Source: archil.com, 2026-09-09
Blaxel Agent Drive
A shared filesystem several sandboxes mount at the same time.
How an agent reaches it
POSIX mount over FUSE, CLI
Whose bytes
Holds the bytes
Versioning
Not documented
Access model
Workload identity and path rules
What a person opens
Console and CLI
Source: docs.blaxel.ai, 2026-09-09
Amulet
A high-performance filesystem for parallel agent workloads.
How an agent reaches it
Linux directory mount
Whose bytes
Holds the bytes
Versioning
Snapshot, fork, merge, roll back
Access model
Not documented
What a person opens
Not documented
Source: amulet.so, Y Combinator company page, 2026-09-09
smolfs
Durable volumes an agent mounts and unmounts between runs.
How an agent reaches it
CLI, Python and TypeScript bindings
Whose bytes
Holds the bytes, local disk or S3
Versioning
Not documented
Access model
Read-only or read-write mounts
What a person opens
None
Source: github.com/CelestoAI/smolfs, 2026-09-09
Turso AgentFS
Agent state as a filesystem, implemented as a database.
How an agent reaches it
TypeScript and Rust SDKs, FUSE on Linux
Whose bytes
Holds the bytes, one SQLite file
Versioning
Snapshot by copying the file
Access model
Not documented
What a person opens
None
Source: turso.tech/blog/agentfs, 2026-09-09

A link a person can open

Workplane
“Turn scattered Markdown and HTML files into one shareable link. Humans review it. Agents build on it.”
How an agent reaches it
MCP skill, published from the conversation
Whose bytes
Holds the bytes
Versioning
History with attribution, rollback
Access model
Per-page visibility, private by default
What a person opens
Rendered page, inline comments
Source: workplane.co, 2026-09-09
display.dev
Permanent URLs for the HTML and Markdown an agent writes.
How an agent reaches it
MCP and CLI
Whose bytes
Holds the bytes
Versioning
History retained on paid plans
Access model
Company SSO, three visibility tiers
What a person opens
Rendered page, comments
Source: display.dev, 2026-09-09

A layer over storage you already have

Fastio
A storage layer that fronts the drives a company already has.
How an agent reaches it
MCP, CLI, API
Whose bytes
Fronts Drive, Dropbox, Box, OneDrive
Versioning
History and file locks
Access model
Project level, people and agents
What a person opens
Not documented
Source: fast.io, 2026-09-09
Mirage
A virtual terminal: one filesystem over many services.
How an agent reaches it
Virtual filesystem, virtual CLIs, FUSE
Whose bytes
Fronts S3, Drive, Slack, GitHub, databases
Versioning
Not documented
Access model
Per-agent profiles, scriptable policy engine
What a person opens
Not documented
Source: strukto.ai, 2026-09-09
Pidrive
S3 as a filesystem, driven with the ordinary Unix tools.
How an agent reaches it
WebDAV mount, Unix tools, CLI
Whose bytes
Fronts S3
Versioning
Not documented
Access model
Share by link or by agent address
What a person opens
Share link
Source: pidrive.ressl.ai, 2026-09-09
Suprbox
A policy gate in front of the data an agent may read.
How an agent reaches it
Scoped key in front of your storage
Whose bytes
Fronts your storage
Versioning
Not documented
Access model
Rules by sensitivity, time and rate; human approval
What a person opens
Not documented
Source: Product Hunt listing, 2026-09-09

Git, addressed to agents

coregit
A serverless Git API for agents that commit at machine speed.
How an agent reaches it
REST, Git Smart HTTP, TypeScript SDK
Whose bytes
Holds the bytes
Versioning
Full Git: branch, diff, merge, snapshots
Access model
API keys with roles, scoped per organisation
What a person opens
Dashboard for keys and repos
Source: coregit.dev, 2026-09-09

A workspace on your own machine

Sayou
A versioned file workspace an agent keeps between sessions.
How an agent reaches it
MCP, installed with pip
Whose bytes
Holds the bytes, SQLite or MySQL and S3
Versioning
Append-only, full history and diffs
Access model
Not documented
What a person opens
Not documented
Source: Show HN post by its author, 2026-09-09
agent-fs
A persistent, searchable filesystem for a single agent.
How an agent reaches it
CLI, REST, MCP, FUSE mount
Whose bytes
Holds the bytes
Versioning
Versioning over SQLite-backed storage
Access model
Not documented
What a person opens
Browser viewer
Source: github.com/desplega-ai/agent-fs, 2026-09-09

If the reader at the end of the work is a person, and something other than that person also has to read the same bytes under a permission you can name — that is the drive we are building.

Open AgentDrive What AgentDrive is

AgentDrive is in beta — sign in and create a drive, there is no waitlist. If we have described your product wrongly on this page, write to support@team.tokencanopy.com and we would rather fix it than keep it.