BearDrive icon

BearDrive

BearDrive is a shared folder for AI agents that keeps their work as real files with links, full version history, and attribution. It is free during beta as a managed service, and the open source core can be self-hosted forever.

BearDrive

What BearDrive does

BearDrive is a shared folder for AI agents. It gives teams a place where agents can read and write real files at real local paths, with links and version history attached after the fact.

The product is aimed at teams that want agent output to live in files rather than inside a chat window, wiki page, or one-off attachment. The site shows it being used for team artifacts, wikis, business context inside code repos, and personal or shared knowledge bases.

Features

Real files in real folders

Agents work in a shared folder rather than pushing content through a separate page editor or attachment flow. The folder sits at a real local path, so files stay usable outside BearDrive.

Versioned file history

New files are linked after they are written, and the homepage says a full history is available seconds later. The product keeps every version instead of replacing older copies.

Attribution for edits

BearDrive records who wrote a file and includes account, device, and agent session attribution in the compare page examples. That makes it easier to trace changes across teammates and machines.

Managed service for teams

The pricing page says managed beta teams get storage, backups, and updates handled by BearDrive. Teams that do not want to run infrastructure can use the hosted option during beta.

Open source self-hosting

The complete server is open source under AGPL-3.0, and the pricing page says it can be self-hosted on S3, GCS, R2, MinIO, or plain disk. The product is designed to move between managed and self-hosted setups.

Works alongside existing tools

The compare and use-cases pages show BearDrive sitting alongside Notion, memory tools, git, and drive sync tools rather than replacing them. It is meant to be the shared file layer those systems point at.

Use cases

  • Share team artifacts

    Marketing, operations, design, and founder teams can collect agent output in one folder that every teammate's agent can read. That avoids repeated copying, uploading, and pasting when the work needs to stay in files.

  • Keep a wiki and its working files separate

    Teams that keep their docs in Notion can place BearDrive underneath it for the working files agents actually produce, such as reports, CSVs, PDFs, and decks. Notion remains the human-facing wiki layer while BearDrive holds the underlying files.

  • Add business context to a code repo

    Engineering teams can keep customer calls, account notes, and roadmap rationale in a context folder that is synced into the repo. Coding agents then have the business context in the same place as the code they are modifying.

  • Turn a personal knowledge base into a shared one

    People who already use markdown-based knowledge bases, such as an OKF bundle, a gbrain repo, or an Obsidian vault, can turn that local content into a shared company brain without exporting or adopting a new schema.

  • Maintain a personal notebook with selective sharing

    A researcher, writer, or consultant can run a versioned notebook that an agent maintains while sharing only selected pages through a public link. Sharing is described as file-level, not folder-level.

Pros and Cons

Pros

  • Stores agent output as real files that remain usable outside the product.
  • Keeps full file history and makes earlier versions easy to restore.
  • Offers both a managed beta service and a free self-hosted open source core.
  • Supports moving between managed and self-hosted setups with export and import flows.
  • Fits alongside existing tools such as Notion, git, memory tools, and drive sync rather than forcing a replacement.

Cons

  • The site does not yet document a full integration list, so support for specific tools is only shown in a few examples.
  • The pricing page says managed team plans will be paid later, but no price has been announced.
  • The product is still in beta, so some details such as setup and plan structure are intentionally not finalized.

FAQ

What does BearDrive cost right now?

BearDrive is free during beta on the managed service, and the open source core is free forever if you self-host. The pricing page says it does not ask for payment details during beta.

Can I switch from the managed service to self-hosting later?

Yes. The pricing page says you can move from the managed service to self-hosting later, and it also says the export and import flow works in both directions against any hub.

Does BearDrive keep file history?

BearDrive keeps every version of every file, and the pricing page says restoring an earlier version is a click.

Can I run BearDrive myself?

Yes. The server is open source under AGPL-3.0, and the pricing page says self-hosting is free forever on your own storage.

What kind of workflows is BearDrive for?

The source describes BearDrive as a shared folder that AI agents read and write, with real files at real paths and links created after files are written. The use-cases page also says it can support team artifacts, a team wiki, business context in a repo, and personal notebooks.

Quick Facts

Category
AI file workspace
Product type
Shared folder for AI agents
Platform
Managed service in beta; open source self-hosted server
License
AGPL-3.0 for the server
Primary users
Teams using AI agents, plus individuals managing notebooks or multi-device context
Website
beardrive.ai