JFrog Runtime Security
LeaderOn a mission to create a world of software delivered without friction from developer to device.
Est 2008|Valuation $11.7B|Raised $580M
Published May 16, 2026
| Starting Price | Runtime pricing not publicly listed; published platform pricing is available; runtime described as an enterprise add-on | Quote-based (host-based licensing model) | Quote-based (enterprise offerings) |
| Recommended for | Existing JFrog platform customers seeking supply-chain lineage and runtime integrity in Kubernetes | Organizations prioritizing runtime insights, container/Kubernetes threat detection, and CNAPP workflows | Large enterprises seeking broad CNAPP coverage (posture, workload protection, code integration) |
| Key Strength | Linkage between running workloads and artifact/build provenance; emphasis on integrity verification | Established runtime threat detection and CNAPP capabilities | Broad platform breadth and enterprise consolidation capabilities |
| Key Weakness | Limited independent benchmarking for runtime threat detection coverage compared with long-established runtime vendors; pricing transparency is limited | Pricing models can be opaque and may require operational security expertise to manage | Quote complexity and potential platform complexity for some teams |
Where JFrog Runtime Security appears to provide advantages
Where competitors can be stronger
Pricing and value comparison (what’s known)
Buyer consideration: Organizations that prefer predictable per-developer AppSec pricing may find products with published per-user metrics easier to estimate. Organizations that prioritize unified artifact and runtime coverage may value JFrog’s platform integration but should plan for a sales engagement to obtain precise pricing.
Market adoption signals