Skip to content
ANCHOR OCCDocs
Talk With Anchor

Anchor OCC Documentation

Explore Anchor from the inside. Play a flow to watch the work move, or select any part of the platform to open its page.

Anchor architecturePeople use Web, which reaches Core over mutual TLS. Compass and Engine connect out to Core. Connect carries sessions from the browser to your systems. Core alone writes to the Vault and Evidence databases. Engine and Connect reach your systems; your SIEM reads Evidence.PRIVATE DATA · ONLY CORE CONNECTS443mTLSSession · WSSmTLS · outboundmTLS · outboundmTLSTLS 5432TLS 5432SSH · WinRM · LDAPS · TLSSSH · RDP · SQLRead-only viewsPeopleBrowser · CLI · APIWebConsole & APICoreAuthority · Policy · AuditCompassPosture scoringEngineCredential workConnectLive sessionsVaultEncrypted credentialsEvidenceAudit & historyYour systemsLinux · WindowsAD · PostgreSQLYour SIEMReads, read-only
Select a component once to see what it holds; select it again to open its page. Every Anchor host also runs a small agent that carries out host operations only after Core has signed them and an administrator approved them. Ports shown are the defaults.
Meet Anchor

What Anchor does, the idea behind it, and who uses it.

Start Here
Product Tour

Eight stops through a real console: onboarding, sessions, policies, Atlas, evidence, Compass and operations.

Take the Tour
How It Works

The components behind the console and how they connect.

Explore the Platform
Security & Insight

How credentials are protected, access is controlled, and outcomes are proven.

See What Matters
Deployment Options

One host or one per role, on-premises or in your cloud.

Compare Options
Is Anchor Right for You?

A short, honest checklist, and what is in this release.

Check the Fit

© 2026 Anchor OCC. All rights reserved.