MSSP and enterprise

Managed security teams can integrate ThreatMap intelligence through REST and MCP, subject to configured account scopes, plans, and provider licenses.

Current integration scope

Account-owned projects, monitors, API keys, BYOK, and intelligence APIs are implemented. Enterprise catalog limits and configurable features support broader usage; deployment and contract terms require operator confirmation.

Planned capabilities

Parent/customer tenant lifecycle APIs, white-label CNAME/branding, cross-tenant incident consoles, bulk rule deployment, and per-tenant credit allocation are not established implemented interfaces in this repository. Do not use former tenant API examples as a setup guide.

On-prem, air-gapped, multi-region residency, OEM pricing, and support/SLA commitments must be scoped and verified with the account/infrastructure team. Docker development configuration alone does not establish these offerings.

Start with REST/MCP setup and confirm enterprise requirements before designing a customer-facing managed workflow.

Opening page…
THREATMAP / APPEARANCE LAB

Theme Studio

Tune the whole catalog in real time. Saved on this device.

ThreatMap RubyAa 1,284
Color mode

Pick any color or enter an exact hex value. Presets keep your chosen accent; Reset restores Ruby.

Primary typeface

Geist Mono remains the secondary font for indicators and technical data.

Content density
Navigation layout
Explore eight presets
Your accent flows through the ThreatMap wordmark, globe, and interface. Semantic severity colors stay independent.