Trust you can verify, and revoke.
Every security SaaS asks you to trust it with your data. Alyria is built so you can check instead: fleet data and audit records are encrypted under an envelope key we delete on request: so it can no longer be read. Enterprises can bring their own KMS key, revoke it, and watch our access die in their own CloudTrail. The claim is verifiable, not promised.
Free. Read-only. Remove it with one command.
- Under your keys
- an envelope key we delete, or your own KMS key you revoke
- One audit chain
- signed, tamper-evident, end to end
- Keys we never hold
- endpoint secrets sealed to device hardware keys
Encrypted by default. Cut us off, verifiably.
Trust, verifiable. Enterprises can bring their own KMS key: hold it, revoke it, and watch our access die in their own CloudTrail. By default, fleet data and the audit chain are encrypted under an envelope key we delete on account termination or request, and static blobs stored with us are encrypted under your key. That is a claim you can check, not one you take on faith.
Umbra: secrets under your keys, short-lived leases and safe hand-offs between agents. See the module →
Encrypted by default
Fleet data and the audit chain are encrypted under an envelope key we hold and delete on account termination or request, so they can no longer be read. Nothing to configure.
Bring your own key, for enterprise
Regulated and large fleets can bring their own KMS key (BYOK), or hold a key they never share with us (HYOK). Alyria operates only with the access you grant, and every use of the key is logged on your side.
Revoke and verify
Delete our envelope key, or revoke your own BYOK key, and our ability to decrypt ends. You can confirm it in your own CloudTrail or KMS audit log.
Keys we never hold
For endpoint secrets, Umbra seals each secret to the device's own hardware key (TPM or Secure Enclave), so the broker only ever moves ciphertext and Alyria never holds the key.
Custody claims, precisely
Data at rest in our systems is stored as ciphertext under data keys wrapped by a key you control and can revoke. Remove the grant and our ability to unwrap those keys ends, and the denial shows up in your own CloudTrail, in an account we cannot write to. At rest is doing real work in that sentence: while our pipeline processes an event, plaintext exists in memory on our side under your revocable grant. The claim covers stored data and revocation, not copies you exported to your own systems.
{
"eventSource": "kms.amazonaws.com",
"eventName": "Decrypt",
"userIdentity": { "arn": "arn:aws:sts::...:assumed-role/alyria-tenant-acme/..." },
"errorCode": "AccessDenied",
"errorMessage": "The ciphertext refers to a customer master key that does not
exist, does not exist in this region, or you are not allowed
to access."
}We walk through the revocation with you in a BYOK engagement, and you read the result in your logs rather than ours. Customer secrets and key leasing are separate: see Umbra.
Auditability
A custody claim is only as good as your ability to check it, which is why revocation shows up in your own logs. The rest is built to the same standard: the audit chain is signed, the endpoint agent is reproducible, and the client crypto carves out to open source as it ships.
Open, auditable client crypto
Umbra's client crypto and protocol carve out to open source (Apache/MPL) so anyone can verify the client-side crypto end to end when it ships, a claim you can read, not take on faith.
Open-core & licensing→One signed audit chain
Every policy decision and detection writes to a single append-only, cryptographically signed log: one source of truth spanning APG and ADR, legible to auditors and adversaries alike.
Tamper-evidence
The audit chain is hash-linked and signed, so any gap, reorder, or edit is detectable after the fact. Stream it to Observatory or straight into your own Elastic/Kibana SIEM.
Signed & reproducible builds
Beacon is built to ship signed, with reproducible builds, so you can confirm the binary on your fleet is the code that was reviewed.
OWASP ASI for what attackers do. NIST & ISO for how you govern it.
One signed audit chain covers both: the adversarial story and the compliance story from a single source of truth, so the two can never drift.
- ASI02Tool misusebrokered, policy-checked MCP calls
- ASI03Identity & privilegecapabilities scoped to the IdP identity
- ASI04Supply chainMCP posture and tool pinning
- ASI05Unexpected code executionuser-space runtime observation
- ASI07Inter-agent commsactivity recorded under your keys
- NIST AI RMFMap / Measure / Manage / Govern: the risk-management spine US enterprises align to.
- ISO/IEC 42001The AI management-system standard your auditors and procurement teams ask for by number.
- EU AI ActRisk-tiered obligations for AI systems: the regulatory anchor for governance buyers.
One chain, both audiences. The same signed log that proves an ASI05 code-execution block to a red team is the evidence that satisfies a 42001 audit: no second system, no reconciliation.
A paid tier, independent of your license.
The architecture is under-your-keys for everyone. Guarantees are a distinct commercial tier: the signed attestations, SLAs, and response commitments a regulated buyer needs, available with the hosted cloud today, and with self-hosted builds as they open up.
Talk to us about guarantees- Signed & reproducible builds
Verifiable artifacts across the fleet.
- SLA
Contractual uptime and support-response commitments.
- Warranty & indemnity
We stand behind the product commercially.
- SOC 2 + pen-test attestations
Independent attestations as they complete, shared under NDA.
- CVE response windows
Committed timelines to triage and patch.
The open-core playbook.
This is the licensing plan as the platform opens up, deliberately and never the reverse: open where it must be auditable, source-available where it protects the business, closed where it’s the commercial core.
Umbra client-side crypto & SDK
The parts that must be auditable for the under-your-keys claim to be credible will carve out to open source: client crypto, the A2A protocol, and the SDK, published as they ship.
- Verifiable by anyone
- The community on-ramp
- Published under owpz
The platform bulk
Constellation server, Beacon core, Lyra, and Spectra will ship source-available: free to run, read, and modify, converting to open source on a time delay.
- Source you can audit before you deploy
- Free except a competing hosted service
- Auto-converts to OSS over time
Observatory & the broker
The hosted Alyria Cloud console, the Umbra broker service, and enterprise features stay proprietary: the commercial core.
- Observatory / Alyria Cloud
- Umbra broker service
- SSO/SCIM, RBAC, fleet mgmt
Security guarantees (signed builds, SLA, warranty/indemnity, SOC 2 + pen-test attestations, CVE response windows) are a paid tier that sits independent of any license above.
Found something? Tell us.
We welcome coordinated disclosure and will work with you in good faith. Report vulnerabilities to our security team and see our published policy and contact key.
Please do not disclose publicly until we’ve confirmed a fix. We aim to acknowledge reports promptly and keep you updated through remediation.
See the model, then audit the claim.
Walk through key revocation and the audit chain with our team, or read how key custody, audit, and enforcement fit together.
Free. Read-only. Remove it with one command.