Single tenant by design
One install serves one organisation. There is no shared processing tier and no multi-tenant data path to reason about, which is what makes an in-network deployment achievable.
Security
Built to be handed the keys.
An agent that writes into a real repository is a serious piece of trust. Here is how Intelli-Dev is designed to earn it, and an honest account of where that work currently stands.
Design principles
The decisions that shape the security story
It uses credentials you issue
Intelli-Dev talks to your code host and tracker using access you create, scope and can revoke at any moment. It has no standing access to anything you have not granted it.
Two human checkpoints
A person approves the specification before code is written, and your reviewers approve the merge request under your existing branch protection before anything lands. Neither checkpoint is a feature we expect you to disable.
It cannot reach production
The pipeline ends at a merge request and a pipeline run. It does not hold deployment credentials for your production environment and is not designed to.
An auditable record per order
Each order keeps the original request, the approved specification, every gate result and every approval, so a change advisory board or an internal audit can reconstruct what happened.
Inference where you choose
Model routing is configurable per pipeline role. In a Whiteboxed install you can point every stage at models you host yourself so source never reaches a third party.
Where we actually are
What we will not claim
Intelli-Dev is in early access. It does not hold a security certification, and we are not going to put a badge on this page that we have not earned.
Two items are gating our own path to general availability, and we treat both as hard:
- Credential handling hardening. The way integration credentials are stored and rotated is being reworked before the product is offered commercially.
- An independent penetration test. Conducted by a party that is not us, with findings addressed, before general availability.
If you are evaluating Intelli-Dev for a regulated environment, ask us about both directly. You will get a straight answer about their status rather than a marketing one, and if the answer is not good enough for your risk appetite yet, that is a reasonable conclusion to reach.
Reporting a vulnerability
If you believe you have found a security issue in this website or in Intelli-Dev, please tell us before telling anyone else. We will acknowledge your report and keep you updated on the fix.
security@intelliinfra.aiQuestions your security team will ask first?
Put them in the waitlist form. We would rather have the hard conversation early than waste your time.