Oxelone documentation

How Oxelone governs AI use across your machines and platforms, what the agent does to a machine, and how to script all of it.

Your first hour

Enroll a machine, connect a platform, write a policy and read your first alert.

One process per machine, and the five strategies it can run.

General, Plan and licence, Members and invitations, Roles and permissions and 5 more.

Every route an API key may call, with request and response samples.

97 operations · 10 resources

Browse by area

Get started

Your first hour What Oxelone does Concepts and glossary Rolling out A tour of the console

Inventory

Machines Accounts AI artifacts AI tools Connections

Activity

Interactions File events

Detections

Alerts and issues Triage an issue

Governance

Policies Engines Policy groups Runs Posture Halting enforcement

Connectors

How connectors work GitHub Microsoft 365 Google Workspace OpenAI Anthropic Coverage Matrix

The agent

The agent Deployment Capture strategies What each strategy alters Supported platforms Enrolling many machines Troubleshooting

Administration

General Plan and licence Members and invitations Roles and permissions Single sign-on Okta Microsoft Entra ID Google Workspace API keys

Data and records

Interaction logging Retention Log streaming Audit log

Your account

Signing in Notifications Tickets

Security and trust

What leaves a machine Storage and encryption Access inside Oxelone Legal

Before you install

Exactly what the agent changes on a machine

Every certificate store, proxy setting, registry key and settings file each strategy touches, read from the agent's own source when this site is built.

TLS interception

1 change

Network steering

2 changes

Tool hooks

1 change

Browser extension

Changes nothing

File inspection

Changes nothing

What each strategy alters