3AM documentation
Everything you need to install 3AM inside your network, license it, connect your tools and let it handle incidents with your approval.
3AM is the on-call engineer for systems you can't rewrite. It runs inside your network, watches the alerts you already have, proves the root cause against your live systems, and fixes it with one human approval. Every step it takes is written to a tamper-evident audit log.
Quickstart
From an empty server to 3AM watching your first incidents in under 30 minutes.
Requirements
Hardware, operating systems, network access and accounts to prepare.
Install
Linux, Windows Server, macOS (evaluation), Kubernetes, and air-gapped sites.
Connectors
Step-by-step setup for PagerDuty, Kubernetes, Prometheus and more.
How these docs are organised
| Section | What it covers |
|---|---|
| Get started | What 3AM does, how it works, what you need, and the fastest path to a running install |
| Install | Every way to install 3AM: one server, Kubernetes, or a site with no internet access |
| Licensing | How the offline licence works, how to get one, install it and renew it |
| Console | Signing in, the setup wizard, incidents, approvals, autonomy and the audit log |
| Connectors | Connecting each tool: what to create on its side, what to enter in 3AM, and how to check it works |
| Approvals | Slack, Symphony, PagerDuty, phone and e-mail approvals, escalation and quorum |
| How 3AM decides | Root causes, evidence, actions, shadow mode and the safety rails around every change |
| Operations | Health checks, logs, upgrades, backups, verifying the audit log, troubleshooting |
| Reference | Command line, configuration files, environment variables, API and network ports |
What you'll need from us
3AM is licensed per install. You need a licence file, and for most installs the install bundle, both from 3AM. The licensing guide explains how to request them. Nothing in 3AM needs to reach the internet or 3AM's servers to run.