Skip to main content

ThreatMapper Web vs ThreatMapper Docker

This page is the canonical capability reference. ThreatMapper Web is the public browser-native ATT&CK/CTI workspace. ThreatMapper Docker is the full self-hosted AI-assisted platform.

FeatureThreatMapper WebThreatMapper DockerNotes
ATT&CK matrix exploration and technique searchSupportedSupportedCounts depend on selected domain and ingested release
Manual layer creationBrowser-localSupportedWeb state is stored in the browser; Docker also supports server workflows
Group profile overlay and group-vs-group comparisonSupportedSupportedSimilarity is an investigation lead, not attribution proof
Coverage gap analysis and detection guidanceSupportedSupportedTechnique details include linked detection/hunting context
Detection backlog exportBrowser-generatedSupportedExport engines and fields differ by mode
Investigation workspacesBrowser-localPostgreSQL-backedWeb workspaces remain in browser storage; Docker stores private analyses
Sample workflowsSupportedPlannedWeb includes four functional starting layers
AI report extractionNot supportedDocker-onlyUses the operator-configured LLM provider
PDF/DOCX/TXT ingestionNot supportedDocker-onlyPrivate backend workflow
Claude/OpenAI/Gemini providersNot supportedDocker-onlyProvider availability depends on operator configuration
Private report libraryNot supportedPostgreSQL-backedRequires self-hosted deployment
API accessNot supportedDocker-onlyProtect the API with access control
Report exportsBrowser-generated / partialBackend PDF generationCapabilities differ by deployment mode
ATT&CK sync jobsBuild-time updateDocker-onlyDocker uses scheduled Celery jobs
Authentication/RBACNot applicablePartialTrusted-header roles require a correctly configured authenticating reverse proxy
Production hardeningNot applicableRequires self-hosted deploymentUse TLS, access control, restricted networks, backups, retention, and secrets management

ThreatMapper is suitable for local labs, private analyst workstations, internal CTI workflows, and controlled self-hosted deployments. Internet-facing Docker deployments require additional access control and hardening.