Questions, answered.

AuthLN proves authentication and authorization: who was allowed in, what was allowed to act and on whose authority, on a record no one can rewrite. It brings together Factor Assurance (authority to enter, shipped), Agent Authority (authority to act, coming soon) and the Agent Access Review (available now).

AuthLN is the Auth Lineage Network. Lineage means any action can be traced back through every agent and hand-off to the person whose authority it ran on. The fan in the logo is that lineage: one person on the left, authority branching and narrowing to the right.

The decision layer in front of your identity provider. Every sign-in attempt resolves to Authorized, Denied or Walked away, and arrives in your SOC as one event with an outcome and an ID. It is shipped and in production.

No. It stands in front of Okta, Microsoft Entra ID, Google Workspace and JumpCloud, which stay exactly as they are. Your directory, your policy and your lifecycle are unchanged, and nothing is rerouted.

An attempt that saw the gate and left. Most systems only record a success or a failure. A walk-away still leaves a record, and a walk-away from an untrusted origin is itself a signal.

A device-bound passkey whose private key is generated inside the hardware security perimeter and cannot be exported; proximity-based authentication, which checks device GPS against network geolocation; and an ML-DSA-65-ES256 hybrid passkey with post-quantum signatures. All three are shipped.

Not yet. Agent Authority is coming soon. It is built so every agent action traces back to a person, within limits that only narrow, checked at a gate and recorded where the agent cannot reach. We are forming a small group of design partners.

A two-week review, available now, run from read-only exports with nothing installed. You get an inventory of the agents acting in your environment, a map of what each can reach and under whose authority, and a fix plan your people own.

Read-only exports from tools you already run. Never secrets: no passwords, API keys, tokens or connection strings, and no content such as prompts, message bodies or file contents. If anything is CUI or export-controlled, the review can run inside your GCC High or GovCloud tenant. We delete everything at the end and confirm it in writing.

Outside the thing being recorded. The record is written once and held where the system that acted cannot edit it, so it can be checked by your team, your auditors and your customers.

SOC 2 Type I completed; Type II examination underway, report expected Q3 2026.

Two issued U.S. patents: US 11,956,366 and US 12,118,550.