Riot
OWASP course series commercialThe section your link pointed to isn't on Riot's page any more, so we've brought you to the top.
Riot is an employee cybersecurity platform that helps companies reduce human risk by training employees, monitoring threats, and protecting personal accounts.
Summary
Riot is a commercial employee security posture management platform that monitors and scores how well a company's staff resist phishing and social-engineering attacks. It runs as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service, syncing automatically with Google, Microsoft, and Okta to stay aligned with a company's directory, and it delivers awareness training, attack simulation, and breach intelligence in 33 languages. It is built for cybersecurity and IT teams who need a way to measure and improve employee behaviour rather than just patch systems, giving them a single Karma score to track posture over time. It sits in the integrated-risk-management space, positioning itself against traditional cyber awareness training rather than technical scanning tools, arguing that generic training cannot keep pace with AI-driven attacks. Our records show three releases in the window we track, suggesting steady, ongoing development.
Riot is an employee cybersecurity platform that helps companies reduce human risk by training employees, monitoring threats, and protecting personal accounts.
How Riot helps
Which employees are most likely to fall for the next phishing attempt?
runs attack simulations against staff and rolls the results into each person's Karma score, so weak spots surface before a real attacker finds them
Which team or department is dragging down our overall security posture?
aggregates individual Karma scores into a company-wide score that can be tracked over time to spot which groups need attention
Has our security posture actually improved since we started training?
tracks the integrated Karma score over time, giving a single trend line instead of a pile of disconnected training completion records
Are new hires and departing employees covered by our security monitoring without extra admin work?
syncs automatically with Google, Microsoft, and Okta so the employee directory driving training and simulation stays current on its own
Can non-English-speaking staff be assessed and trained in a language they understand?
delivers awareness training, simulation, and breach intelligence in 33 languages, so results reflect comprehension rather than a language barrier
Who in the company has been exposed in a recent data breach?
feeds breach intelligence into the same platform so exposed credentials or accounts show up alongside the rest of an employee's security posture
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 Riot, 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 Riot 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…
Releases
6 entries
No entries match these filters.
- June 20262
- May 20262
- April 20262
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 →