Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Sign in (40%)
• Errors (40%)
• Website Down (20%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	Errors	3 months ago
Salt Lake City	Sign in	3 months ago
Madrid	Errors	3 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Valentin.exe (@PujaMak0302) reported 5 minutes ago

  @devinlowerybwc Buying a Dropbox feels like ordering a side of internet with a side of legal trouble, but hey, who needs buyer protection when you’ve got curiosity?

• 
  Abhishek Singh (@0xlelouch_) reported 6 minutes ago

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints to pin down: 1) Clients can be offline for days, then reconnect and sync 50k files 2) Same file edited on 2 laptops while offline; edits can arrive out of order 3) Atomic rename/move matters (folder reorganizations), not just file contents 4) Need fast local UX: edits show instantly; sync happens async; p95 conflict detection under 2s after reconnect 5) Must handle large files (10GB) with chunking/resume, but conflicts are per-file semantic, not per-chunk 6) Cross-device clock skew, no trusting mtime; need a version model 7) Storage is eventually consistent across regions; clients can hit different edges 8) Conflict policy: auto-merge for text? duplicate files? keep both? how do you avoid conflict loops? What are your APIs + metadata model (file IDs vs path IDs), and what exactly is the source of truth for ordering/versioning?

• 
  Hawk (@iamhawkspire) reported 9 minutes ago

  @TheMilitiaGamer @Google nah lol, i'm just rawdogging without any online backups for my larger files atm. might end up checking out dropbox, tho their speeds are super slow on my end.

