opal.dev valid

Opal Security

Opal is an AI-native access governance platform and the access control plane for every identity: employees, contractors, service accounts, non-human identities (NHIs), and AI agents. It decides every access request against your policy and enforces the decision in the identity and gateway infrastructure you already run.

For agents: AI-native access governance platform enforcing policy on human, non-human, and AI agent access across identity and gateway infrastructure; has docs and OpenAPI

access governanceidentity securityai agent accessmcp gatewaypolicy enforcement

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T17:03:00.119Z. Cached copy · Source on opal.dev

# Opal Security

> Opal is an AI-native access governance platform and the access control plane for every identity: employees, contractors, service accounts, non-human identities (NHIs), and AI agents. It decides every access request against your policy and enforces the decision in the identity and gateway infrastructure you already run.

Opal governs access across SaaS, cloud, databases, and on-premises infrastructure. It does not replace your identity provider. Opal sits on top of the one already in place (Okta, Entra ID, and others) and adds the decision and enforcement layer that traditional identity governance tools handle on a quarterly review cycle. It is built for engineer-led, cloud-native enterprises where security and engineering teams own access.

The platform has three parts:

- See: Discovery maps every identity, entitlement, and access path. OpalQuery lets teams ask who has access to what, and why, in plain English, including over-provisioned access, separation-of-duties conflicts, and privilege escalation paths.
- Encode: Access policy is written as versioned, reusable logic with OpalScript, either in code or described in plain language and generated by AI.
- Enforce: Paladin, Opal's AI decision engine, evaluates every request, approves what is safe, escalates only what needs a human with a stated reason, and revokes access when it is no longer needed. Grants are time-bound by default and produce audit evidence as a byproduct.

Opal Zero extends the platform to AI agents. Each agent is inventoried, attached to an owner and a declared purpose, and limited to the access its owner holds. Paladin decides each agent request at the moment it is made, and Gateway Sync writes the decision into the MCP gateway already in use as scoped, time-bound policy, with no second proxy in the path. Opal Labs research found that more than 96% of non-human identities have no recorded purpose, and only 10% of their access has been reviewed in the past year.

Customer results include an 88% reduction in standing access at Chronosphere, 86,000 time-bound access requests approved at Databricks, 150+ apps under governance at Superhuman, 5,353 Okta entitlements governed at Mercari, a 78% reduction in privileged access at Palo Alto Networks, 1,500+ developers on just-in-time access at Sophos, and access requests cut from 3 days to 5 minutes at Valon. Opal works with 100+ enterprise teams, including Databricks, Elastic, Grammarly, Cloudflare, Coreweave, Notion, Superhuman, Runway, Mercari, and Blend.

Opal Security is a Series B company that has raised $59 million from Greylock Partners, Battery Ventures, Box Group, SVCI, and Cambium Capital. It was named to Notable Capital's Rising in Cyber 2026 list. Opal is SOC 2 Type 2 certified and can be deployed in Opal's cloud, a customer's own VM, or Kubernetes, with US or EU hosting.

## Platform

- [Platform overview](https://www.opal.dev/platform): How Opal discovers access, encodes policy, and enforces decisions a
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=opal.dev · GET /v1/domain/opal.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for opal.dev:
1. POST https://agentwebmap.com/v1/sites/opal.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://opal.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/opal.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/opal.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.