Company/About

Security is not a feature.
It is the product.

We build the platform we wanted to run: scanners that cannot hurt you, one graph that connects code to runtime, and decisions that fail closed and sign themselves.

Why we exist

A scanner result is not a finding.

It becomes one when you know which commit introduced it, which image carries it and which workload exposes it. Security teams have never lacked results. They lack that chain.

01

Hostile by default

Every scanner — including our own native engine — runs as an ephemeral Job with credentials for the target only. Results enter through one signed callback. We built the trust boundary first and the features on top of it.

02

One vocabulary

52 entity types and 32 relationship verbs, frozen and versioned. When we add a type we add a version; we never change what a stored edge means.

03

Honest gaps

A lineage view says source_gap when it does not know. It never draws an edge to make the picture look complete, and inferred edges never complete a strict path.

04

Fail closed

A policy error is a deny. A callback without a valid token and signature is rejected. Uncertainty is an explicit failure, never a silent pass.

05

Humans decide

Disposition is a human write with a reason code, enforced at the ORM layer and by a database trigger. AI triage is advisory and audited.

06

We use what we sell

The platform's own repository and images are scanned on the same pipeline; the merge gates that block our releases are the ones we describe on this site.

The company

Who we are.

Legal entity
SecurityVault Systems Private Limited, incorporated in India. A United States entity is planned; until then all contracts are with the Indian company.
Stage
Early access. Hosted and self-hosted deployments are available to qualified organisations; general availability has not been announced.
Ownership
Independent and founder-led. No institutional funding has been announced.
Certifications
None held today. We publish our security architecture and answer questionnaires on request; see the trust page.
Infrastructure
Kubernetes on hardware we own and operate, in India. Regional deployments and fully self-hosted installs are available on request.
Talk to the engineers

Bring a repo and a cluster.

Conversations start with the people who built the platform, not with a sales deck.