← Library

Video learning playbook

OpenSource AI Tools That Feel ILLEGAL To Get Free

What this video is about

  • The video counts down ten open-source tools (numbered 10 to 1) that together replace a stack of paid SaaS subscriptions, all running locally on hardware you already own, so no per-page metering, no query logging tied to your identity, and no surprise price hikes. [00:00]
  • The through-line the narrator repeats: cloud vendors rent you a metered API for each capability (OCR, translation, transcription, search, answering); running the open-source equivalent on your own machine removes the meter and keeps the data in the room. [00:23]
  • The stack layers into a system: the last three pieces (a local model engine, a workflow automator, and an autonomous agent) turn the collection of tools into something that reads, translates, transcribes, searches, answers, thinks, acts, and decides without you at the keyboard. [07:45]
  • Ollama is the load-bearing piece: it loads and runs the local language models (DeepSeek, Gemma, Qwen) that power every other tool in the stack. Everything else is an interface that hands its prompt to Ollama. [06:49]
  • The honest caveats: running unattended local models needs a serious GPU or a high-memory Mac (paid once, not monthly); and two tools should stay on their paid versions if you hit their limits (LibreTranslate outside European languages, Tesseract on handwriting). [08:28]
  • The real bill is time, not money: roughly a couple of hours a month keeping it updated and backed up, plus an afternoon of Docker setup up front. [09:11]

The pitch: own the stack, drop the meter

Source statementthese tools run your entire stack for free, on local hardware, "with no one snooping, and no cloud provider secretly hiking prices. Download once, own forever." The claim is not that each tool is novel, but that the paid-SaaS pattern (rent a metered API per capability) has a self-hosted replacement for each layer. [00:00-00:23]

Inferencethe value is highest where a capability is either high-volume (metered per page or per minute) or privacy-sensitive (documents you would not want to upload). For one-off low-stakes use, the paid cloud version is still the lower-effort choice, which the narrator concedes at the end.

#10 Tesseract: read text out of any image

Source statementTesseract "does one job, which is pulling readable text out of any picture, screenshot, or scanned document directly on your own machine." Cloud OCR (optical character recognition, turning a picture of text into editable text) rents you a vision API and charges per page; Tesseract runs on your hardware, so "there is no meter running." [00:23-01:07]

Visual evidence at 00:39: the repo describes itself as "Tesseract Open Source OCR Engine (main repository)", 6,731 commits, ~76k stars, Apache-2.0 license, tags include lstm, machine-learning, ocr, ocr-engine.

#9 LibreTranslate: translate without uploading the document

Source statementpasting text into a translation website is fine for a blog post, but translating "a legal contract or a medical letter" uploads confidential data to a server you do not control. LibreTranslate "gives you a free and open source Machine Translation API that runs directly on your own hardware," so "a contract never leaves the room it's sat in." [01:07-02:10]

Visual evidence at 01:32: the repo About reads "Free and Open Source Machine Translation API. Self-hosted, offline capable and easy to setup.", libretranslate.com, 1,723 commits, AGPL-3.0 license.

#8 Scriberr: transcribe your own recordings locally

Source statementinstead of paying a cloud service to transcribe meetings, run Scriberr, "an audio transcription app" that ships ready to run in Docker (so you skip compiling dependencies by hand) and keeps the recording of your voice on your own machine. [02:10-02:49]

#7 SearXNG: search without generating a log

Source statementevery query typed into a major provider "is saved in a log attached to your identity." SearXNG is "a free internet metasearch engine" that runs locally and aggregates results from various search services; because you host it, the underlying providers see the aggregator, not your network. "Running search this way removes the record rather than relying on an incognito window to hide it." [02:49-03:45]

Visual evidence at 03:05: the repo About reads "SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled.", docs.searxng.org, 9,669 commits, tags bing, brave, duckduckgo, google, metasearch, privacy.

#6 Vane (formerly Perplexica): the local answer engine

Source statementa $20/month subscription buys "a system that reads those raw links and writes a direct response." Number six replaces it. Every article tells you to install "Perplexica, but if you look for it today, the repository is now called Vane. That single rename is a sign of how fast this world moves." Vane "is an AI powered answering engine" that takes the results your machine pulled and writes the answer, entirely on your hardware. [03:45-04:38]

#5 Khoj: an assistant over your own files

Source statementa public answer engine works for public information, but "what is supposed to read the private files sitting in the folders on your own disk?" Khoj is "your AI second brain" that "gets answers from the web or your docs" and is self-hostable, "which is a strict requirement for this to work," because a cloud service could only answer about your files if you first uploaded every one of them. [04:38-05:29]

#4 Open WebUI: one interface over the whole stack

Source statementthe stack runs in the background, so "you still need an interface you can talk to." Open WebUI is "a user friendly AI interface" that wraps the setup into a chat window that "looks and behaves exactly like the paid service you probably already use." Its readme calls it a self-hosted AI platform "designed to operate entirely offline": unplug the router and you keep your assistant, chat history, and documents, because nothing depends on a round trip to a data center. [05:29-06:49]

