Current · v1.10.80
Technical brief
Cerbi Gateway Technical Brief
Current Gateway architecture, controls, reliability mechanics, adoption paths, and benchmark methodology without unverified throughput claims.
Review a Scanner finding or logging requirement against your existing controls. If a recurring gap remains, scope one CerbiShield workload, policy, evaluation window, and evidence review.
Documents + evidence
These documents reflect the current product architecture. Earlier CerbiStream-only sales PDFs have been removed from the primary document library because they no longer describe the full platform accurately.
Technical brief
Current Gateway architecture, controls, reliability mechanics, adoption paths, and benchmark methodology without unverified throughput claims.
Platform overview
The current Scan → Govern → Enforce → Prove model across Cerbi Scanner, CerbiShield, CerbiStream, Gateway, and the Dashboard control/evidence plane.
Performance evidence
Reproducible BenchmarkDotNet results for CerbiStream. Kept intentionally separate from the forthcoming dedicated Gateway throughput benchmark.
Technical documentation
Endpoint contract, deployment model, policy handling, reliability behavior, evaluation guidance, and the distinction between Gateway and CerbiStream.
Documentation policy
Performance numbers are labeled by component and test method. CerbiStream results are not presented as Gateway results.
Compliance-related features are described as controls and evidence support, not as certifications or legal conclusions.
Preview and release-candidate functionality is labeled as such until the corresponding release gates are complete.
We can walk through the trust boundary and a bounded pilot using your actual environment assumptions.