// engage with ziru labs

Engage.

Substantive engagement with Ziru Labs proceeds along five structured tracks. Each track has its own framing, materials, and protocol. Specific cleared counterparties under active engagement are not named publicly.

// route 01 of 05

Strategic Technology Partners.

Silicon vendors, hyperscalers, and systems integrators evaluating Phoenix for platform integration.

Engagement scope: technical-track integration analysis, platform-fit evaluation, and commercial-term framing for product-track integration of the Phoenix primitive into the partner's silicon, cloud, or systems offering. Substantive engagement proceeds under mutual NDA. Materials provided to NDA counterparties include the Technology Architecture reference document, the Phoenix Block Diagram, and the MWP Test Plan.

  • NVIDIA · AMD · Intel · ARM Holdings
  • AWS · Microsoft Azure · Google Cloud · Oracle Cloud
  • Major systems integrators on classified AI delivery contracts
partners@zirulabs.com

// route 02 of 05

Commercial Partners and Customers.

Enterprises across regulated verticals, frontier AI labs, and mission-critical operators evaluating Phoenix for deployment.

Engagement scope: deployment-fit analysis, conformity-evidence framing for regulated verticals (financial services, healthcare, telecommunications, energy, transportation, critical infrastructure), and commercial structure for production deployment. Frontier AI lab engagement focuses on responsible scaling and federated AI infrastructure where hardware-rooted trust is required.

  • Frontier AI labs · Anthropic · OpenAI · Google DeepMind · Meta AI
  • Tier-one financial institutions · regulated healthcare · critical infrastructure
  • Defense industrial base · cleared commercial operators
commercial@zirulabs.com

// route 03 of 05

Sovereign and Allied Partners.

Defense authorities, sovereign investment entities, and allied national programs evaluating Phoenix for sovereign deployment or licensing.

Engagement scope: capability-gap mapping, sovereign-deployment posture, and structured framing for licensing and program-of-record alignment. Five Eyes, NATO, GCC, and select allied national authorities are within scope. Engagement proceeds through appropriate intergovernmental and industrial channels.

  • U.S. DoD · DARPA · NSA · Intelligence Community
  • NATO Allied Command Transformation · DIANA · STO
  • UK · Australia · Canada · Japan · ROK · Five Eyes · GCC
sovereign@zirulabs.com

// route 04 of 05

Policy, Regulatory, and Standards.

Standards bodies, regulatory agencies, and policy counterparties working on the AI trust and hardware attestation frameworks.

Engagement scope: technical input to standards drafting, policy coordination on harmonized frameworks, and substantive technical committee participation. Submissions are publicly available under Creative Commons Attribution 4.0 in the Research section.

  • FY2026 NDAA Section 1513 implementation framework (DoD)
  • EU AI Act Article 40 harmonized standards (CEN · CENELEC · ETSI)
  • NATO STANAG on AI trust (Allied Command Transformation · DIANA)
  • IEEE P3109 series · ISO/IEC JTC 1/SC 42
standards@zirulabs.com

// route 05 of 05

Investors.

Qualified institutional and strategic investors evaluating participation in the Ziru Labs capital program.

Engagement scope: data room access, technical and commercial diligence, and capital structure conversation. Engagement is restricted to accredited and qualified counterparties consistent with applicable securities regulation. Counterparty diligence and mutual NDA workflow are standardized.

  • Tier-one venture capital with deep-tech and defense-tech mandate
  • Strategic investors with platform-integration interest
  • Family-office and sovereign-investment entities with multi-decade horizon
investors@zirulabs.com

// nda pathway

Substantive technical engagement proceeds under mutual non-disclosure agreement.

Counterparties under active NDA receive scope-appropriate technical materials including the Technology Architecture reference document, the MWP Test Plan, the Threat Model Reference, the Phoenix Block Diagram, and engagement-specific materials. The mutual NDA pathway is opened by structured request through the appropriate route above.

Step 01

Initial structured request.

Email through the route appropriate to your counterparty type. Include institution, role, scope of inquiry, and counterparty type. Avoid speculative or unspecified inquiry.

Step 02

Counterparty diligence.

Counterparty type and standing are verified. Where appropriate, mutual NDA template is exchanged.

Step 03

Mutual NDA execution.

Mutual non-disclosure agreement is executed through standard counterparty workflow. Scope-specific materials are provisioned.

Step 04

Substantive engagement.

Technical and commercial conversation proceeds with appropriate Ziru Labs counterparts. Pilot framing follows where applicable.

Response-time standard: substantive structured inquiry receives a response within five business days.