layven.
Sign in

Shared drive for your agents and teammates.

Claude, ChatGPT, Gemini, and any other AI agent read and write the same files. So does the rest of your team.

Every write lands as a signed version. Everyone’s on the latest. Agent overwrote it? Restore the last good version.

Create your shared driveTwo minutes. One MCP config block. No agent code changes.
research/interviews.md03:04v14
claude-researchgpt-writergemini-editor
Sound familiar

You accepted the edit. Then you read it.

Agents work at machine speed and make machine-speed mistakes. The bad ones don't announce themselves. You find them later, in a file that used to be right.

14:26
The diff was 200 lines
You read the first twenty and hit accept. The rest replaced a week of work. The only copy of the old version was the file itself.
MAR 14
The team had old context
You rewrote the marketing and sales playbook. Half the team's agents are still reading the old version, and nobody knows which half.
03:47
Two agents, one file
One wrote while the other was still reading. The one that finished last won, and nothing recorded which one that was.

You can’t stop any of this. You can make it a non-event.

How it works

Four steps. The last one is the point.

01
Paste one config block
One MCP config block, pasted into any client that speaks it. No SDK, no library, no changes to the agents you already have.
mcp.json
"drive": {
  "url": "https://mcp.…/v1",
  "token": "ad_live_…"
}
02
Point every agent at it
Each agent gets its own token, scoped to the paths you choose. They all see one tree, and you can see which of them is in it.
workspace: launch3 agents
claude-prod/notes/
gpt-research/research/
gemini-batch/datasets/
03
Every write is signed
Every write becomes a new version stamped with the agent that made it and the second it landed. Nothing is ever overwritten in place.
/notes/launch-plan.mdv17
claude-prodwrote→ v1503:04
gpt-researchwrote→ v1603:09
backup-scriptwrote→ v1703:12
04
Everything rolls back
One file or the whole tree, back to any moment you name. The restore lands as a new version, so the undo is undoable.
/notes/launch-plan.mdv18
gpt-researchwrote→ v1603:09
backup-scriptwrote→ v1703:12
yourestored to v16→ v1808:47

You do steps one and two once. The drive does three and four forever.

Attribution

Who did what, to the second.

Every action lands in the feed with whoever made it. When something breaks, you can see who broke it, when, and what the file looked like before.

workspace: launch · activity● live
Data lost: 0
Beyond versioning

Not just a record of what happened.

History is the floor. These are the tools your agents and teammates use while the work is still happening. Every one is a call an agent can make itself.

search
Everything any agent wrote, findable
Full-text and semantic search across the whole tree. An agent that wasn't running when the notes were written can still find them.
token grants
One folder, read-only, nothing else
Scope each agent's token to a path prefix and an access level. The research agent never sees /finance/, however you phrase the prompt.
lock
For when last-write-wins isn't good enough
An agent claims a file while it works on it. The others are told, not silently overwritten. Reads are never blocked.
activity
What changed since my last run?
Agents poll one feed and pick up where another left off. A coordination bus that happens to be an audit log.
Use cases

What it's for.

Two agents, one file
Both writes land as separate versions, each named.
Agent work outside the repo
Notes, plans, and scratch files get git-grade history.
Cron jobs that misfire
A bad scheduled run is a one-click restore.
Skills the whole team uses
One copy of the skill, not six in Slack.
Datasets agents rewrite
Every transform is a version you can diff.
Proof for client work
Every change is timestamped and attributed.
Pricing

Flat price. No meters.

Reads, writes, versions, restores, and egress are included at every tier. No credits, no per-operation billing, no line item you have to explain to your agents.

Free
€0 forever

✓5 GB storage

✓30 days of version history

✓30 days of activity log

✓1 workspace

✓5 agent tokens

—Bring your own storage

✓Email support

Pro
€19 /month

✓100 GB storage

✓1 year of version history

✓90 year of activity log

✓5 workspaces

✓25 agent tokens

—Bring your own storage

✓Email support

Scale
€49 /month

✓500 GB storage

✓Unlimited version history

✓1 year of activity log

✓25 workspaces

✓100 agent tokens

✓Bring your own storage

✓Priority support

Enterprise
Custom /month

✓Custom storage

✓Unlimited version history

✓Unlimited activity log + SIEM export

✓Unlimited workspaces

✓Unlimited agent tokens

✓Bring your own storage

✓SLA + DPA

An agent fleet runs at machine speed. Metered billing turns that into a bill you cannot predict and cannot cap. One flat price is the whole point.

✓EU datacenters✓Encrypted at rest✓GDPR deletion that runs✓Files export as plain files
FAQ

Plain questions, direct answers.

Drive and S3 store files; they don’t attribute writes to agents or version every single write. GitHub versions what you commit. Agents don’t commit, they write. We version the write itself, name the agent, and make any moment restorable.

Your agents are going to break something.

The only question is whether your team can put it back.

Create your shared drive
Two minutes to mount. Works with Claude, ChatGPT, Gemini, Cursor, and anything else that speaks MCP.