Request internals access
What is behind the internals gate, who we approve, and how to ask. Initial reply within 1ā2 business days.
These public docs are complete for integration: you can connect a provider, route your agent, read verdicts, verify evidence, and deploy ā without asking anyone for anything.
What they deliberately leave out is mechanism. How the integrity engine reaches a verdict, how the evaluations compose, how to author policy against your own workflows, and the source itself. That material is behind a gate, and this page tells you how to get through it.
What is behind the gate
How a verdict is actually reached ā what the engine evaluates, how the results combine, and where the decision boundaries sit. The part the public tier describes only in outline.
Writing and versioning your own policy instead of adapting one of the starting sets: the structure, the review workflow, dry-running a change against recorded traffic before it goes live.
Component-level architecture, the deployment topologies, and the operational runbooks ā what to watch, what to alert on, what to do when it fires.
Run the stack yourself, audit the detection path, and evaluate it against your own workloads rather than our examples.
How detection quality is measured, on what data, and what the numbers mean ā including where they are weakest.
A shared Slack channel with the engineers who wrote it, for integration and evaluation questions.
Who we approve
We approve readers who are actually going to use the material:
- teams integrating Sentisec, or evaluating it for a real deployment;
- security reviewers assessing it on behalf of such a team;
- investors and partners doing technical diligence.
We decline requests whose stated purpose is competitive research. That is not a judgement about you ā it is the reason the gate exists.
How to ask
Email [email protected] and tell us:
- Name and company
- Role ā who you are in the decision
- Use case ā what you are integrating, and what risk you are trying to close
- Do you need the source? ā yes, no, or not sure
Email [email protected]
What to expect
Initial reply: 1ā2 business days. Docs access is granted in that reply when the use case is clear.
Source access: a further 1ā2 business days after the NDA round-trip. It is a standard one-way NDA covering the internal documentation and the source; we can countersign your own form instead if your legal team prefers it.
Your team: one grant covers your whole team for the documentation. Source repository seats are provisioned individually.
One-off questions: if you only need one thing answered, say so. We would rather reply inline than run you through a provisioning cycle for a single question.
In the meantime
The public docs are not a teaser. If you have not already, these are the pages worth your time before you ask for more: