Vault
Local model inference, sized around your workloads.
Explore Vault ↗01 / DEFENSE ENGINEERING
Bring local models and engineering tools to your team’s environment.
Talk through your program ↗FOR ENGINEERING TEAMS
COMPUTE + ENGINEERING
Local model inference, sized around your workloads.
Explore Vault ↗Investigate software issues and propose changes for your team to review.
Explore Blitz ↗Choose either product or both.
DEPLOYMENT REQUIREMENTS
Define data access, external connections and support with your team before deployment.
Review prompts, retrieved files, generated code, tool results, telemetry, storage and backups. Confirm approved destinations and outbound paths with the program owner; local inference alone does not define the whole boundary.
Scope repositories, retrieved context, credentials and trace visibility by program. Agree whether separate deployments are needed. Validate identity mapping and denied-access behavior before widening access.
Start with offline engineering work and reviewable diffs. Keep write permissions, test environments and release authority within your existing engineering process. Live equipment and release credentials require separate approval.
Agree collection, filtering, access, retention and deletion rules. Treat logs containing technical data as protected workflow content. Agree recording and analysis before enabling them.
Scope approved versions, artifact provenance, package transfer, rollback and support access before installation. Determine applicable customer handling requirements with your program and security owners.
START WITH A PILOT
Choose an engineering task with your program team.
A dedicated forward-deployed engineer supports your pilot.
Plan your engineering pilot ↗