Evaluation & deployment packages, scoped per programme

What is included

• Working session with the Agnile engineering team on a representative architecture
• KAVACH walkthrough covering architecture canvas, TARA, attack paths, and Cybersecurity Case fragments
• Honest review of integration effort against the customer's existing toolchain
• Recorded session for internal sharing where needed

Typical inputs from the customer

• A representative ECU, feature, or system architecture description
• One identified engineer on the customer side to drive the working session
• Optional toolchain context (DOORS / Polarion / Jira / AUTOSAR ARXML) for integration discussion

Expected outputs

• Recorded session and KAVACH artefacts generated during the call
• Written summary of fit and integration gaps
• Recommended next-step scope

Deployment and security

No deployment required. The evaluation runs on Agnile-controlled infrastructure for the working session. No customer programme data is retained after the session unless the customer explicitly requests it.

Best next step

If the evaluation surfaces enough programme fit, the natural next step is a Scoped Pilot on one real engineering scope.

What is included

• Scoped pilot on one programme target — feature, ECU family, or vehicle subsystem
• Architecture-aware TARA, attack-path, and control-mapping workflows
• Engineer-in-the-loop review at every stage; AI-assisted acceleration is configurable
• Toolchain integration validation for the agreed targets
• Pilot readout with cycle-time observations and gap analysis

Typical inputs from the customer

• Programme scope agreement — what the pilot covers and what it doesn't
• Architecture inputs for the chosen scope (e.g. AUTOSAR ARXML, ECU descriptions, signal flows)
• One or more customer engineers participating in review sessions
• Toolchain access where integration is part of the pilot

Expected outputs

• Structured TARA draft on the agreed scope
• Attack paths, controls, and Cybersecurity Case fragments
• Toolchain integration validation
• Pilot readout with measurable cycle-time observations

Deployment and security

Customer-controlled desktop, on-premise, or customer-dedicated EU VPC — see the Trust Center deployment page. Sensitive vehicle-architecture data is designed to stay inside the customer-defined boundary.

Best next step

A successful Scoped Pilot typically expands into Program Deployment for the full programme scope, optionally with an Engineering Services Accelerator running alongside.

What is included

• On-premise or customer-dedicated EU VPC deployment of KAVACH
• Programme-wide TARA, attack-path, controls, and Cybersecurity Case workflows
• Toolchain integration with DOORS, Polarion, Jira, or AUTOSAR ARXML where applicable
• Onboarding, training, and governance setup for the customer engineering team
• Agnile engineering support and review across the programme
• AI configuration agreement — enable, scope, or disable AI-assisted features per programme

Typical inputs from the customer

• Programme-wide architecture, asset, and supplier scope
• Deployment-environment specification — on-premise infrastructure or VPC region
• Identity-provider, access-policy, and storage-encryption requirements
• Toolchain integration requirements
• AI configuration preference for the programme

Expected outputs

• Deployed KAVACH workspace inside the customer-defined boundary
• Programme-wide cybersecurity evidence chain — TARA, attack paths, Cybersecurity Case
• Toolchain integration in production
• Trained customer engineering team
• Agnile engineering support cadence agreed and running

Deployment and security

On-premise inside the customer's network, or customer-dedicated EU VPC scoped to one customer. Specific identity, access, encryption, and data-residency requirements are agreed at deployment. See the Trust Center deployment page for the full breakdown.

Best next step

Program Deployment can run alone or alongside the Engineering Services Accelerator when the programme needs senior engineering capacity on top of the workspace.

What is included

• Senior engineers embedded into the customer programme for a defined scope
• Specialist ownership of cybersecurity, safety, embedded, validation, or digital engineering workstreams
• Works with KAVACH, with the customer's existing toolchain, or both
• Knowledge transfer and process-alignment activities as part of the engagement

Typical inputs from the customer

• Programme scope and workstream definition
• Reporting line and governance into the customer organisation
• Tooling and infrastructure access for the embedded engineers
• Defined engagement duration and acceptance criteria

Expected outputs

• Specialist team extension on the customer programme
• Ownership of cybersecurity work-product delivery
• Knowledge transfer and process alignment

Deployment and security

Engineers operate inside the customer's programme environment under the engagement's contractual data-handling and confidentiality terms. KAVACH may or may not be part of the engagement, depending on customer choice.

Best next step

Engineering Services Accelerator engagements often inform a longer-term Program Deployment once the customer team has direct exposure to how the work scales.