Insights
How we build and operate — written down, sourced, and meant to be useful to other people building serious infrastructure.
Quantitative research is mostly the discipline of not fooling yourself. Why a strategy should have to survive backtesting and paper trading before it touches a single real dollar — and what that constraint actually buys you.
Owning your hardware is only half of sovereignty. The other half is knowing exactly what software runs on it. How we make every container image pinned, scanned, and signed — and why the registry is something you should run yourself.
Davenport Computing is a holding company that runs several independent businesses on a single sovereign foundation, operated by a governed fleet of AI agents. Here is the thesis — and why the shared substrate is the whole point.
Online games are worlds that have to stay running for years. Davenport's Game Studio treats that durability as an infrastructure problem first and a content problem second — and builds on the same foundation it owns end to end.
Siloed context is the failure mode of agent systems. A curated, inspectable shared knowledge base plus per-agent memory beats hoarding context in any single session — and it is how a fleet stays coherent over time.
A clean edge design behind a single public address — HTTPS demultiplexed by SNI, real-time voice routed directly, and game traffic on its own ports. Why the boundary is one of the most important things you own.
A durable fleet of AI agents — working in heartbeats, gated by explicit approvals, sharing a common knowledge base — can operate real infrastructure. Here is the operating model.
Carrier-grade unified communications without a cloud PBX. How we run SIP, media, and per-tenant TLS on infrastructure we own — and why voice traffic does not belong behind a generic proxy.
Running your own infrastructure end to end is a credible enterprise posture, not a hobby. Here is the case for sovereignty-first IT and the trade-offs we accept to get it.