Selected results
By the numbers
Live products
What I've shipped
Production systems and apps, each with its own page.
Vaelor · vaelor.ai
Self-hosted code-intelligence MCP server for AI coding agents, formerly go-code. Gotree-sitterApache AGEpgvectorPrometheusJaegerMCP
MemDB · memdb.ai
Self-hosted long-term memory database for AI agents. Pure Go core, one docker-compose. GoPostgreSQLApache AGEpgvectorQdrantRedis
OxPulse Chat · oxpulse.chat
Censorship-resistant encrypted chat and real-time video. RustAxumSolidJSPostgreSQLWebRTC
OxSay
Dictate, record calls, voice a script. All on your Mac: local, private, with an MCP server for agents. GoC++SwiftMetalCore MLMCP
Engineering & infrastructure
What makes it run
Libraries, engines, and MCP servers, built by the same hands. Most are open source and link to their repo.
go-kit
The shared Go toolkit the whole fleet is built on: tiered cache, circuit breaker, rate limiter, hedged requests, pub/sub, LLM and rerank clients. GoRedisPrometheus
GitHub →go-mcpserver
The bootstrap framework behind my MCP servers: one Run() call instead of the usual boilerplate, on the official MCP Go SDK. GoMCP
GitHub →go-workflow
A standalone DAG workflow engine for LLM and agent tool-loops: native MCP, Postgres SKIP LOCKED queue, crash recovery, approval flows. Apache 2.0. GoPostgreSQLMCP
GitHub →oxpulse-sfu-kit
Reusable WebRTC SFU library on str0m: simulcast, dual BWE (Kalman + googcc), pacer, AV1-DD, active speaker. Published on crates.io. Ruststr0mTokioWebRTC
GitHub →ox-whisper
Self-hosted, OpenAI-compatible speech-to-text in Rust: one ARM64 CPU, no GPU, real-time WebSocket streaming, word-level timestamps. RustONNXWebSocket
GitHub →go-twitter
A Twitter/X scraping library that gets through the anti-bot wall: TLS fingerprinting, a multi-account pool with health tracking, TOTP 2FA, CAPTCHA solving. GoGraphQLgo-stealth
GitHub →go-search
A self-hosted Perplexity: an MCP server that fuses web scrapers, API integrations and LLM summarization into cited answers. GoMCPLLM
dozor
AI-first server monitoring and deploy over MCP: walks a Linux fleet (Docker, systemd, SSL) and returns LLM-optimized output, with webhook deploys. GoMCPDockersystemd
Why now
Choosing an IC seat, on purpose
For 19 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. And I work inside code I don't own, not only my own: my graph backend was merged into MemOS (PR #966). Contributing upstream is the part of the job I want more of.
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. After 19 years running production end to end, I want to take on the hard parts with a strong team behind me.
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 →