FLEET-ENROLLED PROTECTION, SELF-SERVED RECOVERY

IT enrols the fleet. Nobody else signs up for anything.

An administrator deploys the agent with Group Policy or MDM, and that is the last setup step anyone performs. When an AI agent or a bad update wrecks someone’s work, the person it happened to opens their twin from a browser on any device — signed in with the same work account they use on the laptop — and picks up from before it happened.

Enrol the fleet. Find it yourself.

Setup neededEndpoint application control

Open this product's main page Products

Arivaran Aran protection

Setup needed

The diagram shows the mechanism, its current result, and the limit that remains in force.

Step 1 of 3Detect and record a local decision
Deterministic checks produce a disposition and policy action; today the endpoint records the result rather than blocking.
Step 2 of 3Contain and recover: planned
The plan is to coordinate containment with recovery in one platform; that is not available today.
Step 3 of 3Limits
Unknown programs are allowed with an alert by default, not blocked. Coordinated protection and recovery are planned. WORM applies only to the supported S3 storage with Object Lock turned on; other backends fail closed.

Mechanism

Deterministic checks produce a disposition and policy action; today the endpoint records the result rather than blocking.

Platform state

Today, endpoints observe and record; blocking programs in real time is deferred and will be platform-specific.

Limits

Unknown programs are allowed with an alert by default, not blocked. Coordinated protection and recovery are planned. WORM applies only to the supported S3 storage with Object Lock turned on; other backends fail closed.

Before you start

A released agent, a policy mode, baseline and publisher lists, a place to send audit records, and platform support.

Evidence reviewed 2026-08-26

Aran products

Overview
Arivaran Aran protection — Setup needed
The shipped local classifier combines baseline, publisher, and behavior-derived evidence into an auditable disposition without an LLM or external analysis service.
1. Mechanism
  Detect and record a local decision
  Deterministic checks produce a disposition and policy action; today the endpoint records the result rather than blocking.
2. Current outcome
  Contain and recover: planned
  The plan is to coordinate containment with recovery in one platform; that is not available today.
3. Limits
  Limits
  Unknown programs are allowed with an alert by default, not blocked. Coordinated protection and recovery are planned. WORM applies only to the supported S3 storage with Object Lock turned on; other backends fail closed.
Platform state
Today, endpoints observe and record; blocking programs in real time is deferred and will be platform-specific.
Before you start
A released agent, a policy mode, baseline and publisher lists, a place to send audit records, and platform support.
Arivaran Keybound — Unavailable
The intended clients make hardware use, software fallback, package identity, signing, and provider compatibility separately reviewable.
1. Mechanism
  Custody-aware signing request
  A client requests a bounded operation and reports whether the key remained hardware-protected or used an approved fallback path.
2. Current outcome
  Explicit credential provenance
  You can see what Keybound will be, but unpublished clients have no install action.
3. Limits
  Limits
  Hardware-backed custody is not universal, and no install command is shown until each SDK meets its release requirements.
Platform state
Hardware and fallback behavior vary by platform; no language registry or signed client package is claimed available here.
Before you start
Still needed: an approved product name, published packages, signing, registry listing, a hardware support matrix, a fallback policy, and tested revocation.
Aran provider verification — Unavailable
The intended verifier or gateway checks a bounded proof and policy context before an upstream service accepts the request.
1. Mechanism
  Proof before provider action
  A gateway validates the request envelope, freshness, identity binding, and configured policy, then returns an explicit accept or reject decision.
2. Current outcome
  A reviewable server integration
  Providers can review the planned design without assuming our verification code is a supported service yet.
3. Limits
  Limits
  This is not released yet, so there is no endpoint, credential, gateway deployment, or compliance claim here.
Platform state
No gateway image, hosted verifier, provider list, or SLA is offered until it is packaged and validated.
Before you start
Still needed: a published verification spec, trust roots, a replay policy, a gateway package, provider integration tests, and proven operations.
Aran Cage — Planned
Copy-on-write copies, secret exclusion, the Cage boundary, and reviewed merge-back are separate layers of the isolation workflow.
1. Mechanism
  Copy, confine, review
  The Cage builds a lightweight working copy, keeps excluded secrets out, runs inside the platform's isolation boundary, and lists changed files for approval.
2. Current outcome
  Disposable work with selective return
  Creating the copy and merging changes back have shipped; the cross-platform isolation boundary is still in beta with its own permission limits.
3. Limits
  Limits
  A disposable twin reduces blast radius but does not imply universal kernel enforcement, entitlement, or platform parity.
Platform state
Copying and confinement work differently on Linux, macOS, and Windows; one platform's isolation does not imply another's.
Before you start
Still needed: a released Cage package, platform permission or a fallback, a secret policy, the isolation boundary, a review screen, and tested cleanup.
Aran MCP and editor integrations — Unavailable
The planned MCP and editor integrations use Aran's policy and records, each with its own sign-in, signing, and distribution checks.
1. Mechanism
  Tool-to-policy request
  A developer tool sends an allowed request, receives a bounded trust result, and links the user to the matching Aran record.
2. Current outcome
  Protection context in the workflow
  Integration intent is visible without presenting an unpublished server or extension as available.
3. Limits
  Limits
  This is not released yet, so there is no server URL, install command, token, or marketplace button.
Platform state
No MCP server, editor extension, or marketplace listing is released until its package and compatibility are validated.
Before you start
Still needed: published protocol and extension packages, sign-in scopes, signing, a compatibility matrix, and tested revocation and uninstall.

Self-service that begins with “create an account” is not self-service — that is the step which quietly turns it back into a ticket, because the account does not exist, or the password is stale, or the first thing the user meets during an incident is an enrolment form. Aran starts from the device instead.

IT enrols the fleet
Group Policy or MDM pushes the agent. The endpoint enrols itself and takes hardware-custodied identity on every platform — TPM on Windows and Linux, the Secure Enclave on Mac. The person at the laptop is never involved and needs no account.
On the machine itself, not even that
The sign-in above is only needed when the user is somewhere else. Standing at their own enrolled machine they browse their own twin with no sign-in at all: the agent answers “is this your twin?” from the identity it enrolled with, never from anything the request claims, and serves that one endpoint’s own catalogue, read-only, on an internal listener that is never published to the network.
Bytes back need a person, on purpose
An enrolled device writes backups and reads its own catalogue. It cannot pull data back out — that refusal is what stops a compromised laptop from exfiltrating your backup history using nothing but the machine’s own identity. Restoring is human-authenticated, and in an enterprise that is the sign-in your people already use every morning.

Two layers. Take one, or take both.

They answer different failures, which is why the honest recommendation is both. The local twin decides how much an agent can reach. The cloud twin decides what happens when something gets through anyway — or when the machine simply stops existing.

Use your laptop

Work the way you always have. When an agent wrecks a morning’s work — or the laptop is stolen, bricked, or sitting on the bench — your cloud twin is a browser away, backed up continuously to cloud or to your own data centre and immutable for its retention window.

Or don’t

Run the agent on a local twin instead: a copy-on-write clone of the machine you already use — same desktop, same applications, same configuration, same files — so nothing has to be rebuilt to work in it. Whatever the agent breaks, it breaks in the copy. Keep the files worth keeping; throw the rest away.

Either way, the cloud twin is still there. A browser away.

IT enrols the fleet. Nobody else signs up for anything.

Arivaran Aran protection

Mechanism

Platform state

Limits

Nobody signs up for anything.