Exaforce
From Raw Logs to Semantic Intelligence commercialThe section your link pointed to isn't on Exaforce's page any more, so we've brought you to the top.
Exaforce runs AI Exabots that detect, triage, investigate and respond to threats across cloud, 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., identity, endpoint and code on a real-time knowledge graphknowledge graphA representation of entities and the relationships between them. Software can follow those connections to answer questions or combine information from different sources..
Summary
Exaforce is a commercial SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. that runs AI Exabots to detect, triage, investigate, and respond to threats across cloud, SaaS, identity, endpoint, and code using a real-time knowledge graph. Since its documentation does not specify usage constraints, it is positioned for SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts and incident responders. It operates as an agentic-soc cyber tool(s) and its project launched in 2023.
Exaforce runs AI Exabots that detect, triage, investigate and respond to threats across cloud, SaaS, identity, endpoint and code on a real-time knowledge graph.
How Exaforce helps
Which AI agents, coding assistants, MCP servers, and plugins are actually connected to our company accounts right now?
maintains a continuous, agentless inventory of connected AI apps, hosted agents, coding agents, skills, and IDE plugins tied to the people and permissions behind them
Which of our AI agents or MCP servers carry the most risk?
scores every agent, skill, MCP server, and plugin individually, flags issues like excessive permissions or unvetted servers, and pairs each with a recommended fix
Is an agent or identity chaining together actions that look fine individually but add up to misuse?
correlates agent actions, prompts, endpoint data, file access, and code context against human identities in the knowledge graph to surface sequences of legitimate-looking steps that together indicate misuse or data exposure
Is anyone burning through AI token usage in a way that signals exploitation or misuse?
tracks token consumption across the organization and flags anomalies against expected usage patterns
Who is using AI apps outside of what we've sanctioned, and for what?
checks connected apps, agents, and models against defined governance rules tied to identity and endpoint controls, and separates chats and prompts classified as personal versus business use
Can we shut down a compromised agent or session without waiting on a manual response?
executes containment through existing EDR, identity, and model-provider controls — revoking sessions, deactivating API keys, isolating devices, or killing an agent's process — with autonomy set per action from analyst-approved to fully automatic
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 Exaforce, 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 Exaforce 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
exaforce.com, every changeExaforce's home page and 40 more pages as they looked each month from April 2024 to October 2026: 97 renders, 25 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.
Coverage
Missing something? Tell us
What Exaforce connects to, runs on and detects, read from its release notes and docs. So far: 1 new integration, 1 new supported platform.
2 changes, tracked since Oct 1, 2026.
-
Oct 12026
new SaaS platform detection coverage
With GitHub, Snowflake, Salesforce, OpenAI
Detection coverage across SaaS platforms. Coverage spans GitHub, Snowflake, Salesforce, and OpenAI, providing visibility across environments that can be difficult to monitor with traditional security tools.
-
Oct 12026
new CTC-MSS AI SOC Service — Japan market availability
With CTC-MSS AI SOC Service powered by Exaforce
CTC-MSS AI SOC Service powered by Exaforce will be available to ITOCHU Techno-Solutions customers in Japan starting October 1, 2026.
Model providers & gateways 1
Source control & CI/CD 1
Databases & data platforms 1
Other 1
Other 1
Nothing first seen in this window. That doesn't mean Exaforce shipped nothing, only that we found no record of it.
How we count
Read from 1 of 6 release notes and docs updates we hold for Exaforce. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Exaforce's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
6 entries
No entries match these filters.
- October 20261
- September 20263
- July 20261
- June 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.