One synced folder for your whole team β humans and agents. Share any file with people as a public URL; give every agent the same memory, synced across machines in seconds. Real files. Use the managed cloud, or self-host the whole thing in one Go binary.
Your hub stores on the object storage you already have
HOW IT WORKS
BearDrive mounts any folder as a synced volume. Your agents just write files β every editor, every tool, every agent already knows how to do that.
Init the folder. bdrive init connects the project and
starts a background daemon. Teammates run the same command and converge on
the same files within seconds.
Agents write, everyone sees β including their agents. Claude writes
wiki/report.md on your machine; moments later it's in every
teammate's folder, where their own agent reads it β attributed, versioned,
kept forever.
Share by URL. bdrive share wiki/report.md prints a
public link that renders the file as a page β always the latest synced
version, no account needed, revocable any time.
WHY BEARDRIVE
Share context across agents. The folder is shared memory. What your agent learns today β findings, plans, decisions, notes β is on your teammate's disk in seconds, so their agent starts tomorrow's session already knowing it. Context stops being siloed per laptop; every agent on the team reads from, and writes to, the same brain.
Share files with people. Anything in the folder is a
bdrive share away from being a public URL that renders as a page β
markdown, HTML, PDFs. No accounts for viewers, no "can you re-send that?",
always the latest version, revocable any time. Dropbox-link simplicity for
everything your team produces.
See what your agents actually read. Every change is attributed to the human, agent, or device that made it β and BearDrive's Insights show which files your agents lean on and which "hot but stale" docs the team relies on that nobody maintains. Agents aren't just users of the folder; they're measured.

FEATURES
Sync is table stakes. What agent teams actually need is provenance, shareability, and a security model that assumes files are written by software.
Real files, zero lock-in. Not a virtual filesystem, not an API. A normal folder on disk β grep it, open it in your editor, point any agent at it. Stop syncing any time; the files stay.
Every change tracked, forever. Who changed each file, when, from which device β every past version viewable and downloadable. An agent overwriting your doc is an annoyance, not a loss.
Gated links your agents hand you. When Claude writes or updates a file, it drops a link right beside the path β a hub link that only opens for signed-in teammates on the project. Safe to paste in any internal channel; the turn-start hook teaches every agent to do it automatically.
Public share links. Need it truly public? Any synced file becomes a rendered page at an unguessable URL: HTML as a page, markdown Obsidian-style, PDFs inline. Sandboxed, rate-limited, living until you revoke it.
Teams & organizations. Projects belong to your org; only members see or sync them. Invite a teammate with one expiring link. Accounts, device registry, and history come built in.
Offline-first, conflict-safe. Append-only journals and deterministic replay: devices converge without a coordination server, and concurrent edits keep both versions as conflict copies.
Bring your own storage. Your hub is backed by S3, GCS, R2, MinIO, or a plain shared directory β nothing but dumb object storage. Clients sync through the hub over HTTPS and never hold cloud credentials at all.
CLAUDE CODE & COWORK
wiki/q3-findings.md.
It's already syncing to the team; here's the link (sign-in required, so
it's safe to paste anywhere):wiki/q3-findings.md β synced to this machine
four minutes ago β churn concentrated in self-serve accounts, andβ¦GET BEARDRIVE
The entire product is open source under AGPL-3.0 β server, teams, history, share links, nothing held back. Or skip the buckets entirely β BearDrive Cloud is live at app.beardrive.ai.
bdrive web is the viewer, uploads, and sync hubbdrive login, and goSign up for the managed cloud and go, or brew install and self-host in one binary. Files travel to people as URLs; context travels to every agent on the team.