INTEGRATIONS
Connect OZLILI to the systems you already use.
Evidence is most useful when it lives where decisions are made. OZLILI's integration architecture is built to bring the record into existing workflows — and the architecture is real, even where specific connectors are not yet shipped.
THE ARCHITECTURE
How integrations work underneath.
OZLILI's Runtime is provider-neutral by design. The integration surface is not a list of hardcoded connectors — it is an extensible architecture that new providers plug into without changing the core.
Provider-neutral Runtime
The Runtime orchestrates compute, models and gateways through an extensible registry. New providers — cloud, local, or third-party — register without changes to the Kernel.
Evidence as the integration point
The record is what connects. Integrations bring evidence in from external systems and carry OZLILI's evidence out — the foundation stays the same, the pipes change.
One governance model
Consent, access and audit apply to integrated data the same way they apply to native data. Connecting a tool does not create a parallel trust boundary.
DIRECTIONS
Where integrations are heading.
These are the integration directions the architecture supports. They are stated as directions, not as shipped connectors — the list will grow as specific integrations are completed.
HR and people platforms
DirectionBringing OZLILI's evidence layer into the hiring, performance and development tools organizations already use.
Learning and development
DirectionConnecting course completions, certifications and assessments to the evidence record so they count toward readiness.
Model and agent providers
In progressThe Runtime already registers cloud and local model providers through its gateway registry. A user-facing surface over this registry is in development.
Identity providers
DirectionSingle sign-on and directory integration for organizations managing access to OZLILI through their existing identity infrastructure.
The architecture is ready. The connectors are coming.
If you need a specific integration that is not listed here, tell us what your stack looks like. The architecture is designed to accept new providers without rebuilding the core — so the answer is often sooner than you expect.