ARIVARAN TWIN · PLANNED RECOVERY DIRECTION

Twin is not a backup. It is designed as a live endpoint, ready when you need it.

Planned direction: open a live, browser-accessible digital twin when the original endpoint is unavailable. Available today: authenticated, role- and organization-scoped browsing of a completed snapshot, with single-file download. Where policy grants it, the assigned owner of an endpoint can browse their own stored files and download one at a time from a clean browser. Booting a full Twin, restoring to another endpoint, and an owner restoring files to the original endpoint are not available yet.

Planned outcome: no restore queue. No administrator wait.

Setup neededEndpoint and server recovery

Open this product's main page Products

Twin for endpoints and servers

Setup needed

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

Step 1 of 3Catalog plus immutable block identity
The browser resolves a stored file through its catalog and verified block references without treating the source device as the recovery path.
Step 2 of 3Browser file recovery
Authorized users can inspect stored snapshots and recover a selected file when the required snapshot and blocks exist.
Step 3 of 3Limits
File browse and download do not prove a bootable Twin, in-place restore, standby, or migration outcome.

Mechanism

The browser resolves a stored file through its catalog and verified block references without treating the source device as the recovery path.

Platform state

Agent, filesystem, and restore coverage vary by platform and must be checked before deployment.

Limits

File browse and download do not prove a bootable Twin, in-place restore, standby, or migration outcome.

Before you start

A completed enrollment, a finished snapshot, a stored catalog and blocks, and authorization for the signed-in user.

Evidence reviewed 2026-08-26

Twin products

Overview
Twin for endpoints and servers — Setup needed
A stored catalog and content-addressed blocks keep file browse and download separate from live endpoint reachability.
1. Mechanism
  Catalog plus immutable block identity
  The browser resolves a stored file through its catalog and verified block references without treating the source device as the recovery path.
2. Current outcome
  Browser file recovery
  Authorized users can inspect stored snapshots and recover a selected file when the required snapshot and blocks exist.
3. Limits
  Limits
  File browse and download do not prove a bootable Twin, in-place restore, standby, or migration outcome.
Platform state
Agent, filesystem, and restore coverage vary by platform and must be checked before deployment.
Before you start
A completed enrollment, a finished snapshot, a stored catalog and blocks, and authorization for the signed-in user.
Twin for Microsoft 365 — Unavailable
The beta service follows Graph delta links for incremental capture and writes supported item restores back through Graph.
1. Mechanism
  Delta-query capture
  Versioned Microsoft Graph paging records changed Exchange and OneDrive items; optional shared dedup has to be turned on in configuration.
2. Current outcome
  Item-level cloud recovery
  Exchange and OneDrive capture is built and tested, and restoring items back to Microsoft 365 is implemented.
3. Limits
  Limits
  Do not infer SharePoint, Teams, or universally enabled cross-workload dedup from the current beta.
Platform state
Cloud-to-cloud beta for Exchange Online and OneDrive; SharePoint and Teams are not current engines.
Before you start
Tenant OAuth consent, required Graph permissions, deployment-specific service authentication, and egress to Microsoft Graph.
Twin for Kubernetes — Planned
The beta Kubernetes agent separates manifest export, CSI-backed PVC data, and the Watch API journal instead of presenting them as one uniform guarantee.
1. Mechanism
  Layered cluster record
  Resource bundles form layer one, PVC blocks use the shared storage pipeline when CSI snapshots are available, and Watch events form a change journal on higher tiers.
2. Current outcome
  Workload-aware backup evidence
  Each layer can expose its own readiness and recovery boundary for the target cluster.
3. Limits
  Limits
  The CSI path is crash-consistent and still maturing; the change journal depends on your tier.
Platform state
Kubernetes beta; CSI capability and storage behavior depend on the cluster and provider.
Before you start
Helm deployment, cluster permissions, compatible VolumeSnapshot support for PVC capture, storage connectivity, and the required journal tier.
Twin for VMware vSphere — Planned
The beta proxy reads changed virtual-disk blocks and parses supported filesystems from raw bytes to build the familiar file catalog.
1. Mechanism
  No-mount filesystem parsing
  A vSphere-facing proxy reads snapshot data through the management path, then walks partition and filesystem structures without an in-guest agent.
