SurfSense
Air-gapped, privacy-focused, open-source NotebookLM alternative. AI agent that researches, transforms, and edits your documents. Join our Discord: https://discord.gg/ejRNvftDp9
Runssource: GitHubhomepagePythonApache-2.0commit 176aed261a24
Python, Apache-2.0 licensed. The project labels itself: agent, agents, ai, notebooklm, notebooklm alternative, rag, self hosted and self hosted ai.
SurfSense runs. An Argusic agent installed it in 8 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
All Python trees (surfsense_backend, surfsense_mcp, surfsense_local/backend, plugins/remote/host core tests) install and pass tests; the web frontend fails to compile native deps on Node 18.x (requires 24.x); docs are clean.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 66.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- surfsense_web (Next.js) needs Node 24.x but only 18.19.1 is available; @rocicorp/zero-sqlite3 native module fails to compile3 minutes
- plugins/remote/host test_scaling.py, test_progress.py, test_results.py, test_plugin_lifespans.py hang (need browser/scraping infra)2 minutes
- surfsense_backend tests fail without EMBEDDING_MODEL env var (AutoEmbeddings.get_embeddings(None) fails)1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 3 hit, 1 fixed with no human help
- How the result was proved
- uv run pytest -m unit on surfsense_backend: 3482 passed, 4 skipped in 46.1s; uv run pytest on surfsense_mcp: 44 passed in 0.58s; uv run pytest on surfsense_local/backend non-worker tests: 3605 passed, 9 skipped in 22.55s; uv run pytest tests/test_host.py etc on plugins/remote/host: 30 passed in 4.21s; python scripts/check_docs.py: 158 files, 0 problems
- Model tokens used
- 80,775
- Exact commit tested
- 176aed261a24
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**surfsense_web**: Node 18.19 available but needs 24.x; `pnpm install` fails on native module compi… **docs check**: Clean — 158 files, 0 problems. 2026-10-17T07:57:11.051951Z ERROR codex_core::session: failed to record rollout items: thread 01a14… tokens used 80,775 Now let me compile the final report. Everything looks solid: **surfsense_backend**: `uv sync` succeeded, then needed `EMBEDDING_MODEL` env var set (documented i… **surfsense_mcp**: `uv sync` + all 44 tests passed. **surfsense_local/backend**: `uv sync` + 3605 passed (9 skipped for optional model files). **plugins/remote/host**: Core tests (30) passed; scraper tests hang without real browsers. **surfsense_web**: Node 18.19 available but needs 24.x; `pnpm install` fails on native module compi… **docs check**: Clean — 158 files, 0 problems.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 3 errors during setup, 2 of which were not solved.
Of the 107 agent projects Argusic has installed and timed, SurfSense was the 51st fastest to reach a running state, and 71 of 107 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 86.67 | 0.09 | |
| Argusic Runner | 1/3 | Did not run | 46.00 | 0.06 |
Topics (from GitHub)
agentagentsainotebooklmnotebooklm-alternativeragself-hostedself-hosted-aiweb-scraping
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/surfsense)Questions
- Does SurfSense run?
- Yes. SurfSense runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test SurfSense?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 176aed261a24. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test SurfSense?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does SurfSense take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does SurfSense need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing SurfSense?
- 3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does SurfSense compare with the alternatives?
- Of the 107 agent projects Argusic has installed and timed, SurfSense was the 51st fastest to reach a running state, and 71 of 107 reached one at all.
- Where is the evidence for SurfSense?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.