CalypsoAI
1.0.0 commercialThe section your link pointed to isn't on CalypsoAI's page any more, so we've brought you to the top.
CalypsoAI tests AI systems for security, safety, and compliance risks before deployment.
oc patch clusterpolicy gpu-cluster-policy --type=merge -p '{"spec":{"cdi":{"enabled":false}}}'
Summary
CalypsoAI is a commercial AI tool that runs as a backend service for probing AI systems against security, safety, and compliance risks before they go into production. Its API is organized around campaigns and scans run against configured providers and scanner packages, with projects used to scope access and roles, which suggests it is built for teams managing many models or deployments at once rather than testing a single chatbot by hand. Support for providers like OpenAI, Anthropic, and Google alongside its own scanner packages points to red teamers and AI security or compliance owners who need to run repeatable test campaigns across multiple model backends under one audit trail. It sits in the ai-security category, alongside tools built to stress-test models before release rather than monitor them in production, and its pace of 16 releases in the tracked window, the latest 23 days ago, indicates active, ongoing development.
CalypsoAI tests AI systems for security, safety, and compliance risks before deployment.
How CalypsoAI helps
Which of my AI projects are running scanners or providers nobody has reviewed lately?
lists scanners, scanner packages, and providers attached to each project so a security team can see what is active without asking each project owner
Who has access to a given campaign run, and did anyone change that access?
reports the current access list per campaign run and records each patch to it, so a change in who can see results is traceable to a person
Which chats or campaign runs match a person, model, or project I'm investigating?
supports searching chats and campaign runs and filtering campaign runs by model or project, narrowing a broad log into the sessions relevant to an incident
What happened around a specific security event, and who triggered it?
looks up individual audit events by identifier alongside the full audit feed, giving the detail behind a single flagged action rather than just its summary line
Can a failed campaign run be re-executed without rebuilding it from scratch?
retries a campaign run directly, reusing its existing configuration instead of requiring a new one to be defined
Who holds which roles and permissions across the users in this deployment?
exposes roles, their permissions, and per-user role assignments, and lets any of those be revoked, so entitlements can be audited and pruned from one place
Languages
Command line
1 command for CalypsoAI, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
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 CalypsoAI, 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 CalypsoAI 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…
Website history
f5.com, every changeF5's home page and 40 more pages as they looked each month from August 2021 to October 2026: 50 renders, 8 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
20 entries
No entries match these filters.
- October 20261
- September 20266
- August 20263
- July 20262
- June 20261
- May 20262
- April 20261
- March 20262
- February 20261
- January 20261
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 →