Local model serving
Open-weight models served locally through Ollama, routed via a hardened provider gateway with rate-limiting and metrics. Switch models per task. Nothing calls out to a third party.
An AI assistant over my own documents and systems, running on hardware I own. Nothing leaves the house, every answer cites its source and lands in a log, and the stack is hardened with the discipline I bring from network security.

Bank statements, receipts, health notes, letters, family plans: the most useful things to ask an AI about are exactly the things I would never paste into a cloud chat. So the assistant comes to the data, not the other way round.
The usual answers are a cloud subscription or an expensive appliance. I took a third route: open-weight models and plain software, on a box I already own.
Each layer comes from running code extracted from a fleet of 20+ self-hosted AI applications.
Open-weight models served locally through Ollama, routed via a hardened provider gateway with rate-limiting and metrics. Switch models per task. Nothing calls out to a third party.
RAG over your own documents with a source citation on every answer, auto-chunking, dedup, and reranking built in. No source, no claim.
A chat assistant grounded in your data ships in the first install. Multi-step agents that take real actions across your systems, observable, resumable, idempotent on retry, already run across the fleet and are packaged into the product next.
Every question and answer written to an immutable log. Role-based access, least-privilege database users per workload, secrets in environment only, capabilities dropped at the container.
The same hardening I apply to networks sits underneath: capability-dropped containers, per-app network isolation, prompt-injection defence and secrets hygiene from day one, not bolted on later.
I built it as software you run yourself, rather than a hardware box, for a few deliberate reasons.
The first deployment does one thing end-to-end, properly, before anything is added on top.
Honest status: the core is real and runs every day on my own machine, as the backbone of the apps in the portfolio. Connectors and agents grow as my own needs grow. It is a working lab, not a product launch.
The same stack sits under the household tools in the portfolio: private data that stays at home.
Curious how a piece of it works, or want to build something similar for yourself? Get in touch.
Last updated: September 2026