ProjectDiscovery Cloud
Introducing Internal Network Scanning: see your network the way an attacker inside it would (2026-07-21) commercialThe section your link pointed to isn't on ProjectDiscovery Cloud's page any more, so we've brought you to the top.
ProjectDiscovery Cloud is a platform providing cloud-based security scanning and reconnaissance tools for identifying vulnerabilities and assets in applications.
Summary
ProjectDiscovery Cloud is a commercial vulnerability management platform that discovers assets and validates which vulnerabilities are actually exploitable, running as a cloud service with a free sign-up tier and a demo path for enterprise-scale coverage. It inventories internet-exposed, internal, and cloud assets—VMs, load balancers, Kubernetes ingresses, subdomains—and tracks changes continuously, while an internal network scanning capability reaches assets and exposures external scanners cannot see. Findings are confirmed through runtime attack simulation rather than CVE matching alone, which cuts triage work, and detection logic is kept current through a community-contributed, internally vetted template feed. It suits security teams and developers who need a prioritized, noise-free view of real risk rather than a raw vulnerability list, sitting in the exposure-management space alongside attack-surface monitoring tools.
ProjectDiscovery Cloud is a platform providing cloud-based security scanning and reconnaissance tools for identifying vulnerabilities and assets in applications.
How ProjectDiscovery Cloud helps
Which internet-facing and internal assets do I actually have, and has anything changed since last time?
continuously enumerates VMs, load balancers, Kubernetes ingresses, sub-domains and cloud resources and records a changelog per asset, so new hosts or configuration drift show up instead of going unnoticed
Of everything flagged, which vulnerabilities can an attacker actually use against me right now?
runs a safe, real-world attack simulation against each finding at runtime and only surfaces the ones proven exploitable, instead of relying on CVE version matching alone
What is exposed on my internal network that nobody scanning from outside would ever see?
scans from inside the network itself, reaching hosts and misconfigurations that an external, internet-facing scanner cannot reach
Am I about to spend my week chasing findings that don't matter?
strips out unconfirmed matches before they reach the team, which is reported to cut manual triage effort by up to 97 percent
Is my detection coverage keeping up with newly emerging exploits and CVEs?
pulls in new vulnerability templates from a community feed that ProjectDiscovery's internal security team vets before release, so new attack techniques get added without waiting on a private research cycle
Did the fix I shipped for a finding actually hold, or did it regress?
supports automated retesting of previously found vulnerabilities to verify remediation and catch regressions
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for ProjectDiscovery Cloud, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail ProjectDiscovery Cloud puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
30 entries
No entries match these filters.
- July 20261
- January 20261
- December 20251
- August 20251
- June 20251
- April 20251
- March 20251
- February 20251
- December 20241
- October 20241
- September 20242
- August 20241
- June 20241
- May 20242
- April 20242
- March 20241
- February 20242
- January 20242
- December 20234
- November 20233
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →