Funding rounds, leadership changes, incidents, new capabilities and announcements across the vendors in this catalog — collected automatically from vendors' own public feeds. Product release versions are on their own page, so the landing feed here never reads as one vendor's changelog.Where this comes fromEvery item links to the vendor's own published source: a GitHub release feed, a changelog, a status page, an SEC filing or a company blog. Nothing here is written or editorially reviewed by 0-Doubt, and nothing is a recommendation — it is machine-collected public record, labelled the same way as all other baseline content on the platform. Coverage is uneven by design: a vendor that publishes no public feed will not appear, and that absence is not a judgement about the vendor.
17 matching stories — release, in Bug Bounty — showing up to 3 per vendorPer-vendor capWhile browsing, no single vendor may fill more than three slots on any one page, so a vendor with a chatty release cadence cannot buy the page you are looking at. That means a page can render fewer stories than the count above. Searching a headline or naming a vendor turns the cap off, because then you have asked to see everything that matches.
What we did: We added support for equally splitting bounties when duplicate findings are submitted within a collaborative pentesting setup involving multiple researchers. When duplicate submissions are identified, the bounty can be distributed across the relevant researchers instead of rewarding only the first person to submit. Why we did it: Collaborative pentests work best when researchers combine their skills and knowledge to achieve the strongest possible outcome for the customer. If duplica
What we did: We added severity filters for Slack and webhook notifications, so companies can choose which submission severities trigger notifications. Why we did it: This helps teams reduce noise and focus notifications on the findings that matter most to their workflow. Who it helps: This helps companies that use Slack or webhooks to route relevant vulnerability updates to the right teams and channels.…
What we did: We added support for multi-researcher PTaaS programs, allowing one PTaaS program to include multiple researchers and pentests under the same engagement. Teams can set the number of researchers needed and coordinate submissions collaboratively within one streamlined flow. Why we did it: Large scopes often need different specialist skills and parallel testing within a fixed customer testing window. Previously, this required duplicating programs and extra manual coordination. This up…
