Deepfence ThreatMapper
threatmapper.org
- Free plan
- Windows
- Linux
- Web
- API
- Self-hosted
What Deepfence ThreatMapper is
Deepfence ThreatMapper is a free, self-hosted security tool that hunts for threats in production environments and ranks them by exploit risk. It discovers pods, containers, applications, and infrastructure, then maps topology and attack surface. ThreatMapper generates runtime software bills of materials for workloads and operating systems and checks them against multiple vulnerability feeds. It can detect exposed keys, tokens, and passwords in containers and host filesystems, and assess infrastructure settings against CIS, PCI-DSS, HIPAA, and other compliance benchmarks. Its Threat Graph connects vulnerabilities, secrets, and compliance findings with network flows, security groups, and live status. A standalone management console runs in containers on a Docker host or a dedicated Kubernetes cluster, providing HTTPS administration and API automation. One console can manage different workload types across on-premise and cloud deployments. Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic, and AWS S3; image-build scanning supports CircleCI, Jenkins, and GitLab. Windows Server support is experimental and not suitable for production use. Sensors require Linux kernel 4.4 or newer, among other listed requirements.
Who it suits
ThreatMapper may suit security teams managing cloud and on-premise workloads that want vulnerability scanning, exposed-secret detection, and compliance checks in a self-hosted setup. It is not suited to production use on Windows Server.
Good to know, and what to watch
- Ranks threats by exploit risk.
- Generates runtime SBOMs and checks multiple vulnerability feeds.
- Threat Graph correlates findings with network context.
- One console manages on-premise and cloud deployments.
- Free plan has no stated limits.
- Windows Server support is experimental, not production-ready.
- Sensors require Linux kernel 4.4 or newer.
- Sensor access to console port 443 is required.
Plans
Every plan and priceThreatMapper
Free plan
Getting started
- Open the ThreatMapper documentation website
- Run the management console as containers on a Docker host or dedicated Kubernetes cluster
- Deploy sensor agents with a console URL and API key
- Provide sensors with at least 0.2 CPU cores, 200 MB to 1 GB RAM, Linux kernel 4.4 or newer, and console port 443 access
- Connect documented integrations or CI/CD image-scanning systems
Limits to check
The ThreatMapper plan is free at no cost with no limits or hidden features. Windows Server support is experimental and not suitable for production use.
The Club's review
Deepfence ThreatMapper is a free, self-hosted platform for finding and ranking security risk across containers, cloud infrastructure, and on-premise systems. It suits teams operating Linux-heavy, mixed environments that want discovery, scanning, and prioritization in one console. The broad scope is valuable, but running the console and avoiding experimental Windows Server deployment are important practical constraints.
Overview
ThreatMapper discovers pods, containers, applications, and infrastructure, mapping topology and attack surface while ranking threats by exploit risk. Its Threat Graph connects vulnerabilities, exposed secrets, and compliance findings to live and recent network flows, security groups, and current status. That context gives security teams a way to concentrate on issues with meaningful exposure instead of treating every alert alike.
The management console is self-hosted in containers on a Docker host or dedicated Kubernetes cluster. It provides HTTPS administration and API automation, and one console can manage multiple workload types across cloud and on-premise deployments. This is a strong fit for organizations that need control over deployment and data, but it also makes console operation part of the security team's workload.
Key features
Discovery, SBOMs, and secrets
Runtime SBOM generation covers running pods, containers, serverless applications, applications, and operating systems, with matching against multiple vulnerability feeds. ThreatMapper also scans images and registries, and detects exposed keys, tokens, and passwords in containers and host filesystems. These capabilities bring supply-chain and runtime findings into the same workflow rather than limiting analysis to build-time images.
Context and compliance
Infrastructure configuration checks cover CIS, PCI-DSS, HIPAA, and other benchmarks. Threat Graph correlation adds network and security-group context to those results, which can improve remediation order when an estate contains many theoretical vulnerabilities. Runtime protection and Kubernetes security are included alongside vulnerability and SBOM functions.
Operations and integrations
Image-build scanning supports CircleCI, Jenkins, and GitLab. Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic, and AWS S3, giving teams routes for notification, ticketing, logging, and export. Sensor agents communicate with the console over TLS using a URL and API key. Sensors require 0.2 CPU cores, 200 MB to 1 GB of RAM, Linux kernel 4.4 or newer, and access to console port 443.
Cloud Scanner tasks run locally through Terraform modules, typically use read-only cloud API access, and do not listen for remote connections or take control. Windows Server support is experimental and is not suitable for production, so Windows-first estates should look elsewhere.
Pricing
The ThreatMapper plan costs free, with no limits and no hidden features. It includes image scanning, runtime protection, Kubernetes security, registry scanning, and SBOM generation. Because the project is free under the Apache 2 license, it is well suited to teams that can provide their own infrastructure and operational support. The trade-off is the self-hosted deployment: there is no paid hosted tier described here that transfers console management to the vendor.
Platforms
ThreatMapper provides an API, web console, Linux sensor and self-hosted deployment model, with Windows listed but Windows Server support remaining experimental. Its single-console design spans cloud and on-premise workloads, while sensor requirements make Linux the dependable production foundation.
Who it's for
Choose ThreatMapper if you run Kubernetes, containers, serverless workloads, or mixed infrastructure and need vulnerability, secret, compliance, and runtime context together. It is particularly suitable for security and platform teams able to operate Docker or Kubernetes-hosted management software and maintain Linux-based sensors. It is less suitable for organizations seeking a managed SaaS service or production-grade Windows Server coverage.
Pros and cons
- Pro: One console combines discovery, runtime SBOMs, vulnerability feeds, secret detection, compliance checks, and threat correlation.
- Pro: A single deployment can cover multiple workload types across cloud and on-premise environments.
- Pro: Unlimited free licensing removes seat and usage-cost barriers for self-hosting teams.
- Con: The console must be deployed and operated on Docker or Kubernetes, adding infrastructure responsibility.
- Con: Windows Server support is experimental and unsuitable for production use.
- Con: Sensors need specific Linux kernel, memory, CPU, and port access, which may complicate constrained hosts.
Alternatives
For a broader set of Container Security Software, compare the directory's category list. Pick Qualys External Attack Surface Management if you want a freemium platform with a 30-day no-cost CSAM and EASM period rather than an unlimited free self-hosted console.
Docker Desktop is the better choice when your priority is a developer desktop bundle covering Docker Engine, Kubernetes, Docker Hub, Docker Scout, and Docker Debug; its Personal plan is free, while Pro costs $9 a month. Choose Snyk Open Source for hosted software-composition analysis: its free plan covers five projects, and Team costs $25 a month.
Kubescape suits teams wanting a free Apache 2.0 Kubernetes CLI and operator in a self-hosted model. Choose RapidFort for curated near-zero-CVE images: its free plan supplies five images from a limited catalog with daily rebuilding and patching. Dockle is a free open-source container image linter, while Grype is a free Apache-2.0 vulnerability scanner. KubeArmor is a free open-source runtime-security project whose workload and platform support varies by its support matrix.
Verdict
ThreatMapper is a strong choice for security and platform teams that want broad, risk-ranked coverage of Linux-based containers and mixed cloud/on-premise workloads without license fees. Its main reason to choose it is the combination of discovery, SBOM and vulnerability scanning, secret and compliance checks, and live threat context in one unlimited free console. Look elsewhere if you need a managed service, a simpler desktop-focused tool, or production-ready Windows Server protection.
The verdict
ThreatMapper combines workload discovery, vulnerability and secret detection, compliance checks, and contextual threat correlation in a self-hosted console. Review sensor requirements and the experimental Windows Server status when planning a deployment.
Questions people ask
Is Deepfence ThreatMapper free?
Yes. The ThreatMapper plan costs nothing and has no limits or hidden features.
Where can ThreatMapper run?
It supports API, Linux, self-hosted, web, and Windows environments. Windows Server support is experimental and not suitable for production use.
What does ThreatMapper scan?
It scans workloads and infrastructure, including pods, containers, applications, serverless apps, operating systems, images, registries, and runtime environments.
Does it generate SBOMs?
Yes. It generates runtime SBOMs and matches them against multiple vulnerability feeds.
Which integrations are documented?
Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic, and AWS S3. Image-build scanning supports CircleCI, Jenkins, and GitLab.
How are sensor agents secured?
Sensor agents communicate with the management console over TLS using a URL and API key.
What the maker publishes
- CI/CD
- Image-build scanning supports CircleCI, Jenkins and GitLab. source
- Cloud scanning
- Cloud Scanner tasks run locally through Terraform modules, use typically read-only cloud API access and do not listen for remote connections or control. source
- Compliance
- It evaluates infrastructure configuration against CIS, PCI-DSS, HIPAA and other compliance benchmarks. source
- Deployment scope
- A single console can manage multiple workload types and on-premise and cloud deployments simultaneously. source
- Integrations
- Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic and AWS S3. source
- License and support
- The ThreatMapper project is offered under the Apache 2 license, with GitHub issues and a Deepfence Community Slack channel available for support. source
- Management console
- The standalone management console runs as containers on a Docker host or dedicated Kubernetes cluster and exposes HTTPS administration and API automation. source
- Purpose
- ThreatMapper hunts for hidden threats in production platforms and ranks them by risk of exploit. source
- SBOM vulnerability scanning
- It generates runtime SBOMs for running pods, containers, serverless apps, applications and operating systems and matches them against multiple vulnerability feeds. source
- Secret detection
- It detects exposed keys, tokens and passwords in containers and host filesystems. source
- Sensor requirements
- Sensor requirements include 0.2 CPU cores, 200 MB to 1 GB RAM, Linux kernel version 4.4 or newer and access to console port 443. source
- Sensor security
- Sensor agents communicate with the management console over TLS using a URL and API key. source
- Threat Graph
- The Threat Graph correlates vulnerabilities, secrets and compliance issues with live and recent network flows, security groups and live status. source
- Windows support
- Windows Server support is experimental and not suitable for production use. source
- Workload discovery
- It scans platforms to identify pods, containers, applications and infrastructure and maps their topology and attack surface. source
Checked against the maker's pages on 30 Sept 2026.