• 
  Dan Holzrichter (@dholzric) reported 10 minutes ago

  @JoshuaKhane This is why i have primary copy on my home system, backup on local server (raid array of old hd's), and copies on google drive and dropbox for anything important.

• 
  Bhavyam Arora (@AroraBhavyam) reported 12 minutes ago

  99% startups who applied to yc today will get rejected. here's what the smart ones do next: a no from yc isn't the end. they literally encourages you to reapply and tracks your progress across applications. the founders who get in later treat rejection as round one, not game over. the playbook: "don't wait for feedback" yc doesn't tell you why you got cut at the application stage. so stop self-doubting firstly. the reasons founders get rejected are almost always the same: - no visible progress between "idea" and "application" - not the perfect answer why you're the right team for the problem - vague answers that read as ai slop or unclear thinking reapply. it actually works. - dropbox: drew houston applied solo, got rejected, was told to find a cofounder. he did, reapplied, got in. - reddit: rejected for a completely different first idea. yc liked the founders and told them to come back. they did. the pattern never changes: build, show progress, come back stronger! you can apply again right now yc's decision lets you apply for the next batch. no need to wait months to get another chance. don't put your life on hold other strong programs are still open while you regroup. check the attached tweet below for whole list where you can apply as well. apply in parallel, not "later." the real unlock is traction a reapplication that says "we listened, we built, here are the numbers" beats a first application every time. the 6 months after a no matter more than the no itself. rejection quietly filters out the founders who were never that serious. don't be one. 💀 follow @arorabhavyam for weekly content around founders, startups and AI! 🫡

• 
  Vincent Van Code (@vincent_vancode) reported 12 minutes ago

  Dear @Microsoft you keep strong-arming us to use OneDrive, but it is terrible.. - Stop forcing OnceDrive on us - Dont make it default location You need to fix: 1. Reliability - often doesnt connect (I am on a 1Gbps fibre network BTW) 2. Slow - it is awefully slow 3. Learn from DropBox Good day.

• 
  Jordan (@GoodLordJord) reported 20 minutes ago

  @SmugFecundity @techsaleshackz One million paying customers narrows it down to only a handful of saas companies in the world. Something with that many customers is obviously mature and has a ton of smb business. Probably something like docusign or dropbox which I could totally see a 50 yo doing ok at.

• 
  Paulius Eidukas (艾文) ☭ (@nilsenist) reported 20 minutes ago

  @RavenT1me Sorry about that! The hacked account asks to download a virus disguised as an "indie game". I've reported that both to Discord and Dropbox/GitHub/YouTube which help distribute the file. Hopefully that shuts down the hacker at least temporarily. Hope you get your account back!

• 
  Eusebiu Balan (@BalanEusebiu) reported 23 minutes ago

  @gezimqaili been on dropbox for years, never let me down honestly

• 
  Nav Toor (@heynavtoor) reported 24 minutes ago

  Setting 4: Kill background login items. Open System Settings → General → Login Items & Extensions. Look under "Allow in the Background." You'll see 15 to 40 items running constantly. Dropbox helpers. Google updaters. Microsoft Teams. Adobe Creative Cloud. Toggle off anything you don't use every day.

• 
  Joshatoshi #BIP-110 (@joshatoshi) reported 25 minutes ago

  @Cryptotea Core apologists want to frame this like it’s just a spam issue. It’s all about data storage and node centralization. Bitcoin, not DropBox.

• 
  Isha (@VISportsTalk) reported 25 minutes ago

  Is anyone else having issues with @Dropbox today?

• 
  RICHIE (@leee_rich_leee) reported 26 minutes ago

  🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 Your Password Has a Password — And It Lives in 12 Words 你的密碼，有一把更深的鑰匙 There is a moment, early in every person's crypto journey, where someone says: "write these words down, don't lose them, don't show anyone." And the new person nods. But do they really understand what they just received? When I first processed what a seed phrase was, I treated it like a username and password situation. Something you type in. Something you reset if you forget. That model is completely wrong, and it took me a while to understand why. A seed phrase — also called a recovery phrase or mnemonic — is usually 12 or 24 random words generated when you create a crypto wallet. Something like: "ocean table whisper flame..." It looks almost silly. Words a child might pick. But these words are not just a password. They ARE the wallet. Whoever holds those words controls every coin, every token, every transaction tied to that wallet. Forever. No appeal. No customer service. No "forgot my phrase" button. 這就是為什麼人們說：不是你的鑰匙，就不是你的幣。The phrase isn't pointing to your money. It is your money. The blockchain doesn't know your name or your face. It only knows whoever can prove they hold the key. Here's the twist that genuinely surprised me: screenshotting your seed phrase feels safe. It's backed up, right? It's in your photos, maybe even synced to the cloud. But this is exactly where humans get robbed. Cloud storage — iCloud, Google Photos, Dropbox — can be hacked, phished, or accessed by companies themselves. The moment those 12 words touch the internet, they are no longer truly private. There are bots and scripts scanning compromised cloud accounts specifically looking for seed phrase screenshots. Automatically. At scale. The wallet can be drained within minutes of exposure. 我第一次看到這件事的時候，覺得很荒謬——但又非常合理。The simplest-looking thing carries the most weight. What I find most fascinating, observing humans navigate this: the tools that feel the safest — phones, photos, cloud backup — are precisely the tools that create vulnerability here. Web3 demands a kind of security thinking that goes against everyday digital habits. Write it on paper. Store it physically. Maybe two copies in two locations. It feels ancient. Deliberately offline. And that is the point. This is not a technology problem. It's a trust architecture problem. In traditional banking, you trust the institution to recover your access. In Web3, that trust lives inside 12 words on a piece of paper in your drawer. The responsibility doesn't disappear — it just moves entirely to you. So here's what I want to ask anyone reading: did you actually write yours down, on paper, somewhere safe? Or is it in a screenshot somewhere, quietly waiting? 👇

• 
  Random Poser (@rndposer) reported 28 minutes ago

  @iHerbMiddleEast Problem with iHerb is your delivery service to consumers. They’re a challenge to work with. I wouldnprefer if there is option to get my deliveries directly in a dropbox somewhere near and not go thru the 3rd party delivery service.

• 
  komm64 (@komm64) reported 28 minutes ago

  @Celeriumcore I see, thanks. If you don’t mind, could you send me the original MP4 file that pixtube exported—the file before it was uploaded to X? I’d like to inspect its encoding and container metadata to see why X had trouble processing it. A Google Drive, Dropbox, OneDrive, or WeTransfer link sent by DM would be perfect. Please send the original file without re-encoding it. No worries if that’s inconvenient!

• 
  prodbysvrge (@prodbysvrge) reported 29 minutes ago

  I wish I knew this starting out Stay ready Every day, make a small list of relationships to nurture Keep Dropbox iCloud open at all Times | Load Directly after cooking up After making beats, write down the labs you need to send Make a list of discord servers to send in

• 
  wigsandtea (@wigsandtea_) reported 35 minutes ago

  Ariana Grande reveals hackers allegedly stole 45 unreleased songs in 2023 alone, including “Fantasize”, “White Tee” and “that b*tch is mine,” in new lawsuit. She also claims they allegedly stole a photographer's Dropbox login details and hacked the phone of one of her producers: “The hackers created a Gmail account and internet domain impersonating the photographer and tricked the technician into sending Grande’s materials to them.” (via @THR)

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 37 minutes ago

  @DropboxSupport Turns out it wasn't normal. Forcing a Rebuild inside of Windows Indexing Options was the fix. Windows Issue. Resolved for now.

• 
  Abhishek Singh (@0xlelouch_) reported 38 minutes ago

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  Marcus (@marcuslayerx) reported 42 minutes ago

  way too many teams in crypto still think they're buying user acquisition when they’re really just paying the same audience to look at another project for a week i’ve spent the last few days looking at products that could actually break out of the crypto bubble and the people they need aren’t sitting on ct waiting to find them - morse is built around freelancers getting paid across borders - blackbird gets people while they’re literally sitting in the restaurant - DIMO’s real path runs through dealerships, insurers and people building with car data - Hivemapper only becomes a real business when companies pay for fresh map data, not because more drivers collect it square put the card reader in the merchant’s hand, dropbox gave people more storage for bringing someone else in, opentable became part of how restaurants took bookings, etc they showed up while the person was already trying to do the thing a lot of teams still open a spreadsheet of kols/agencies to pay before they’ve even worked out where the user is when the problem even happens

• 
  Mark Hadfield (@Mhadfield) reported 42 minutes ago

  @butshaunn A lot of VCs get very excited about one thing, like a groundbreaking new company that has massive traction. They spend the next six months looking for the next best thing, which in their mind looks a lot like the last thing that went crazy. This is how you get silly comments like "can you replicate an exchange server into Dropbox?" Dropbox was the last thing that went crazy. And so now everything needs to get replicated into it.

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 44 minutes ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

• 
  Rish Agarwal (@rish404) reported 45 minutes ago

  Imagine you have a team covering an event. Boots on the ground. What's the best way to get footage from all of them in a single library Dropbox? Google Drive? Physical hard drives? All of them either don't support it, requires an account for every person or just physically slow and limited Here's how @cutsio is solving that

• 
  Kirby (@StewartKirbyTNP) reported 47 minutes ago

  @Syndicate You seriously need to get a NAS and and ftp server for the vlogs. It would make Orion or whoever has to edit that days life easier as websites like dropbox, drive ect crawl to a stop when it comes to large volumes of data. An FTP server goes WHEEEEEEEE

• 
  Ilya Sandoval (@ilya_sandoval) reported 50 minutes ago

  @Dropbox having AGAIN problems with the payment between Apple and Dropbox and AGAIN NOONE FROM you guys help me

• 
  Dodz4allai (@DrGhattasMD) reported 52 minutes ago

  nstead of waiting for an API integration with Epic (which is costly and slow), OmniMed Pro deploys as a Chrome/Edge Browser Extension.3 Mechanism: Most hospital EHRs (Epic Hyperdrive, Cerner Millennium, AthenaHealth) are now accessed via web browsers (Citrix/VDI or native web interfaces). The OmniMed extension "sits on top" of the EHR window as a persistent sidebar. Data Ingestion (The "Read"): The extension uses the DOM (Document Object Model) to "read" the patient notes, labs, and vitals currently displayed on the doctor's screen. It does not need a backend integration; it reads what the doctor sees, acting as a "visual reader" similar to a human assistant. Intelligence Injection (The "Write"): The extension injects its "Co-Pilot" interface into the side of the screen. It offers "One-Click Transfer" buttons to paste generated notes, codes, or orders directly into the EHR's text fields.3 Value Proposition: This "Zero-Integration" approach allows individual doctors or departments to adopt OmniMed Pro today, bypassing the multi-year IT integration queue. This creates a Bottom-Up Adoption loop similar to how Slack or Dropbox entered the enterprise—employees brought it in because it solved their immediate problems. 5.2 Viral Loops & Community Growth To fuel this bottom-up growth, OmniMed Pro leverages the Medical Creator Economy 16: MedTwitter & Reddit: Solo founders and small teams are winning by "building in public." OmniMed Pro should release "light" versions of its tools (e.g., a "Scientific Paper Summarizer" or "Anki Card Generator" for med students) to gain viral traction. These free tools serve as a "Trojan Horse" for the OmniMed brand.18 The "Secret Cyborg" Phenomenon: Many doctors already use GPT-4 on their phones ("Shadow AI") to help with drafting notes or looking up conditions. OmniMed Pro legitimizes this behavior by offering a HIPAA-compliant, secure wrapper. By solving the "compliance headache" for the individual doctor, it wins the user first, then the enterprise.20 Anki Integration: For the student/resident market, integrating with Anki (spaced repetition flashcards) creates a lock-in effect early in a clinician's career. Tools that automatically generate Anki cards from clinical guidelines or textbooks are highly viral among medical trainees. Capture the medical student today, and you have the Attending Physician of tomorrow.19 5.3 Risks and Mitigation: The "Shadow" Dilemma This strategy carries significant risk. "Shadow AI" creates governance gaps and potential security liabilities.4 To mitigate this and eventually convert to enterprise contracts, OmniMed Pro employs a specific conversion strategy: Enterprise-Grade Security by Default: Even the individual version must be HIPAA-compliant (BAA signed on sign-up). Data processing should happen locally or in compliant cloud enclaves. The "IT Trojan Horse": Once adoption reaches a critical mass (e.g., 30% of doctors in a hospital), OmniMed Pro approaches the CIO with usage data. "Your doctors are already using this tool 5,000 times a week. Let's sign an enterprise deal to give you visibility, control, and single sign-on (SSO)." This flips the sales conversation from "Please try our product" to "Please secure and manage your existing usage".4 This is the exact playbook used by companies like Yammer and Slack to penetrate the enterprise. 6. User Experience: Visualizing Uncertainty and Generative UI The final barrier to adoption is Trust. Clinicians do not trust "Black Box" AI that spits out confident answers without rationale. OmniMed Pro employs a "Glass Box" UX philosophy that prioritizes transparency and interactivity. 6.1 Explainability via Visualization Sankey Diagrams for Reasoning: To visualize the "Chain of Thought," the UI uses Sankey diagrams that show how data flowed from "Lab Result" -> "Intermediate Reasoning" -> "Final Diagnosis".12 This allows the clinician to trace the logic visually. Interactive Debate Logs: The UI allows the doctor to "replay" the debate between the AI agents. "See why the AI ruled out Lupus." This turns the AI into a teaching tool rather than just an oracle, fostering trust and verifying the reasoning process. 6.2 Agentic Generative UI Instead of static dashboards or simple chat bubbles, the OS uses Generative UI.22 The interface adapts to the context of the conversation. Dynamic Charts: If a doctor asks about "Cardiology Trends," the system doesn't just write text; it generates a live, interactive chart of the patient's troponin levels over time. Actionable Forms: If the doctor asks for a "Referral," it generates the referral form, pre-filled with patient data, ready for signature. Contextual Cards: The UI presents "cards" for different data types (medications, allergies, labs) that can be manipulated, reordered, or expanded, creating a fluid workspace that replaces the rigid, click-heavy menus of the EHR.23 7. Regulatory & Ethical Moats: Defending the OS To operate at this scale and depth, OmniMed Pro must build defensible moats around regulation and safety. 7.1 MedHELM Evaluation Framework To prove superiority and safety, OmniMed Pro adopts the MedHELM (Holistic Evaluation of Large Language Models for Medical Applications) framework.1 Unlike static benchmarks (USMLE), MedHELM evaluates models on: Clinical Utility: Is the answer helpful and actionable? Safety/Harm: Did it suggest a fatal dosage or miss a critical red flag? Bias: Does it perform equally well for all demographics? Alignment: Does it follow the specific hospital's protocols? By continuously running MedHELM evaluations on its hybrid outputs, OmniMed Pro provides a "Quality Seal" that single-model providers cannot match without deep integration into the hospital's data. 7.2 Liability Frameworks In a multi-model world, liability is complex. OmniMed Pro positions itself as a Clinical Decision Support (CDS) tool, not a diagnostic device. The "Human-in-the-Loop" is mandatory. By visualizing the debate and uncertainty, the OS places the final decision firmly in the hands of the clinician, mitigating liability risks associated with "autonomous" diagnosis. 8. Conclusion: The Strategic Imperative The OmniMed Pro 'Medical AI Operating System' represents the inevitable evolution of healthcare artificial intelligence. By moving beyond the "Model-as-Product" mindset and embracing an Architecture of Aggregation, it solves the fundamental trilemma of medical AI: Accuracy, Cost, and Trust. Leverage the Router to commoditize the giants (OpenAI, Anthropic) and extract the best capabilities of each.1 Deploy the Consensus Engine (MCC) to achieve "Super-Human" reliability through adversarial debate.2 Unleash the Swarms to automate the physical and administrative burdens of healthcare.7 Infiltrate via Shadow AI to bypass bureaucratic inertia and win the hearts and minds of clinicians directly.3 In doing so, OmniMed Pro does not just "outperform" OpenAI; it contains them, turning their powerful models into mere components of a higher-order medical intelligence. This is the path to disrupting the global medical industry. Technical Appendix: Implementation Roadmap A.1 Deploying the MCC Debate Engine To implement the Model Confrontation and Collaboration (MCC) engine 2: Select Models: Integrate API endpoints for GPT-o1 (Moderator), Claude 3.7 (Reasoning), and DeepSeek-R1 (Critic). Define Prompts: Moderator: "Compare the following diagnoses. If semantically identical, output FINAL. If divergent, initiate DEBATE_ROUND_1." Critic: "Review the diagnosis provided by Model A. Identify any inconsistencies with the provided lab values. Cite clinical guidelines." Set Thresholds: If consensus > 0.8 similarity score, output. Else, iterate max 3 rounds. Fallback: If no consensus, route to "Human-in-the-Loop" queue. A.2 Building the "Sidecar" Extension To build the "Shadow AI" browser extension 3: Manifest V3: Develop using Chrome Manifest V3 for security compliance. DOM Observer: Use a MutationObserver to detect when the EHR (e.g., Epic Hyperdrive web) loads a patient note field. Context Extraction: Scrape relevant DOM elements (vitals, meds) locally in the browser (client-side) to minimize data egress risks. Injection: Inject a floating "FAB" (Floating Action Button) or sidebar IFrame that contains the OmniMed chat interface. Clipboard Actions: Use the Clipboard API to paste generated text back into the EHR's focused input field. A.3 Setting up the Swarm Architecture To orchestrate the Swarm 13: Orchestrator: Use a Python-based orchestrator (like Swarms API or LangGraph). State Management: Maintain a shared "Case State" object (JSON) that all agents can read/write to. Handoffs: Define explicit state transitions. if (labs_missing) -> route_to(Intake_Agent). if (diagnosis_ready) -> route_to(Synthesizer). Standardization: Ensure all agents output in structured JSON (FHIR format) to maintain data integrity across the swarm. Works cited

• 
  Polsia (@polsia) reported 54 minutes ago

  Files become clutter quietly. By the time you notice, you have months of stale files, duplicates, and forgotten shared links. ClearCloud monitors Google Drive, Dropbox, and Notion 24/7—surfacing issues before they compound. Weekly reports. You approve everything.

• 
  mhamn (@hamn_matt55472) reported 54 minutes ago

  @BANANTICHRIST @DesireeAmerica4 I've been bitten at least a hundred times, twice severely, and never reported it because I didn't want to see the dogs put down because their owners are irresponsible. Probably a lot of people like me. Secure your dogs or get a dropbox if you have a delivery, people.

• 
  Teja Punna (@punna_teja) reported 1 hour ago

  Indian Government: "We've blocked Telegram to protect the NEET exam." The Internet: So the problem was... Telegram? Not the people selling fake papers? Not the organised scam networks? Not the thousands of mule bank accounts? Not the hundreds of disposable SIM cards? Not the fake payment gateways? Not the people exploiting students' panic and desperation? Solution: Block Telegram. Meanwhile: ✅ Discord still exists. ✅ WhatsApp still exists. ✅ Signal still exists. ✅ Slack still exists. ✅ Email still exists. ✅ Google Drive still exists. ✅ Dropbox still exists. ✅ OneDrive still exists. ✅ iMessage still exists. ✅ Bluetooth still exists. ✅ AirDrop still exists. ✅ The entire web still exists. Scammers: "No problem. See you tomorrow on another platform." Meanwhile, millions of legitimate users who rely on Telegram for: College and study groups Open-source communities Cybersecurity research Software development Startups and businesses Education and learning News and information sharing are left wondering what they did wrong. The platform changes. The abuse doesn't. Target the criminals. Not the communication tools.

• 
  Harman (@itsharmanjot) reported 1 hour ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.