Developers

For the engineers behind a partner.

Everything is source-available. Read it, run it, extend it — before your client's security team asks, and without signing anything.

Resources

What is documented.

Architecture, APIs and SDKs are documented end to end. You can read the source, run a local instance and build connectors without a commercial commitment.
  • Documentation

    Architecture, concepts, deployment and integration guides.
  • GitHub

    Open source code for platform, inventory and engines.
  • Architecture

    Layer model, data plane and engine composition.
  • API Reference

    REST APIs for inventory, policy decisioning and access analysis.
  • Engine SDK

    Build custom engines or extend reconciliation, PDP and analysis.
  • Connector SDK

    Implement connectors for downstream systems and identity sources.
  • Deployment guide

    Reference topology and operational procedures.
  • Examples

    Sample products and integration patterns.
Developer Paths

Six things partner engineers actually do.

TaskWhat it means
Due diligenceRead the kernel and the products before your client's security team asks you to.
Run it locallyStand up the kernel and one product on a laptop with sample data.
Write a connectorBring a local HR system, directory or SaaS application into the inventory.
Author policiesExpress a client's access rules as policy the decision point evaluates.
Add an agent sourceTeach discovery where a new agent platform keeps its agents, tools and grants.
Deploy for a clientFollow the hardened profile: topology, baseline, logging, backup, upgrade.
API & SDK

REST APIs, policy decisions and connectors.

REST only. Inventory, findings, lifecycle cases and the policy decision point (AuthZen) are all plain HTTP. The connector SDK is how a partner brings a client's local systems — and local agent platforms — into the inventory.
Connectors

Connectors are where partners add the most value.

Every market has an HR system, a directory flavour or a government e-service nobody else integrates. A connector you write for one client works for all of yours — and stays yours.
Start building

Open code. Read it before you trust it.