ZTA Labs

Open ecosystem for institutional investors

Designed for an open institutional ecosystem.

ZTA Labs is designed for asset managers and asset owners that already have established data, infrastructure, applications, security controls, and service relationships. The open, deployable reference architecture is designed to fit that environment rather than force a rip-and-replace decision.

How we think about partners

The architecture should integrate with the institution’s operating environment.

ZTA works across an open partner ecosystem that can include enterprise data platforms, open-source software, open-weight model providers, infrastructure providers, identity and security systems, workflow platforms, and implementation partners.

Partner strategy follows the client’s environment and governance requirements, not the other way around.

01

Enterprise data & content

Platforms that hold or govern institutional evidence, entitlements, and metadata.

02

Inference & model operations

Serving, routing, evaluation, and orchestration capabilities for approved open-weight models.

03

Infrastructure

NVIDIA infrastructure and the software layers required to deploy client-controlled AI environments.

04

Identity & security

Institutional identity, access control, audit, secrets, encryption, and operating controls.

05

Workflow systems

Existing research, diligence, committee, or monitoring systems that should remain part of the user workflow.

06

Implementation partners

System integrators and specialist partners that can help the institution operate and extend the environment over time.

Certified Consulting Partner Program

Build on the platform, not inside it.

Consulting firms can implement ZTA for their clients under a Certified Partner Development License, with the boundary between our software and your work product written down rather than assumed.

01
What certification grants
A development license to build client-specific extensions, run a partner lab, and implement ZTA in client environments without receiving or modifying the proprietary core.
02
What you keep
Your independent consulting methods and your work product remain yours. Certification grants no ownership interest in ZTA software and no redistribution right.
03
How licensing works
Every production customer holds a direct ZTA entitlement, regardless of which partner performs the implementation. There is no resale tier and no ambiguity about who is licensed.

The extension interfaces you build against are published and versioned. Your work sits on a stable contract rather than inside software we may change.

Data and content providers

Licensed data stays inside the client’s walled garden.

ZTA is deployed inside infrastructure the institution controls. Your data is consumed by your licensed client, in their environment, under the contract you hold with them.

What the architecture guarantees

  • Content is retrieved into the client’s own environment, not a shared ZTA tenant
  • Entitlement-aware, read-only access patterns
  • No pooling of client content across environments
  • Provenance and lineage retained on every piece of evidence

What we ask of you

  • The licence terms that apply to each source or series
  • Any redistribution and display restrictions
  • A technical contact for connector certification

You provide data lineage. We provide decision lineage. You provide entitlement checks. We provide AI evidence entitlements.

Live connectors

Rights enforcement was built before it was required.

The first live connectors read public sources: SEC EDGAR and FRED/ALFRED. Nobody would have challenged how we handled either. We enforce per-source rights on them anyway, because the same machinery has to hold when the source is licensed.

Live

SEC EDGAR

Filing retrieval, with the retrieved document carried as evidence rather than summarised away from its source.

Live

FRED and ALFRED

Series retrieval including vintage data, with rights enforced per series rather than per provider.

Published contract

Any new source

New connectors are certified against a published contract with declared rights, bounded retrieval, and evidence that can be replayed.

Operating principle

Open-source first, clear boundaries, client control.

ZTA defines the operating boundaries required for governance and transferability while leaving room for the institution’s preferred tooling choices. Components remain replaceable where the substitution does not compromise control, auditability, security, or portability.

What is fixed

  • Read-only, entitlement-aware access patterns
  • Risk-tiered policy routing
  • Independent evaluation and human approval for consequential actions
  • Portable architecture and documentation

What can vary

  • Inference engine and serving stack
  • Selected approved open-weight models
  • Open-source software components
  • Adjacent workflow integrations
  • Infrastructure choices
  • Implementation and support arrangements