Open-source NotebookLM alternative: connect your sources, ask grounded questions, generate cited outputs, and extend deep knowledge work with Virtual FS and extensible Skills.
Self-hosted and multi-model, with files, web pages, notes, YouTube, and SaaS connectors so teams stay in control of their data, models, and knowledge work.
SourceWeft is an open-source NotebookLM alternative for deep knowledge work. Connect PDFs, web pages, notes, YouTube, Notion, Google Drive, Gmail, Slack, and more into one organized source space, then ask questions with answers grounded in verifiable citations.
Beyond Q&A, SourceWeft helps you create study guides, FAQs, timelines, research briefings, drafts, audio overviews, image artifacts, and other knowledge outputs. Virtual FS, built-in Skills, custom Skills, web tools, and working files give agents the context and tools to read, search, create, organize, and refine work across your sources.
Research briefing. Papers, web pages, and notes -> cited research briefings with key claims, evidence, and open questions.
Learning guide. Course material, videos, and PDFs -> study guides, FAQs, and quiz drafts.
Content workspace. Product docs, web pages, and team notes -> blog drafts, launch outlines, and image Artifacts.
Team knowledge. Drive, Gmail, Slack, Notion, and other connected sources -> traceable answers about decisions, projects, and shared context.
Connect all your sources. Work across files, URLs, notes, YouTube, source trees, and SaaS connectors.
Ground every answer. Ask across selected sources and get cited, verifiable responses.
Give agents a real workspace. Virtual FS organizes sources, working files, Artifacts, and Skill instructions into navigable context.
Extend agents with Skills. Built-in and custom Skills add reusable domain methods, slash commands, tool defaults, and task-specific guidance.
Self-host SourceWeft, use your own models for chat, embeddings, rerank, image, and audio, and share workspaces with your team.
-
Create a workspace. Start with a personal workspace, or invite teammates into a shared workspace with roles and shared billing.
-
Add your sources. Upload files, paste URLs, write notes, add YouTube links, or connect tools like Notion, Google Drive, Gmail, and Slack.
-
Let SourceWeft index them. Sources are parsed, chunked, embedded, and made searchable with hybrid retrieval.
-
Ask, create, and refine. Chat with selected sources, generate cited outputs, use Skills, search the web, create Artifacts, and keep working from the same context.
-
Use it everywhere. Continue from the web app, desktop app, or browser extension with your sources and team workspace in sync.
SourceWeft can optionally run approved commands in an isolated, temporary sandbox runtime. The sandbox is a scratch execution environment; SourceWeft /work remains the durable working-file area.
Mental model:
/workis durable SourceWeft workspace storage.- Sandbox
/workspaceis temporary and disposable. - Selected
/workfiles may be copied into sandbox/workspace/inputor/workspace/workonly after explicit approval. /kbsource evidence is not mounted or copied directly into the sandbox.- Commands run in the sandbox only after human approval.
- Outputs are not durable until collected back into
/workor published through a supported artifact pipeline. - Sandbox-generated outputs are not citable evidence unless verified against citable sources.
The sandbox provider is an operator detail; users should think in terms of an isolated temporary execution environment rather than a specific provider.
Use Docker Compose when you want to run SourceWeft from the published container image.
git clone https://github.com/SourceWeft/SourceWeft.git
cd SourceWeft
cp docker/.env.example docker/.env
# Edit docker/.env — set the two required secrets before using beyond localhost.
# OSS defaults start with quota enforcement on and payment/mail SaaS providers off.
# Model provider keys are optional for boot; configure one before using model features.
docker compose -f docker/docker-compose.yml up -dOpen http://localhost:3000, sign up, and start.
Sandbox execution is disabled in the base compose file. To enable sandbox
execution, point the DAYTONA_* values in docker/.env at an external Daytona
deployment and review the sandbox TTL, timeout, and file/output byte limits.
SaaS billing and payment checkout are opt-in. See the SaaS billing block in
docker/.env.example for the required SOURCEWEFT_SAAS_ENABLED,
BACKEND_BILLING_PROVIDER, Creem, and public checkout UI settings.
Bug reports, feature ideas, code, and design — all welcome.
See CONTRIBUTING.md to get started.
- 💬 Discord — Join our server
- 🐛 Issues — github.com/SourceWeft/SourceWeft/issues