A thread · 10 notes · G8KEPR
Building G8KEPR.
What my security startup does, why it's built the way it is, and what it's like building it alone.
- 1
What G8KEPR Is, in Plain English
The security startup I build on nights and weekends, explained without the jargon: what it guards, how it does it, and where it runs.
- 2
Four Checkpoints on One Request: The G8KEPR Pillars
API security, MCP security, an AI gateway and a verification engine, one at a time: what each one looks at and what it's there to catch.
- 3
MCP Tool Poisoning, and Why G8KEPR Fingerprints Every Tool
What MCP is, how a tool's own description can be turned against the model reading it, and why a hash that's re-checked on every call is such a useful tripwire.
- 4
No LLM-as-Judge: Why G8KEPR Uses Regex and Classical ML
A lot of AI security tools ask another AI model to grade the first one. G8KEPR doesn't. Here's why, what it costs, and what the published numbers do and don't mean.
- 5
Why It Runs in Your VPC (and Nothing Leaves)
G8KEPR is self-hosted by design: deployed with Helm or Terraform, sitting in your request path, sending zero bytes out and charging nothing per token. Here's the reasoning.
- 6
Building a Security Startup by Myself
One founder, a Delaware C-Corp, evenings and weekends, and a codebase with more lines of tests than lines of code. Here's what that ratio says about how I build.
- 7
From Do-Everything Platform to Correlation Engine
G8KEPR started as an AI security platform that tried to do everything. In September 2026 I narrowed it to the one thing that's actually different, and kept most of what I'd built.
- 8
Open Source for About a Day
On September 9 I decided G8KEPR would be open source under Apache-2.0. On September 10 I changed my mind. Both days had good arguments.
- 9
A Scorecard Instead of a Vanity Metric
How I keep score on G8KEPR with a feature scorecard graded 0 to 10, why it leaves out anything about clients or partners, and the P0-P4 lists that decide what I work on next.
- 10
How I Build with Three Claude Code Agents at Once
My build loop for G8KEPR: a plan in Todoist, a tracker page, three DEV briefs, and three Claude Code windows working in parallel while I supervise until it's done and tested.