diff --git a/.claude/agents/beardrive-gtm.md b/.claude/agents/beardrive-gtm.md index 7531365..9a9b545 100644 --- a/.claude/agents/beardrive-gtm.md +++ b/.claude/agents/beardrive-gtm.md @@ -60,7 +60,8 @@ writers whose activity is attributed and measured. 1. `README.md` — the repo front door: first-90-seconds test (what is it, who is it for, why now, time-to-first-wow), positioning line, badges, quickstart friction, screenshot/demo presence. -2. `website/` — the landing page: headline/subhead, category claim, CTA +2. `cloud/web/landing/` — the landing page (cloud-only; served by the hub at + its root for signed-out visitors): headline/subhead, category claim, CTA hierarchy (self-host vs cloud), social proof, pricing posture. 3. `plugin/` — the Claude Code plugin + skill: as a distribution channel (marketplace install → team onboarding loop → does a teammate's first diff --git a/docs/gtm-handoff.md b/docs/gtm-handoff.md index 47263aa..7ec3259 100644 --- a/docs/gtm-handoff.md +++ b/docs/gtm-handoff.md @@ -51,9 +51,9 @@ Draft copy is ready to paste; adjust voice as you like. - T1: `bdrive share wiki/findings.md` → open the public URL. Tools: `vhs` (charmbracelet) or QuickTime + gifski. Put the result at `docs/assets/demo.gif` and add it above the fold in README. -9. **Verify beardrive.ai serves the updated landing page** (the repo's - `website/` — including the new `assets/insights.png`) after the next - deploy. +9. **Verify beardrive.ai serves the updated landing page** (now + `cloud/web/landing/`, served by the hub itself at `/` for signed-out + visitors) after the next deploy. ## P2 — when you're ready to be seen (launch window) diff --git a/docs/gtm-quality-prd.md b/docs/gtm-quality-prd.md index 73fc53c..97e303f 100644 --- a/docs/gtm-quality-prd.md +++ b/docs/gtm-quality-prd.md @@ -10,7 +10,8 @@ agent never scores its own work. Everything GTM-relevant that lives in this repo: - `README.md` (positioning, quickstart, time-to-wow, demo assets plan) -- `website/` (headline, category claim, CTAs, pricing posture copy) +- `cloud/web/landing/` (headline, category claim, CTAs, pricing posture copy — + cloud-only, served by the hub at its root for signed-out visitors) - `docs/` (self-host guide, quickstart, a launch plan, a metrics plan) - Community surface: `CONTRIBUTING.md`, `.github/` issue/PR templates, `CHANGELOG.md` or release-notes convention, a public `ROADMAP.md` diff --git a/website/assets/browse.png b/website/assets/browse.png deleted file mode 100644 index a59a0f5..0000000 Binary files a/website/assets/browse.png and /dev/null differ diff --git a/website/assets/insights.png b/website/assets/insights.png deleted file mode 100644 index 05b4fab..0000000 Binary files a/website/assets/insights.png and /dev/null differ diff --git a/website/assets/share.png b/website/assets/share.png deleted file mode 100644 index 8efc676..0000000 Binary files a/website/assets/share.png and /dev/null differ diff --git a/website/index.html b/website/index.html deleted file mode 100644 index 2de06af..0000000 --- a/website/index.html +++ /dev/null @@ -1,641 +0,0 @@ - - - - - -BearDrive — Google Drive for AI agents - - - - - - - - - - - - - - - - -
-
-
Open source AGPL-3.0 · single Go binary · on Homebrew
-

Google Drive for AI agents.Your agent knows what their agent knows.

-

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.

-
- Start free → - Self-host it - -
-
-
-
-
~/acme-wiki
- 

-    

-  

-  

-    
Your hub stores on the object storage you already have

-    

-      Amazon S3Google Cloud StorageCloudflare R2
-      MinIOany folder
-    

-  

-

-
-

-  

