Built with Astro, hosted on Google Cloud behind Cloudflare.
Confidence reflects how many independent signals matched.
| Technology | Version | Confidence | First seen |
|---|---|---|---|
| JavaScript Frameworks & Libraries1 | |||
| – | High | 14 Oct 2026 | |
| CDN & Hosting2 | |||
| – | High | 14 Oct 2026 | |
| – | High | 14 Oct 2026 | |
| Analytics & Tag Management1 | |||
| – | High | 14 Oct 2026 | |
| Video, Audio & Media Delivery1 | |||
| – | High | 14 Oct 2026 | |
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.combart.ns.cloudflare.comlove.ns.cloudflare.comv=spf1 include:_spf.google.com ~allgoogle-site-verification=2eXqOZvf4P2Pqf262Ex_r3cBRXLvllsTZ5buAU7qhN4# beardrive.ai # # The default here is YES. Answer engines are a distribution channel, not a # threat to it: a page that GPTBot or ClaudeBot can't fetch can't be cited, and # a citation is the one link a reader clicks after asking a question. The # training-vs-retrieval distinction is deliberate — both are allowed, because # being the source the model already knows is the same win as being the page it # fetches today. # # The app lives on this same origin (beardrive.ai is config.DefaultServer), so # the disallows below are the hub's own routes: private files, the sync API, # auth pages. They are gated server-side too — this just keeps crawlers from # wasting requests on 401s. # # There are deliberately NO per-bot groups. Under the robots protocol a crawler # obeys only its most specific matching group, so a `User-agent: GPTBot` block # saying `Allow: /` REPLACES the rules below rather than adding to them — which # silently un-disallowed /s/ and handed every share token to the training # crawlers. The wildcard group already allows everything a named group would. User-agent: * Allow: / Disallow: /api/ Disallow: /auth/ Disallow: /p- Disallow: /s/ Disallow: /join/ Disallow: /billing Sitemap: https://beardrive.ai/sitemap-index.xml
# BearDrive > One shared folder that every teammate and every AI agent on the team reads and writes. > Real files on disk, synced through a hub you can self-host, with per-file history, > access scopes and links that stay alive. Open source, AGPL-3.0. ## Docs - [Documentation index](https://docs.beardrive.ai/llms.txt): every page on docs.beardrive.ai, one line each. - [Documentation, condensed](https://docs.beardrive.ai/llms-small.txt): the same site as a single short file. - [Documentation, full text](https://docs.beardrive.ai/llms-full.txt): every docs page inlined in full. ## Blog - [How our company wiki writes itself](https://beardrive.ai/blog/company-wiki-writes-itself.md): Our company wiki took 1,817 changes in fifteen days and nobody maintained it. The five mechanisms behind it, and the 1685 method they come from. - [How our team works with AI agents through one shared folder](https://beardrive.ai/blog/how-our-team-works-with-ai-agents.md): How our team collaborates with AI agents: one shared folder, agent-to-agent handoffs, and what three HTML files named final taught us about artifacts. - [How to share context between your team's AI agents](https://beardrive.ai/blog/share-context-between-ai-agents.md): Four ways teams share context between AI agents — pasting, a repo, an MCP server, a synced folder — and the trade-off each one makes. ## Product - [Use cases](https://beardrive.ai/use-cases/): the jobs teams hire BearDrive for. - [Compare](https://beardrive.ai/compare/): how it differs from Drive, Dropbox and MCP memory servers. - [Pricing](https://beardrive.ai/pricing/): plans and what counts as a seat. - [Source](https://github.com/runbear-io/beardrive): the CLI, the sync engine and the hub.