Self hosting

Self-hosting means scanning, findings and storage run inside your infrastructure, deployed from the open-source repository with Docker. Your source code and results stay with you.

What stays in your environment

• Source code. Analysis happens where your code already lives. It is not transmitted to Sentrasec.
• Findings and scan history. Stored in your own database, under your retention policy.
• Decisions and records. Triage decisions, their evidence, remediation plans and re-scans stay with your deployment.
• Policy. Severity thresholds and gating rules are yours to define and enforce.

What crosses the boundary

Some features need outbound access:

• Vulnerability data updates, so SCA and container scans check against current advisories.
• Explanation prose, which is written by a language model. Triage decisions themselves are deterministic and do not depend on it.
• Integrations such as GitHub, GitLab, Jira, Linear, Slack, Microsoft Teams, webhooks and email.

We go through each of these with you before you deploy, so you know exactly what leaves your network and why.

Data residency

Because scanning and storage run in your environment, you choose the region, the storage, the retention period and the backup regime. Whether that meets a particular residency requirement is for you and your auditors to confirm.

Getting set up

Deployment sizing, installation, upgrade procedures and onboarding are handled with you, sized to your environment and constraints.

Book a demo to talk about a self-hosted deployment.