-    
HOW IT WORKS

-    
One command per project. That's the integration.

-    
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.

-    

-      
01
-        
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.

-      

-      
02
-        
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.

-      

-      
03
-        
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.

-        A shared markdown runbook rendered as a public page
-      

-      

-        
your folder  ←scan/materialize→  local volume  ←push/pull→  a BearDrive hub (on S3 / GCS / R2 / a folder)
-real files                per-device journals,      devices converge through the hub's dumb storage:
-every tool works          content-addressed blobs    append-only, no locks, offline-safe

-      

-      

-        The hub web UI browsing a project — per-file agent read counts, heat dots, and the folder's change feed
-      

-    

-  

-

-
-

-  

-    
SHARE WITHOUT A SHARE STEP

-    
The link is born with the file.

-    
The moment your agent writes a file, the path in its reply is
-    already a clickable, members-only hub link. You didn't run a command, you didn't
-    copy a path — any teammate who's signed in opens it in one click, rendered and at
-    the latest version. It's gated to your project, so it's safe to paste in any
-    internal channel.

-    

-      

-        ●
-        Deal page written to shared/wiki/deals/motive.md 🔗
-      

-      
↑ your agent's own reply — the 🔗 is a live hub link it added automatically. No bdrive share, no copy-paste, nobody asking you to resend it.

-    

-  

-

-
-

-  

-    
WHY BEARDRIVE

-    
Two superpowers, one folder.

-    

-      
🧠

-        
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.

-      

-    

-    
BearDrive Insights — every file plotted by agent and human reads versus staleness

-  

-

-
-

-  

-    
FEATURES

-    
Built for teams where half the "members" are agents.

-    
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

-      
Your agents become fluent in it.

-      
    
-        
  • /beardrive:install sets a whole team project up
-        conversationally: CLI, sign-in, project, and sync hooks — one plugin that
-        works the same in Claude Code and Claude Cowork.
    • 
-        
  • Hooks keep everything fresh — a pull when you submit a prompt
-        (Claude reads the team's latest files) and an async push after every edit
-        (artifacts hit the server seconds after Claude writes them). Works for
-        every teammate, plugin or not.
    • 
-        
  • Every file it writes comes with a link — the turn-start hook
-        teaches Claude to drop a gated hub link beside any synced path it mentions,
-        so "share this report with the team" just works.
    • 
-      

-      Explore the plugin →
-    

-    

-      
You, to your Claude

-        
Write up the Q3 findings and share them with the team.

-      

-      
Your Claude

-        
Done — I saved the report to 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):


-        https://acme-hub.example/p-1a2b3c4d/wiki/q3-findings.md


-        Say the word if you need a public link for someone outside the team.

-      

-      
Your teammate, to their Claude

-        
What did we learn from the Q3 numbers?

-      

-      
Their Claude

-        
Per wiki/q3-findings.md — synced to this machine
-        four minutes ago — churn concentrated in self-serve accounts, and…

-      

-    

-  

-

-
-

-  

-    
GET BEARDRIVE

-    
Self-host everything. Or let us run it.

-    
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.

-    

-      

-        
Open source

-        
AGPL-3.0 · free forever · your infrastructure

-        
    
-          
  • The complete server — teams included
    • 
-          
  • One binary: bdrive web is the viewer, uploads, and sync hub
    • 
-          
  • Any storage: S3 / GCS / R2 / MinIO / a folder
    • 
-          
  • File-backed registries — no database to run
    • 
-        

-        

-          View on GitHub
-          Self-hosting guide
-        

-      

-      

-        
BearDrive Cloud

-        
app.beardrive.ai · managed hosting · live now

-        
    
-          
  • Zero setup — sign up, bdrive login, and go
    • 
-          
  • Managed storage, backups, and support handled for you
    • 
-          
  • Funds the open source project
    • 
-        

-        

-          Start free →
-          Log in
-        

-      

-    

-  