2. Current outcome
  VM file browse on the Twin model
  Tests of the parser, change tracking (CBT), proxy, and catalog back the design, without claiming an independently measured speed.
3. Limits
  Limits
  Documented parse-time and cost figures are estimates, not marketing benchmarks; bootable/live VM Twin remains separate.
Platform state
VMware/vSphere beta through an external proxy; transport and datastore modes remain configuration-specific.
Before you start
Supported vSphere APIs, proxy deployment, snapshot and CBT access, datastore reachability, and a validated restore scope.
Twin for Nutanix AHV — Planned
The beta Nutanix proxy connects through Prism, reads snapshot data, and feeds supported virtual-disk content into the same no-mount catalog path.
1. Mechanism
  Prism-to-catalog proxy
  An external proxy keeps AHV credentials and snapshot access at the management boundary while raw disk parsers produce the catalog.
2. Current outcome
  AHV-aware stored recovery data
  Tests of the Prism client, changed regions, backup engine, and parser back the beta.
3. Limits
  Limits
  This panel does not claim universal AHV compatibility, measured recovery speed, or a booted replacement VM.
Platform state
Nutanix AHV beta through an external proxy; support is not inferred for every Prism or storage configuration.
Before you start
A supported Prism endpoint, scoped proxy credentials, snapshot access, storage reachability, and a validated recovery configuration.

Verified path

From protected snapshot to one downloaded file.

The original endpoint can be offline because browsing and file reassembly use the stored catalog and content blocks. Access still depends on a valid identity, role, tenant, and organization scope.

Twin browser download journey

Available with role and scope

Three supported beats end at a single-file browser download. No in-place restore is depicted.

Step 1/3Store a recovery point
An enrolled endpoint must complete a snapshot with a persisted file catalog.
Step 2/3Browse the snapshot
A signed-in role with file browse permission can open the stored catalog inside its tenant and organization scope.
Step 3/3Download one file
A role with file download permission can reassemble one stored file in the browser.

Outcome matrix

What works now, and what does not.

Availability belongs to each outcome, not to Twin as one broad promise. Every available row carries its access and data conditions.

Arivaran Twin public recovery outcome availability
Outcome	Status	Condition
See only assigned endpoints	Available	Available for an assigned user with a trusted sign-in and a non-admin role that policy grants recovery. They can open, browse, and download from only the endpoints assigned to them; another user's endpoint is refused.
Browse stored files	Available	Available after a completed snapshot with a persisted catalog, for roles with file browse permission inside their tenant and organization scope.
Download one file	Available	Available for roles with file download permission when the snapshot and stored content blocks are accessible. Folder and whole-snapshot export are not included.
Restore to the original endpoint	Unavailable	Not part of owner self-service. An administrator with restore permission can send a restore from the dashboard to the original endpoint while it is enrolled and online. That administrator path is in beta: the files land in a new restore folder, never over the files in use.
Original endpoint lost or offline	Available	Stored browse and single-file download remain available under the same access conditions. This does not make in-place restore possible.
Identity compromised	Unavailable	Unavailable as a bypass. Recover or revoke the identity through the configured identity provider or an authorized administrator first.
Restore to another endpoint	Unavailable	Unavailable. A different target is not dispatched by the current dashboard restore request.
Boot a full Twin	Planned	Planned. No bootable endpoint replica is marketed as generally available.
Owner policy and audit proof	Available	Available for file browse and single-file download. Each allowed download and each refused request is kept as a durable record of who asked, for which endpoint, and the decision, without file content.

Recovery boundaries

A lost endpoint is not a compromised identity.

Twin can recover stored data only after identity and authorization succeed. Losing a device does not weaken those checks.

Available

Endpoint lost or offline

Use scoped snapshot browse and single-file download from a clean browser. The stored-data path does not contact the original endpoint.

Unavailable

Identity recovery comes first

Twin does not bypass sign-in, revocation, or administrator controls. Recover the identity before requesting data.

Not yet available

Restore and boot stay out of frame

Restore to another endpoint and full boot are not available yet. Owner self-service is limited to browsing files and downloading one file at a time from an assigned endpoint.