Documentation
Run RootTrace your way, and read exactly how.
Every guide below is generated straight from the docs that ship in the repo. Self-hosted, air-gapped, hardened, and OEM integration, all in one place.
The repository checkout is not a customer deployment artifact. Verify the release before extracting its Compose files.
Open the verified install path →Understand
Overview
What RootTrace does, the shape of an incident inside it, and where AI stops.
Read →Change tracking
Link deploys and repositories so RootTrace can say what changed before it broke.
Read →Availability
Uptime, outage patterns, and percentages that say what they assume.
Read →Continuous profiling
Which function is eating the box, what it costs a month, and what the last deploy changed.
Read →Deploy
Quickstart
RootTrace on your own machine in about ten minutes: two containers, no TLS, no licence.
Read →Install
Install and verify RootTrace with the supported Docker Compose stack.
Read →Air-gapped install
Stand the whole stack up on a host with no internet access.
Read →Server configuration
Every environment variable the server container reads at startup.
Read →Instrument
Database queries
Which statements cost the most, with parameters never leaving the database.
Read →APM SDKs
Install the published SDKs and evaluate the source-only language clients.
Read →Collector
Install, configure, and operate the read-only diagnostics agent.
Read →Check reference
Every check the collector can run, and how to tune each one.
Read →APM wire protocol
The ingest contract every APM wrapper satisfies, field by field.
Read →APM read API
The endpoints the dashboard calls to read APM data back.
Read →Linux audit trail
auditd ingestion, the STIG rule set, and compliance evidence reports.
Read →Operate
Dashboards & explorer
Chart any metric RootTrace collects, then save the chart onto a dashboard.
Read →Telemetry volume
What your workspace sends, what drives it, and which service is responsible.
Read →Sizing & HA
Hardware tiers, replica counts, and the high-availability topology.
Read →Upgrades
Version scheme, upgrade path, and the one-way notes to plan for.
Read →Security
Security model
Zero-trust and least-privilege model, tenant isolation, key handling.
Read →Hardening guide
CIS-style baseline for an on-prem or air-gapped deployment.
Read →Security signals
Intrusion signals from the SDKs, and what they deliberately do not do.
Read →Disclosure policy
How to report a vulnerability, what we do next, and safe harbor.
Read →