-

-
-

-  

-    
Share files. Share context.
Cloud or self-hosted.

-    
Sign 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.

-    

-      Start free →
-      Self-host on GitHub
-      
-    

-  

-

-
-
-
-
-
-
diff --git a/website/themes-preview.html b/website/themes-preview.html
deleted file mode 100644
index 5418f45..0000000
--- a/website/themes-preview.html
+++ /dev/null
@@ -1,159 +0,0 @@
-
-
-
-
-
-BearDrive — accent theme candidates
-
-
-
-
BearDrive accent themes

-
Same layout, one variable changed. Scroll — the verdict under each card is the honest trade-off.

-

-
-  

-    

-    
🍯 Honeywarm amber#f5a623

-    

-      
Open source AGPL-3.0 · on Homebrew

-      
A shared drive for your AI agents.Synced in seconds. Tracked forever.

-      
Real files. Self-hostable in one binary.

-      

-      
$ bdrive share wiki/q3-report.html
-https://beardrive.ai/s/1aad3327…
-  anyone can open it — no account needed

-    

-    
The bear-brand pick. Honey is literally on-brand, warm and
-    optimistic, and almost untouched in dev tools — instantly distinguishable from
-    Supabase/Linear/Vercel. Risk: amber reads "warning" in some UI contexts.

-  

-
-  

-    

-    
🐟 Salmonwarm coral#fa8072

-    

-      
Open source AGPL-3.0 · on Homebrew

-      
A shared drive for your AI agents.Synced in seconds. Tracked forever.

-      
Real files. Self-hostable in one binary.

-      

-      
$ bdrive share wiki/q3-report.html
-https://beardrive.ai/s/1aad3327…
-  anyone can open it — no account needed

-    

-    
The playful pick. Bears eat salmon — a wink insiders get.
-    Friendly and modern (Claude/Anthropic-adjacent warmth). Risk: coral can read
-    consumer-y rather than infrastructure-y.

-  

-
-  

-    

-    
🧊 Glacierpolar ice blue#7dd3fc

-    

-      
Open source AGPL-3.0 · on Homebrew

-      
A shared drive for your AI agents.Synced in seconds. Tracked forever.

-      
Real files. Self-hostable in one binary.

-      

-      
$ bdrive share wiki/q3-report.html
-https://beardrive.ai/s/1aad3327…
-  anyone can open it — no account needed

-    

-    
The calm-infrastructure pick. Polar-bear cool, Tailscale-like
-    trustworthiness, great contrast on black. Risk: blue is the most crowded color
-    in dev tools (GitHub, Docker, Stripe) — safe but forgettable.

-  

-
-  

-    

-    
🔮 Violetthe product's own accent#a882ff

-    

-      
Open source AGPL-3.0 · on Homebrew

-      
A shared drive for your AI agents.Synced in seconds. Tracked forever.

-      
Real files. Self-hostable in one binary.

-      

-      
$ bdrive share wiki/q3-report.html
-https://beardrive.ai/s/1aad3327…
-  anyone can open it — no account needed

-    

-    
The consistency pick. Your web viewer already uses this violet —
-    landing page, product, and share pages would feel like one thing. Risk: violet-on-dark
-    is the Linear/Obsidian look, i.e. the "too general" you flagged.

-  

-
-  

-    

-    
🌲 CurrentSupabase green (as-is)#3ecf8e

-    

-      
Open source AGPL-3.0 · on Homebrew

-      
A shared drive for your AI agents.Synced in seconds. Tracked forever.

-      
Real files. Self-hostable in one binary.

-      

-      
$ bdrive share wiki/q3-report.html
-https://beardrive.ai/s/1aad3327…
-  anyone can open it — no account needed

-    

-    
The status quo. Proven legibility and OSS-community coding
-    ("green = open source" thanks to Supabase). Risk: it's their green — you'd
-    forever look like a Supabase product.

-  

-
-

-
-