How the engine actually works.
Long-form technical material for engineers integrating Kirtonic into a regulated stack. Protocol-level detail, system invariants, threat model, and the rationale behind each design decision.
- whitepaper · v1
The Kirtonic Engine
A technical reference for a runtime governance plane over multi-provider AI.
15 sections · ~6,000 words · payload schemas · type definitions · threat model - architecture · v1
Browser extension · backend reference
How the Chrome / Edge extension enforces governance at the keystroke. Request lifecycle, classifier pipeline, override loop, threat model.
15 sections · protocol diagrams · api spec · threat model - sdk reference · v1
Kirtonic SDK
Protocol reference and integration guide for the TypeScript, Python, and Go clients. Endpoint schemas, error model, wrapper patterns, fallback policy guidance.
12 sections · 3 languages · endpoint reference · error model · ops guidance - benchmarks · v1
Detection benchmarks
Purpose, methodology, datasets, runner architecture, output schema, and honest caveats behind the public detection-benchmark page. Includes the verdict-endpoint contract for buyers building their own tooling.
10 sections · OWASP LLM01 + Gandalf-style + benign baseline · reproducibility steps - coming
API Reference
Every public endpoint: signals, decisions, audit, integrations, models. Request / response shapes, scopes, error codes.
rest · openapi 3.1 · curl · python · node · go - coming
Deployment & Operations
Self-hosted topologies, region selection, backup / restore, key rotation, on-call runbooks.
kubernetes · vpc · sql migrations · monitoring · slo targets - coming
Compliance Mappings
Reference mappings of platform controls against UK GDPR, SOC 2, ISO 27001, HIPAA, and PCI DSS. Provided for evidence-gathering use, not as a substitute for certification.
mapping tables · audit log queries · sample reports
Stuck on integration, policy design, or anything in between?
If the documentation does not cover what you need, write to hello@kirtonic.io. Gaps are added to the roadmap so the next reader does not encounter the same issue.