Endpoint AI observability

You wouldn’t hire someone and never check their work.

Your agents are digital labor. Origin finds them and puts their work on the record so you can understand what they saw, did, and changed.

Request Demo →

Use cases

Find every agent.

See which agents and MCP servers are running, where they run, and who uses them.

Review every trace.

Find activity that needs attention and see the evidence behind each finding.

Reconstruct any session.

Follow an unexpected action back to the request and context that produced it.

Inventory

Know what’s running.

Keep a current inventory of agents, models, and MCP servers across your endpoints, including local and unapproved tools.

Origin / Inventory

Endpoints · most recent first

6 shown3 unapproved8 MCP servers1 row recognized as the same device

Operating systemRegistered userSensorInstalled AI agentsMCP servers
Monitoring

Give an agent a computer and it gets to work.

Unlike a chat, an agent with a computer acts. It reads files, runs commands, and hands tasks to other agents, sometimes for hours. Origin captures that work and reconstructs it into a trace you can follow.

Origin / Session replay

k.osei · mbp-eng-209 · Claude Code

PromptMove the billing worker onto the new queue and retire the old one.

5h 20melapsed

5h 16m

Opened a pull request for review

Commands
Triage

No one can read every trace.

Your organization can produce thousands a day. Every one is reviewed for what’s worth a closer look, and a triage agent recommends where to start. Each finding takes you straight to the moment it happened.

Origin / Trace review

2,418 traces reviewed · last 24 hours

TriageTriage agent’s order

  1. 1:32 PMT12Worth a look

    Triage agentThe user asked at turn 1 for the changes to stay unstaged.

    T12bash -lc "sed -i 's/getToken(/refreshToken(/' src/auth/refreshToken.ts && npm test -- auth && git add -A"
    Open turn 12
  2. 11:48 AMT6Worth a look
  3. 7:40 AMT48Routine
  4. 2:51 PMT29Routine
Investigation

Follow the work inside the session.

Trace the session back to the request that started it. Inspect commands inside shell calls, see files as they changed, and check the work passed between agents. Read the context the model received to see why it acted.

Origin / Trace investigation

Fix intermittent 401s on staging · j.alvarez · mbp-eng-114

Turn 12of 41

Findings2
User3 prompts
Tools16 calls
Handoffs2
Contexttokens

One tool call ran three actions.

T12bash -lc "sed -i 's/getToken(/refreshToken(/' src/auth/refreshToken.ts && npm test -- auth && git add -A"
EditrefreshToken.tsTest212 passedGit2 files staged
Trace Investigations

See what we found in our own traces.

An agent bypassed an approval prompt. Another unlocked our demo environment and started a deployment during a sales call. Here’s how we traced each one.

Read the investigations →
Ask Origin

Put a question to the record.

Ask about one session or activity across your organization. Each answer points to the traces behind it, so you can follow up or build a report from the evidence.

Works in Origin, Claude, and Claude Code.

Connect Origin with Claude

Origin / Ask

Answers from the record

The user asked at turn 1 for the changes to stay unstaged. The session was compacted after turn 10 and the summary left that out. At turn 12 one shell call ran git add -A.

Answers cite their traces

  1. 1T1 · Prompt
  2. 2T10 · Compaction
  3. 3T12 · Shell call
Asked in Claude Code3 of 179 saved questions
How it works

A lightweight sensor on every endpoint.

Install Origin on managed macOS and Windows devices. It runs in the background and sends AI activity to your Origin tenant, encrypted in transit.

Capture at the source.

The sensor reads each AI tool’s own telemetry or uses application-level hooks. Nothing is intercepted on the network.

Connect cloud activity.

For supported cloud tools such as claude.ai and Microsoft 365 Copilot, Origin collects activity directly from the provider’s APIs.

Configure from the console.

Manage sensor settings centrally. Each sensor picks up changes on its next check-in, so there’s nothing to set up device by device.

Who We Are

Built by endpoint people.

Our team helped build endpoint tools at Elastic, SpecterOps, Tanium, and Microsoft, and includes the author of Evading EDR. Now we’re helping security teams understand and monitor the work AI agents do.

“The most technically differentiated Zone 3 vendor.” — SACR, Endpoint Control and Prevention report, 2026

You need agents
to understand your agents.

Your agents are already at work. Origin’s agents keep pace with them, so you can check their work the way you would anyone else’s.