Build on Alyria.
Cross-vendor agent governance at the endpoint, under your keys. Start with the platform overview, deploy a Beacon in the quickstart, then dive into the modules that govern, observe, and broker secrets across your fleet.
First steps
Platform overview
How Alyria's agent-governance platform fits together across Constellation, Beacon, Observatory, Lyra, Umbra, and Spectra, from the endpoint to the cloud.
Quickstart
Install a Beacon, connect your tenant, and ship your first Lyra policy in a few minutes. Illustrative commands for the Alyria agent-governance platform.
The module references
Beacon — the endpoint agent
The signed local daemon that inventories AI tooling and CVEs, enforces Lyra policy across three planes, and detects OS-level exfil a cloud gateway can't see.
Lyra — policy as code
One capability-brokered, information-flow-aware policy language governs which tools, models, data, and egress every agent may touch — authored once, enforced at the endpoint.
Umbra — secrets under your keys
Agent secrets and fleet data encrypted under a key in your KMS (BYOK), revocable and verifiable in your own CloudTrail. Client-held keys with an externally audited protocol are the roadmap.
Full API & reference docs
Complete CLI, MCP endpoint, and REST references — plus the Umbra client-crypto spec — are on the way. Today’s pages cover the architecture and getting started; commands shown are illustrative.