Direct engineering access
Regular working sessions with the engineers who build the platform, and a named technical contact for questions between them.
The design-partner programme:
shape the platform your teams will run.
The SecurityVault design-partner programme is for security and platform leaders who want a direct hand in the platform they depend on: working access to the engineers who build it, real influence over what ships next, and commercial terms that reward early commitment. Every partnership runs under NDA, and no partner is ever named without written consent.
What partners receive
What does the design-partner programme include?
A deliberately selective cohort, so every partner gets senior engineering attention rather than a support queue.
01
02
Roadmap influence
Discuss priorities with our team and review planned themes on the roadmap. Delivery commitments are agreed separately; the changelog records what has actually shipped.
03
Your deployment model
The hosted service, or a self-hosted deployment of the full platform on request for environments that must keep every component in-house.
04
Commercial discussion
Discuss commercial requirements with our team during the evaluation. Public pricing details are to be announced.
What we ask
What do we ask of design partners?
A partnership works when both sides commit. We ask for four things.
Real workloads
Your repositories, pipelines and cloud accounts, so the platform is proven on the estate you actually run.
Structured feedback
A regular review cadence with the people who use SecurityVault every day, from engineers to the CISO.
A named sponsor
One accountable owner on your side who can make decisions and unblock the rollout.
References only with consent
A reference call happens only with your written agreement, case by case. Your name is never used without it.
Built for regulated estates
Which sectors is the programme designed for?
The operating models SecurityVault was designed around. These describe the sector, not named organisations. See industries.
FS
Financial services
Evaluate release policy, separation of responsibilities and evidence for review periods. Discuss your regulatory control requirements against the published framework coverage; a mapping does not establish regulatory compliance.
HC
Healthcare and life sciences
Review application and cloud risks around sensitive services, then evaluate release controls and audit evidence. Establish your data-handling requirements and the relevant framework coverage before connecting an environment.
PS
Public sector
Evaluate deployment constraints, access controls and evidence against your procurement requirements. Review framework coverage and preview status with our team; using the platform does not confer an authorisation or certification.
SaaS
SaaS and technology
Deployment gates built for high build volume, policy-as-code authored and reviewed alongside service code, and tenant-scoped data throughout.
Joining
How does the application process work?
01
Introductory call
We discuss your estate, the decisions you need to defend and whether the programme is the right fit.
02
Scoped evaluation
One business-critical application, traced from commit to workload, so both sides see the value on your own code.
03
Partnership agreement
Terms, deployment model and review cadence agreed in writing, under NDA.