Filorag — Search Inside Any Video vs Scribe

Filorag — Search Inside Any Video and Scribe are both productivity tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Filorag — Search Inside Any Video

FiloRag's Spotter positions itself as a semantic search and Q&A layer over videos and documents, letting you ask a question and land directly at the relevant moment or passage rather than scrolling blind. The core workflow is upload, query, get a located answer with source attribution. That loop works well for single-file searches and quick summarization tasks. The ceiling appears when you need cross-collection reasoning or branching research workflows — the tool handles retrieval, not synthesis chains. Teams with those needs add a separate analysis layer on top.

Scribe

The pipeline runs in three stages — capture from git repos, Claude Code/Codex sessions, iMessage-dropped URLs, and drop files; triage via keyword-density scoring before any LLM call touches the input; then compile into a typed-graph wiki of plain markdown with auto-generated wikilinks and backlinks. FTS5 pre-filtering means sessions with nothing worth keeping cost zero API tokens. The vendor states the full pipeline runs against a local Ollama server with one line changed in scribe.yaml, eliminating API spend entirely. Where it strains: the system is only as useful as the agent's ability to query the KB — if your agent doesn't read CLAUDE.md or AGENTS.md on startup, the handshake Scribe writes is ignored. Teams adopting this commit to a local-first, terminal-native workflow; there is no hosted dashboard or GUI to inspect what Scribe wrote.

Attribute	Filorag — Search Inside Any Video	Scribe
Pricing	Paid	Free
Price	₹499/month	—
Free trial	No	No
Open source	No	Yes
Has API	No	No
Self-hosted option	No	Yes
Platforms	Web-based (app.filorag.com)	macOS, Linux (Go binary)
Pros	Timestamp-level jump-to-moment retrieval in video files, so you reach the exact explanation you need without scrubbing through an entire recording. Natural-language Q&A over uploaded documents, which means exam prep or meeting follow-up becomes a query instead of a reread. Cross-document search across a paper or video collection, so a literature review question returns relevant passages from multiple sources in one pass rather than requiring file-by-file searches. Automatic summarization of long recordings and documents, so you can triage a two-hour webinar for relevant topics before investing full attention. Unified interface for both video and document content, which means you are not switching tools depending on whether the source material is a PDF or a recorded call.	FTS5 pre-filtering rejects low-value sessions before any LLM call, so zero-insight sessions cost zero tokens — which means running the pipeline daily against a local Ollama server produces no API bill and no noise in the output corpus. The CLAUDE.md and AGENTS.md handshake injection means every new agent session in every project queries prior decisions automatically, so agents stop proposing the library you already evaluated and rejected two projects ago. A typed 10-kind edge schema (supersedes, contradicts, derived_from, and others) connects articles relationally, so the KB captures decision lineage rather than just a flat pile of notes that have no memory of which choice replaced which. One flag in scribe.yaml switches the entire pipeline to a local Ollama server, which means you can run extraction, absorb, and Dream consolidation with zero external API dependency and no data leaving your machine. Output is plain markdown in a git repo you control, so the corpus survives any change to Scribe itself — open it in Obsidian, VS Code, or vim, push it to Gitea or Forgejo, and no vendor has leverage over your data.
Cons	Cross-collection reasoning hits a wall when your research requires synthesizing conflicting findings into a structured argument: the tool retrieves passages but does not construct the argument, so researchers manually bridge the gap in a separate writing environment. No self-hosted deployment option means any document you upload lives on FiloRag's infrastructure — teams handling sensitive contracts, patient records, or confidential IP face a hard stop here and switch to a self-hostable alternative rather than accept that exposure. The freemium tier caps usage at a threshold that becomes visible quickly for anyone with a real document or video backlog; heavy users hit the ceiling before they can evaluate whether the tool fits their full workflow, and the jump to paid is gated rather than gradual. No confirmed API surface means embedding Spotter's retrieval capability into an existing internal tool or research pipeline requires manual workarounds — teams building automated ingestion or retrieval workflows choose a platform with a documented API instead.	The handshake only works if the agent reads CLAUDE.md or AGENTS.md at session start — agents or wrappers that skip that file ignore every decision Scribe wrote, and there is no fallback mechanism to force context injection, so teams with non-standard agent setups get no benefit from the KB without manual wiring. Scribe is a single-developer local tool with no multi-user access model: one machine, one corpus, one git repo. Teams of two or more who need shared architectural memory hit this wall immediately and end up running separate personal instances while syncing decisions by hand — at which point they are maintaining the problem Scribe was supposed to solve. The Dream consolidation cycle runs on a fixed cron schedule (weekly, Sundays at 02:00 per the docs), so a decision made Monday that contradicts a decision made Friday won't be cross-linked until the next consolidation window — teams working fast on interrelated projects find the KB is always one cycle behind the work. There is no GUI, no hosted dashboard, and no search UI outside the terminal qmd command or Claude Code's MCP integration — teams whose product managers or non-engineering stakeholders need to read the KB have no access path without standing up a separate rendering layer like mdbook or Obsidian.

Bottom line

Filorag — Search Inside Any Video is paid while Scribe is free; Scribe is open source. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Filorag — Search Inside Any Video and Scribe?

Filorag — Search Inside Any Video is Paid, while Scribe is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Filorag — Search Inside Any Video better than Scribe?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.