Skip to main content

Stack · Knowledge OS

Tools, with their status made explicit.

Mostly open source, mostly self-hosted, all here for a reason. Search by job, move through the categories, or filter by how far each tool has actually made it into the work.

31 catalog entries 6 fields Public-safe notes

Browse the catalog

31 tools, with the status made explicit

“Active” is part of a current, repeatable workflow. “Testing” is installed or exercised, but not yet a default tool. “Archived” is no longer in active evaluation or routine use, and is retained as historical context.

Showing all 31 tools.

Models & interfaces

The engines and workbenches used to generate, compare, and route AI output.

Ollama

Active

Runs language, vision, and embedding models locally.

Private model work, retrieval embeddings, prompt development, and local fallbacks.

Source ↗

LiteLLM

Active

One OpenAI-compatible gateway in front of local and cloud models.

Keeps applications independent from any single model provider and gives each consumer one stable API.

Source ↗

ComfyUI

Active

Node-based local image and video generation.

The controllable generation engine behind visual experiments, nex_img, and production artwork.

Source ↗

Visual Foundry

Active

A studio-facing generation layer around local visual models.

Turns repeatable generation workflows into a cleaner API for brand imagery and reviewed creative output.

Open WebUI

Active

A self-hosted chat and tool-use interface for local models.

Conversational retrieval and operator workflows that connect models to search, files, automation, and design tools.

Source ↗

LibreChat

Testing

A self-hosted multi-provider chat workspace.

Used to compare a second interface for models, retrieval, and MCP-connected tools without changing the gateway.

Source ↗

Jarvis

Archived

A retired personal-assistant service that joined models, retrieval, and operator tools in one interface.

Previously provided one assistant surface and proved a resilient routing pattern; retained here as historical context after the service was retired.

Retrieval, CRM & reporting

Where source material and operational records become searchable, structured, and visible.

Qdrant

Active

A vector database for semantic search and retrieval.

Stores embedded legal, organizational, and knowledge collections queried through purpose-built tools.

Source ↗

Twenty

Active

An open-source, API-first CRM.

Custom objects and workflows model funders, stakeholders, attorneys, opportunities, and follow-up as living pipelines.

Source ↗

Metabase

Active

Dashboards and practical analysis over operational data.

Turns pipeline records into views people can read without hand-writing a new query for every question.

Source ↗

Automation & research

The connective layer: gathering evidence, moving records, and handing work to the next system.

n8n

Active

Visual workflow automation with code where the edge cases need it.

Coordinates intake, enrichment, research, notifications, publishing, and human review gates.

Source ↗

SearXNG

Active

A privacy-respecting metasearch engine.

Supplies web evidence to research and enrichment flows without binding the system to one commercial search API.

Source ↗

SpiderFoot

Active

Automated open-source intelligence collection.

Adds structured public-web evidence to research pipelines where broad discovery matters more than a single lookup.

Source ↗

Postproxy

Testing

A unified API for scheduled social publishing.

Explored as the final publishing handoff for generated and human-approved creative, without maintaining one integration per network.

Project ↗

Tesseract OCR

Testing

Open-source optical character recognition.

A utility path for turning scanned pages into text before retrieval and document workflows can use them.

Source ↗

Design & media

A local design engine, a brand-control layer, and bridges into production applications.

Open Design

Active

A local-first, agent-native design platform.

Provides project workspaces, design systems, editable artifacts, and structured handoffs for agent-authored design.

Project ↗

NexusDesign

Active

Origin Creative’s brand-operations layer on top of Open Design.

Applies brand rules, coordinates specialist agents, and routes creative through a human approval gate.

Source ↗

Adobe Illustrator MCP

Active

A bridge from agent workflows into native Illustrator documents.

Builds editable files, places artwork, manages layers and swatches, and supports print-production checks.

Source ↗

Premiere Pro MCP

Testing

Agent control for Premiere projects, timelines, effects, and exports.

Installed and exercised as a video-production bridge; it is available when a Premiere editing session calls for it.

Source ↗

Penpot

Testing

An open-source browser-based design and prototyping tool.

Evaluated as an own-your-files collaborative canvas and programmable alternative for interface work.

Source ↗

HyperFrames

Testing

Agent-native HTML-to-video rendering: write HTML, CSS, and JavaScript, then render a deterministic MP4.

Being adopted to turn web-native compositions and structured data into repeatable rendered video for creative and design pipelines.

Source ↗

Remotion

Testing

A framework for creating videos programmatically with React (source-available; a company license applies to larger organizations).

Being evaluated to build data-driven and templated motion graphics as code, alongside the HTML-to-video path.

Source ↗

Knowledge & agent context

Different kinds of memory kept separate so tools, procedures, ideas, and reasons do not blur together.

Obsidian

Active

A plain-Markdown knowledge vault.

Owns long-lived notes and research in portable files, with selected material available to retrieval.

Project ↗

codebase-memory

Active

A structural knowledge graph over source code.

Lets coding agents discover existing symbols, routes, and call paths before they open or duplicate large parts of a repository.

Source ↗

Layered agent memory

Active

A small set of plain-Markdown stores with distinct jobs.

Separates current code, operating procedures, personal knowledge, and the durable reasons behind decisions.

Infrastructure & publishing

The source control, routing, monitoring, and web layer that keeps the rest reachable and reviewable.

Gitea

Active

Self-hosted Git and repository management.

Keeps private source close to the systems it drives while preserving normal branch and review workflows.

Source ↗

Caddy

Active

A reverse proxy with automatic TLS.

Handles secure web serving and routing for selected applications.

Source ↗

Pi-hole

Active

Network DNS with ad and telemetry blocking.

Keeps routine network noise down and supports a cleaner browsing environment.

Source ↗

Uptime Kuma

Active

Self-hosted service monitoring.

Tracks service availability so a silent failure becomes visible.

Source ↗

Astro

Active

A content-focused web framework that ships little client JavaScript by default.

Builds this resource site, its case studies, and the Markdown-friendly library.

Source ↗

Cloudflare Pages

Active

Static-site hosting at the public edge.

Publishes the committed Astro build after a deliberate review and manual release step.

Docs ↗

System map

One system, not a pile of apps.

Models and interfaces provide capability. Automation carries work between them. Retrieval, CRM, and reporting give the work memory and a visible state.

Design and media turn generated output into reviewed artifacts. Knowledge tools keep the reasons and source material close enough for the next person—or agent—to pick up.

Infrastructure is the quiet layer underneath: source control, publishing, routing, and monitoring. The point is not the inventory. It is the clean handoff between fields.

See the systems as case studies →