For internal IT teams

Keep people working. Move device work forward.

Delegate an investigation, configuration change, software rollout, maintenance or support task on authorized endpoints and servers. Mech or your own agent can carry out compatible work and leave checked results for your team.

Windows and Linux supported. macOS technical preview.

Create accountSee plans and pricing

A practical first step

Start with the work you need.

Made for: Internal IT departments and operators managing organizational Windows and Linux endpoints, servers or VMs.
Start with: One recurring task or change on an authorized device, with a clear outcome and agreed scope.

See OpalSpan at work

Watch the case move forward.

EXPLORE MECH · OPALSPANInteractive fictional example

OpalSpanFictional local example

Task context · Studio workstationReady

Focus: Studio workstationCase: Slow application startup

You control this conversationSaved permissions and scope apply

You

Alex is presenting. Investigate the slow startup without restarting, disconnecting or changing anything. Record the evidence and leave disruptive work for later.

Mech

Reasoning

I'll use **read-only checks** and keep Alex's session untouched. Any disruptive follow-up will stay deferred.

Try the example controls. Fictional device, conversation and Case; no real AI or device work is started.

INSIDE MECH · OPALSPANTask, checks and handback

Correct the Linux worker configuration, verify a successful task and keep the findings in the Case.

Source

Generated from the current shared Mech interface with fictional data and scripted responses. This is a simulation, not real device work or measured AI timing. Matching Linux worker desktop and phone generation, 13 October 2026.

01 / THE WORKFLOW

Investigate around the working day

An employee is presenting? Ask Mech for a quiet first pass, then review the findings when the meeting ends.

02 / THE WORKFLOW

Carry out the authorized task

Use the available command and file tools for compatible configuration, deployment, maintenance or support work, then check the result. Specific integrations and workloads still need validation.

03 / THE WORKFLOW

Keep the team in the picture

The employee, device, findings and next step stay together, so another technician can continue without a long handover.

A second example

From VPN complaint to a useful answer.

Mech follows the connection evidence, refreshes the stale DNS state and records the result for the team.

EXPLORE MECH · OPALSPANInteractive fictional example

OpalSpanFictional local example

Task context · Design laptopReady

Focus: Design laptopCase: Project share unavailable

You control this conversationSaved permissions and scope apply

You

The project share is unavailable over VPN. Compare network, DNS and tunnel evidence. Avoid disrupting working connectivity; fix and verify only if the cause is clear.

Mech

Reasoning

I'll separate **internet, DNS, tunnel and target-service** evidence before considering any network change.

execute on device Result received

Arguments

{
  "device": "Design laptop",
  "operation": "Read-only connectivity comparison"
}

Result

{
  "internet": "reachable",
  "public_dns": "working",
  "vpn_tunnel": "connected",
  "internal_dns": "stale server",
  "project_share": "name not resolved",
  "changes": "none"
}

The tunnel is healthy. Only the VPN adapter has a stale internal DNS server, so a full network reset would be unnecessary.

execute on device Result received

Arguments

{
  "device": "Design laptop",
  "operation": "Refresh VPN DNS registration and verify share"
}

Result

{
  "vpn_tunnel": "preserved",
  "internal_dns": "resolved",
  "project_share": "reachable",
  "internet": "unchanged"
}

add case note Result received

Arguments

{
  "case_id": "demo-case"
}

Result

{
  "saved": true,
  "status": "Resolved",
  "verification": "Share resolved through existing tunnel"
}

Try the example controls. Fictional device, conversation and Case; no real AI or device work is started.

INSIDE MECH · OPALSPANTask, checks and handback

Correct the VPNâ€™s assigned DNS, check internal access and keep the result without resetting the tunnel.

Source

Generated from the current shared Mech interface with fictional data and scripted responses. This is a simulation, not real device work or measured AI timing. VPN generation, 13 October 2026. The repair concerns assigned DNS, distinct from the stopped VPN service in the remote-support story.

Bring your next support case.

Create your account and workspace, choose a published plan and connect a Windows or Linux device. Start with the task you need done. You can set up and use OpalSpan yourself; help is optional.

Create accountPlans and pricing