Skip to main content
View as MarkdownOpen in ChatGPTOpen in Claude

Identity Mesh — August 25, 2026

Release Date: August 25, 2026
Release Type: New Features

Overview​

This release lets Mesh collect from systems that live inside your own network — behind a firewall or VPN, with no public endpoint — without opening an inbound port.

  • On-prem connectors — run a small outbound-only agent on a host in your network, register it from the dashboard, and Mesh collects through it on the schedule you set.
  • Directory and internal REST sources — ingest users, groups, memberships and devices from a directory over LDAP/LDAPS, and data from internal REST APIs.
  • Protected with post-quantum cryptography — the agent's channel to Mesh uses hybrid post-quantum key exchange, and the connector software the agent runs is signed with a post-quantum signature and verified before it is loaded.

New features​

On-prem connectors​

Most connectors reach your source systems directly from the cloud. Systems inside your own network have not been reachable that way. You can now run the Axiad edge agent on a host in your environment and connect those systems to Mesh through it.

What you get:

  • Outbound-only connectivity. The agent makes only outbound connections to Mesh. You never open an inbound port, and your internal systems are never exposed to the internet.

  • Register from the dashboard, install on your host. Registering an agent issues a short-lived, one-time enrollment token and a ready-to-run command. Whoever operates the host runs that command as a container; the agent enrolls and comes online, and the dashboard shows it as Enrolled.

  • Central configuration, verified before activation. Add connectors to an agent from the dashboard. Configuration is pushed to the agent, and you can test the connection and see the result before you activate it, so a wrong credential or base URL surfaces during setup rather than on the first scheduled run.

  • Two source types. A directory over LDAP or LDAPS — users, groups, their memberships, and optionally devices and group policy objects — and internal REST APIs through the Universal REST connector. The connector tests each step of the connection as you configure it: name resolution, the secure connection, the handshake, the bind, whether the base DN is reachable, and whether incremental sync is available. Where the directory supports incremental queries, each run fetches only what changed.

  • Fleet health at a glance. Each registered agent reports its status, and Mesh detects an agent that has stopped reporting rather than leaving it to look healthy.

  • A full audit trail. Agent registration, configuration pushes, connection tests, and ingestion runs are recorded in the audit log.

  • Clean removal. Deregistering an agent removes the data sources configured against it and records the removal. Audit history is retained; an agent that is later re-registered is treated as a new instance rather than being joined to the old one's history.

Why it matters: identity and asset data that never leaves your network has been invisible to Mesh, which leaves a gap in exactly the systems that tend to hold the most sensitive accounts. Closing it does not require an inbound firewall rule or a public endpoint — only a host that can make outbound connections.

Post-quantum protection: the agent's connection to Mesh is TLS 1.3 with a hybrid post-quantum key exchange, so the session cannot be recovered later by an adversary who records traffic now and decrypts it once a quantum computer is available. The connector plugins the agent downloads and runs are signed with a post-quantum signature that the agent verifies before loading, so a tampered or substituted plugin will not run.

Known limitations:

  • Deletions at the source are not yet reflected in Mesh. When a user is deleted in a connected on-prem source, the collection run detects the deletion and records that it happened, but the user is not removed from Mesh — a full run does not remove them either. The account stays in your identity graph with any group access it had. This applies to both directory and REST sources, so do not rely on an on-prem connector to revoke access: continue to deprovision through your existing process as well.
  • Revoked group memberships are not always removed. For a directory source, a run removes memberships that no longer exist only when it can prove it read a group's complete member list; if that read was truncated or a member could not be resolved, the run adds and updates but removes nothing, and the revocation persists until a later run reads that group completely. For a REST source, removal depends on the connector definition declaring the member list complete, which the supplied definitions generally do not — so revocations are not removed.
  • Supported sources are a directory over LDAP/LDAPS and internal REST APIs. Database sources are not yet available.
  • Directory ingestion covers an on-premises directory reached over LDAP/LDAPS. A cloud-hosted directory is not ingested through an on-prem agent, and is not yet available through the cloud connector either.
  • Group policy objects are re-read in full on every directory run, because they carry no incremental marker. A run in which nothing changed therefore still reports a non-zero collected count equal to the number of policy objects in the domain, rather than zero. Treat the collected count on a directory run as "read", not "changed".
  • A directory run can also be labelled as an initial sync when it was actually incremental, so the run type shown for a directory connector is not yet a reliable indicator of whether a baseline has been taken.
  • Filtering rules are not yet centrally managed from Mesh; what an agent collects is determined by the connector configuration.

To get started, see On-prem connectors. The two halves of the setup are covered in Set up an on-prem connector for the Mesh administrator and Run the edge agent for whoever operates the host.