#3 Ollama: the engine doing the thinking

Source statementan interface does not generate answers itself. "That something is Ollama. It's the engine that loads and executes the language models powering every tool we just assembled." The search wrappers and transcription apps are only interfaces whose job is to pass your prompt to Ollama running in the background; it "acts as the local server for your models," and its catalog lists models by name "from DeepSeek and Gemma to Qwen." Because of Ollama, nothing in the stack gets sent to a cloud service. [06:49-07:45]

#2 Activepieces: automate it so it runs while you sleep

Source statementthe system "only works while you're sitting at your keyboard giving it instructions." Activepieces handles workflow automation, "running in the background passing data from one step to the next." Because you run the free edition on your own hardware, "it has unlimited runs, so using it more doesn't cost more." This is what turns the collection of tools into a system that runs unattended. [07:45-08:28]

Visual evidence at 07:52: the flow builder shows a three-step automation, New Item in Feed (RSS) then Ask ChatGPT then Create Tweet, with a "Learn about this flow" panel, the self-hosted equivalent of a paid Zapier/Make flow.

#1 OpenHands: the agent that decides what to do

Source statementan automation chain "does exactly what it's told," so if you are not typing the instructions, "something else has to decide what to tell it to do." OpenHands sits at the top of the chain as "an autonomous coding agent" that operates the tools underneath it, so the finished stack "reads, translates, transcribes, searches, answers, thinks, acts and decides entirely on hardware you own." You can point it at a model running on your own machine instead of a paid one over the internet. [08:28-09:11]

Visual evidence at 08:35: the landing page reads "OpenHands / Agent Canvas / The self-hosted developer control center for coding agents and automations", noting you can "run OpenHands, Claude Code, Codex, Gemini, or any ACP-compatible agent across local, remote... backends" (BETA, BUILD PASSING, v1.14.0).

The verdict, and where to keep paying

Source statementfor most of the stack the answer is "yes, worth it," because Ollama is "a straight replacement where you give up nothing." But a local model good enough to run unattended "needs a serious graphics card, or a Mac with a lot of memory in it. The hardware costs money, but you only pay it once." And there are two places to keep the commercial versions: LibreTranslate's accuracy "drops compared to the paid tools" outside European languages, and Tesseract "struggles" on handwritten notes while paid vision models still win. "The honest bill is hours, not money", roughly a couple of hours a month updating and backing up. [09:11-10:09]

Inferencethe argument is not "self-host everything." It is that the engine layer (Ollama) is a clean swap with no quality loss, the privacy-sensitive layers (documents, transcription, search) win on data control, and two accuracy-bound tools (translation outside European languages, OCR on handwriting) are worth keeping paid. The deciding question the narrator poses: is keeping documents private, or running unmetered automated workflows, worth an afternoon of setup to you.

Tools and resources

Tool Number Replaces Self-description (on screen) License / signal
Tesseract#10Cloud OCR / vision API (per-page)"Open Source OCR Engine"Apache-2.0, ~76k stars
LibreTranslate#9Paid translation API / website"Free and Open Source Machine Translation API. Self-hosted, offline capable"AGPL-3.0
Scriberr#8Paid transcription subscription"Self-hosted AI audio transcription"MIT, 2.9k stars
SearXNG#7Logged search engines"A free internet metasearch engine... neither tracked nor profiled"docs.searxng.org
Vane (ex-Perplexica)#6~$20/month answer engine"An AI powered answering engine"ItzCrazyKns/Vane
Khoj#5Cloud doc-assistant (upload required)"Your AI second brain... answers from the web or your docs"khoj.dev
Open WebUI#4Paid chat interface"User-friendly AI Interface (Supports Ollama, OpenAI API)"openwebui.com
Ollama#3Hosted model API"Build with open models, on your computer and in the cloud"serves DeepSeek/Gemma/Qwen
Activepieces#2Zapier/Make (metered runs)"Workflow automation... unlimited runs" (self-hosted free edition)self-hosted
OpenHands#1Paid autonomous coding agent"The self-hosted developer control center for coding agents"ACP-compatible, v1.14.0

Claims to verify

  • "Unlimited runs" for Activepieces applies to the self-hosted free/community edition specifically; cloud or enterprise tiers meter differently. Confirm against Activepieces' current licensing before relying on it. [07:45]
  • The star counts and version numbers shown (Tesseract ~76k, Open WebUI 17,819 commits, OpenHands v1.14.0, the Ollama model names nemotron-3.5/gemma4/qwen3.6) are as of the video's mid-August 2026 capture and drift quickly. [multiple]
  • The Perplexica-to-Vane rename is shown in the repo history; confirm the current canonical repo/name before installing, since the narrator's own point is how fast this renames. [03:45]
  • "Give up nothing" for Ollama versus a hosted API is true on capability but not on quality-per-dollar-of-hardware: a small local model is not a frontier hosted model. The video's own GPU caveat is the counterweight. [06:49, 08:28]

