Staff Software Engineer · AI Infrastructure
I build production infrastructure for AI agents, and operate all of it myself.
Selected results
By the numbers
Live products
What I've shipped
Three production systems. Own domains. Open in a new tab.
MemDB · memdb.ai
Self-hosted long-term memory database for AI agents. Pure Go core, zero Python in hot path. Single docker-compose: PostgreSQL + Apache AGE + pgvector + Qdrant + Redis + embed-server. 72.5% LoCoMo LLM-Judge, beating Mem0 by 5.62pp using open-source primitives only. Apache 2.0, v0.23.0 in production, Discord community of early adopters. GoPostgreSQLApache AGEpgvectorQdrantRedis
go-code · krolik.tools
Code intelligence MCP server for AI coding agents. 35 tools across 16 languages: semantic search, call-graph and dataflow analysis, automated PR review. Apache AGE knowledge graph + pgvector + ColBERT reranker. Bridges Prometheus alerts and Jaeger traces directly to file:function hypotheses. Gotree-sitterApache AGEpgvectorColBERTPrometheusJaegerMCP
OxPulse Chat · oxpulse.chat
Censorship-resistant encrypted chat and real-time video, usable down to 1 KB/s. Verified a 5,000-user-per-room broadcast at 99.6% delivery (load test) on a 4-core box. Multi-domain partner-edge architecture (oxpulse.chat + 4 partner brands). Rust backend, SolidJS widget, production CSP. RustAxumSolidJSPostgreSQLWebRTC
Engineering & infrastructure
What makes it run
Libraries, orchestration, observability, built by the same hands.
- oxpulse-sfu-kit · Reusable WebRTC SFU library on str0m. Simulcast, dual BWE (Kalman + googcc), pacer, AV1-DD, active speaker. Published v0.11.0 on crates.io. Ruststr0mTokioWebRTC
- Multi-MCP ecosystem · 8 additional production Go MCP servers: web research, job hunting, startup research, security probing, knowledge graph, web automation, WordPress automation. All healthy 24/7. GoMCPDockerPrometheus
- dozor · Auto-deploy orchestrator for a 24-host fleet. GitHub webhook → debounced build queue → systemd. Telegram bus for alerts. GoDockersystemd
- Observability stack · Prometheus + Loki + Jaeger + Grafana + Alertmanager + 4 exporters. Hand-wired docker-compose. PrometheusLokiJaegerOTLP
Why now
Choosing an IC seat, on purpose
For 14 years I ran my own products and carried production myself: on call, no team to escalate to, every outage mine to fix. That taught me what holds up under real load and what only looks good in a demo.
I'm choosing an individual-contributor role deliberately. I want to go deep on hard infrastructure problems alongside a strong team, not manage one. I ship, I operate, and I take the pager. The ownership instinct stays the same; only the org chart changes.
Open to
What I'm looking for
Staff+ engineering roles at AI infrastructure companies
Anthropic, Cursor, Sourcegraph, Cognition, and similar: code intelligence, agent memory, distributed systems, platform, internal tooling. 14 years of carrying production pain personally means I ship and operate, not just prototype.
Founding-engineer roles at early-stage AI startups
AI-infrastructure and developer tools, where deep ownership and 0-to-1 building matter. Same work, earlier stage.
Let's talk
Staff and Senior engineering roles at AI-infrastructure and dev-tools companies: code intelligence, agent memory, distributed systems, platform. Open to founding-engineer roles at early-stage startups too. SF Bay Area, onsite or hybrid.
Email →