Atrix Analytics: Ingests 42.7k events/s on a single CPU at 66 ms p99
Product analytics platform (a PostHog alternative) written in Rust on ClickHouse.
The calls that shaped it
Change the cost curve with the language choice
Analytics SaaS pricing scales with event volume because the vendor's compute does. A Rust ingest path on ClickHouse processes 42.7k events per second on a single CPU at 66 ms p99 — which means the unit economics of the product are structurally different.
Ship the whole PostHog surface
Feature flags, A/B experiments and session replay, not just event charts. A platform people switch to has to cover the workflows they already depend on.
An analyst, not a dashboard
The AI analyst is exposed over MCP, so questions about the data can be asked from any assistant — the same integration pattern as Atrix itself.
What this proves about how I lead
This is the clearest example of a CTO-level trade-off: choosing Rust and ClickHouse was a bet that performance would become a pricing advantage, and the benchmark proves it. I make technology decisions by asking what they do to the business model, then I verify them with numbers.
Every product under Atrix was built with the same operating model I bring to a team: a written architecture decision before the first commit, a thin vertical slice in production within the first weeks, AI-assisted delivery for the volume work, and human judgment reserved for the decisions that compound — data model, security boundary, provider choice. The hire-me page lays out how that translates into a 90-day plan for your company.
Want to talk through the architecture?
I'm happy to walk a hiring panel or a founder through any of these systems in detail — or ask my AI twin first.