Glossary

  • OCR (optical character recognition): turning a picture of text (a scan, screenshot, or photo) into editable, searchable text.
  • self-hosted: running the software on hardware you own and control, rather than calling a company's servers over the internet.
  • metered API: a cloud service that bills per unit of use (per page, per minute, per token), so heavier use costs more.
  • machine translation API: a programmatic endpoint that translates text between languages on request.
  • Docker: a packaging system that ships an app with its dependencies as a ready-to-run container, so you avoid installing and compiling libraries by hand.
  • metasearch engine: a search tool that queries several other search engines and merges their results, instead of running its own crawler.
  • answer engine: a tool that reads search results and writes a direct written answer (the pattern popularized by Perplexity), rather than just returning links.
  • second brain: an assistant that indexes and answers questions over your own notes and documents.
  • Ollama: a local server that downloads, loads, and runs open language models on your machine and exposes them to other apps.
  • mixture-of-experts (MoE): a model design where only a subset of the network's parameters activate per token (e.g. a 30B model with 3B active), giving large-model quality at lower run-time cost.
  • workflow automation: chaining separate apps into an automatic pipeline where one step's output feeds the next (the Zapier/Make/n8n category).
  • autonomous coding agent: an AI agent that plans and executes multi-step coding and tool-use tasks on its own, deciding the next action rather than waiting for each instruction.
  • ACP (Agent Client Protocol): an open protocol that lets different coding agents (Claude Code, Codex, Gemini, OpenHands) be driven through a common interface.
  • AGPL / Apache-2.0 / MIT: open-source licenses; MIT and Apache-2.0 are permissive, AGPL additionally requires that network-served modifications be shared back.

Personal recommendations

Evaluate Ollama as a fully-local brain option for fleet test-box children

Source
06:49
Demonstration
Ollama ran DeepSeek/Gemma/Qwen locally as the model server behind every other tool, with no cloud round trip.
System value
fleet-control already supports a brain swap (the cc-kimi / OpenRouter path for TEST-BOX workspaces). Ollama would add a third option, an offline, zero-API-cost local brain, useful for cheap mechanical fleet steps on the test box where a frontier model is overkill. Client children stay on Claude-on-Max, unchanged.
Proposed form
Evaluation task (does a local Ollama model drive Read/Edit/Write tool-use reliably enough for a caged child, and does this box's GPU/RAM run one at usable speed), then a scoped brain-swap entry if it passes
Target project
fleet-control (test-box only)

Test self-hosted Activepieces against current paid client automation

Source
07:45
Demonstration
a three-step RSS-to-ChatGPT-to-Tweet flow ran in the self-hosted free edition with unlimited runs.
System value
client automations currently lean on paid metered tools (Make, Instantly in the RR-connections stack). A self-hosted automator could cut metered-run cost for high-volume flows, but managed reliability and uptime are the reason to be cautious, so this is an evaluation, not a swap.
Proposed form
Evaluation task weighing self-hosted unlimited-run savings against the operational burden of hosting and monitoring it versus managed Make
Target project
RR-investment / client automation (evaluation)

Note OpenHands as a comparison point for fleet-control's agent runner

Source
08:28
Demonstration
OpenHands presents as a self-hosted control center that runs Claude Code, Codex, Gemini, or any ACP-compatible agent across local and remote backends.
System value
fleet-control solves a related problem (spawn, isolate, and supervise agent children). OpenHands' Agent Canvas and ACP support are worth reading as prior art, for the dashboard/control-center UX and for whether ACP is a useful interop target, not as a replacement.
Proposed form
Reference note in fleet-control docs; a short read-and-summarize of OpenHands' architecture and ACP
Target project
fleet-control (reference only)

Consider SearXNG as a privacy-preserving backend for the web-research workflow

Source
02:49
Demonstration
SearXNG aggregated multiple engines locally so the upstream providers saw the aggregator, not the user, with no query log tied to identity.
System value
the current web-research lane uses WebSearch/Firecrawl directly. A self-hosted SearXNG instance could serve as a lower-noise, non-logged search backend for research sweeps, though it adds a service to maintain.
Proposed form
Optional evaluation, low priority; only if the maintenance cost is justified by research volume
Target project
Personal computer tooling

Take this with you

Save the playbook to read later, or hand the raw notes to your favorite AI.

What's this?

The Markdown file (a .md file) is a plain-text copy of this whole playbook, written in the simple format AI chat tools read best. It keeps the headings, links, timestamps, and captions and drops all the page styling. Think of it as the raw notes behind this page, ready to hand to an assistant.

To use it, download the file and drag it into ChatGPT, Claude, or any AI chat (or just paste the text in), then ask for what you want: “Summarize this into a one-page cheat sheet,” “Turn these steps into a checklist I can follow,” or “Quiz me on the key ideas.” Because the file is already structured, the assistant works from the real content instead of guessing.