Open-source NotebookLM alternative for churned Google users
Build or position a lean open-source-based alternative to NotebookLM aimed at the churn of users frustrated by Google deprecating or hobbling beloved products. Target source-grounded research/Q&A over large document sets (up to 200 sources), paired with exportable study/report assets (mind maps, slide decks, short videos) for students, researchers, and content creators who want NotebookLM-like features without depending on Google's roadmap.
What to build
An open-source-based web app that replicates NotebookLM's core workflow: upload up to ~200 source documents, get grounded Q&A with citations, and export the research as mind maps, slide decks, and short explainer videos — aimed at students, researchers, and content creators who build research workflows around a tool like this.
Google has a track record of degrading or killing beloved products, and someone already shipped a public 'fix' for NotebookLM — a signal that a churn-ready user base exists for a source-grounded research tool that doesn't depend on Google's roadmap.
Demand
Students, researchers, and content creators who rely on NotebookLM for large-document Q&A and study-asset generation want a version they control, especially once they've been burned by Google changing or removing features they depended on.
- Reddit r/SideProjectAnecdote
Post titled 'Google cooked NotebookLM, so I fixed it' framing Google as notorious for abandoning/degrading working products, prompting the author to build a replacement.
- Signal title/author claimOpinion
Author states they built a fix/alternative in direct response to perceived Google mismanagement or feature degradation of NotebookLM.
- Opportunity brief (internal signal metadata)Analysis
Describes the target feature set: source-grounded research/Q&A over up to 200 sources plus exportable mind maps, slide decks, and short videos, aimed at students, researchers, and content creators frustrated with Google's product changes.
Stack
- Ollama or vLLM for open-weight LLM inference (with OpenAI/Anthropic API fallback)
- Qdrant or Supabase pgvector for retrieval
- LlamaIndex or LangChain for RAG orchestration
- Unstructured.io or PyMuPDF for multi-format document ingestion
- Remotion + TTS API (ElevenLabs/OpenAI TTS) for slide/video export
- Vercel + Supabase for hosting and auth
Solo + AI difficulty
Source-grounded Q&A over many documents with citations is straightforward with existing RAG tooling and shippable in a few weeks; the hard, slow part is building a reliable mind-map/slide/video export pipeline that matches NotebookLM's output quality. A text-Q&A-plus-mind-map MVP is realistic in 3-4 weeks solo with AI coding help; full feature parity including video generation is more like 2-3 months.
- Entry threshold
- Core RAG-over-documents stack (embeddings, vector search, LLM Q&A) is buildable solo in weeks using existing APIs; the harder, higher-effort layer is the video/voice generation pipeline (ElevenLabs integration, motion graphics rendering), which this poster reused from a prior 10K-user product rather than building from scratch.
- Window
- 6-9 months
Where to find first users
- r/SideProject (where the original signal was posted)
- Product Hunt launch
- r/LocalLLaMA and open-source AI communities
- Show HN on Hacker News
Competitors
Counter-signals & risks
NotebookLM benefits from deep integration with Google's Gemini models, Drive, and Workspace ecosystem, which an open-source alternative may struggle to replicate at comparable quality or cost.
User frustration expressed in a single blog/signal may not represent broad market churn; Google could reverse or improve the criticized changes before an alternative gains traction.
Building and maintaining a multi-format export pipeline (mind maps, slide decks, video generation) alongside large-context document Q&A is resource-intensive and may be difficult to sustain as a lean or open-source project against a well-funded incumbent.
Original title: Google cooked NotebookLM, so I fixed it
Related signals
- Productivity#12
Exercise-gated app blocker for phone addiction
Build a mobile app blocker that requires verified physical proof-of-work (squats, pushups, walking steps counted via camera pose detection or sensors) before unlocking distracting apps, sold as a one-time purchase or small subscription to people who have already failed with simple screen-time limiters. Target productivity and digital-wellbeing communities, habit-tracking forums, and self-improvement audiences on Reddit and TikTok who complain that existing blockers are too easy to bypass.
Demand4/10est.Buildability7/10est.Competition5/10est.via Reddit44 competitors - Productivity#1
Cheap external-partner portal layer for Airtable
Build a lightweight external-collaborator layer for Airtable (and similar tools like Smartsheet, monday.com): a portal that syncs with linked bases via API, enforces row-level permissions so outside partners only see their own records, supports SSO for core staff, and charges per light-user seat at a fraction of Airtable's full seat price. Sell to ops and RevOps teams at mid-size companies who have a small internal builder team plus a much larger pool of external viewers/updaters.
Demand6/10est.Buildability7/10est.Competition5/10est.via Reddit44 competitors - Productivity#3
Lightweight internal app builder to replace messy Smartsheet workflows
Build a lightweight internal-app builder focused on one workflow archetype: request form plus reviewer approval queue plus role-based visibility (requesters see only their own rows), with Smartsheet-style reporting/dashboards built in. Target ops and IT teams who have outgrown a spreadsheet-based workflow but don't want a full no-code platform like Retool or a heavyweight app like ServiceNow. Package it as a template (equipment/IT request tracker) so teams can deploy in under a day.
Demand5/10est.Buildability7/10est.Competition5/10est.via Reddit44 competitors