Upwind
Upwind Story Replay: Watch the Attack Unfold (2026-10-21) commercialThe section your link pointed to isn't on Upwind's page any more, so we've brought you to the top.
Upwind is a runtime-powered CNAPPCNAPPA cloud-native application protection platform that combines checks across cloud configuration, workloads and development. It helps teams connect risks that separate tools might report apart. that protects cloud workloads by combining posture, detection and response, and identity security with real-time runtime context.
Summary
Upwind is a commercial CNAPP delivered 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. platform that protects cloud and AI workloads by combining agentless scanning with runtime sensors, giving security, developer, and devops teams a shared, continuously refreshed view of what's running, connected, and exposed. It scores live compliance against frameworks like CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline., NIST, ISOISOA widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability., and the EU AI ActEU AI ActEU regulation that classifies AI systems by risk level and imposes compliance obligations—documentation, transparency, human oversight—on developers and deployers, shaping how AI-based cyber tools are built and sold in Europe., ties findings to specific accounts and owners, and uses runtime context to cut alert noise and flag active attacks as they happen rather than relying on static severity scores. It also pulls in source-control and data-platform context, scanning repositories across GitHub, GitLab, Azure DevOps, and Bitbucket, and inventorying assets in Snowflake. It sits in the CNAPP category alongside live-inventory and exposure-management tools, and has shipped six releases since launching in 2022, most recently 19 days ago.
Upwind is a runtime-powered CNAPP that protects cloud workloads by combining posture, detection and response, and identity security with real-time runtime context.
How Upwind helps
Which of my cloud workloads are actually exposed at runtime versus just misconfigured on paper?
correlates posture findings with live runtime behavior so a flagged workload is ranked by whether it is actually reachable and running, not just non-compliant
Which of my repositories have findings that need attention before merge?
scans connected repositories across version control providers and surfaces findings directly on pull requests, without altering the existing pipeline
Who or what actually touched this identity or resource, and was that expected?
ties identity activity to runtime context so an access event can be checked against what the workload was actually doing at the time
Which organizations and repositories are in scope for scanning right now?
lists every connected organization and repository in one place, separate from the access grant, so scan coverage can be checked without re-auditing permissions
Is a detected threat in my cloud environment something to act on immediately?
combines detection and response signals with runtime context to show whether the flagged behavior is live and ongoing in the workload
Do teams outside GitHub, GitLab, Azure DevOps, or Bitbucket Cloud have visibility into their scan results?
accepts scan results from any version control provider through the API, so findings from unsupported tooling still land in the same place as the rest
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Media
Videos from the release notes, newest first. They play right here.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 Upwind, 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 Upwind 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
upwind.io, every changeUpwind's home page and 31 more pages as they looked each month from September 2022 to October 2026: 293 renders, 140 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 Upwind connects to, runs on and detects, read from its release notes and docs. So far: 2 new vulnerability checks, 2 new detections, 1 new integration.
5 changes, tracked since Oct 13, 2026.
-
Oct 212026
new PHP core unauthenticated RCE detection rules (CVE-2026-109618, CVE-2026-109619)
Two critical unauthenticated RCEs in PHP core, with research published before the official disclosure. Upwind had detection rules deployed before the vulnerabilities were confirmed
-
Oct 212026
new eMudhra intermediate CA key exposure detection
The private keys of eight eMudhra intermediate CAs were recoverable from the certificates themselves, enough to sign fraudulent TLS and code-signing certificates that chain to a trusted root ( what we published ).
-
Oct 212026
new LiteLLM 1.107.0 poisoned PyPI backdoor detection
With .pth, sitecustomize.py
LiteLLM 1.107.0. A poisoned PyPI release shipped a remote-code backdoor through .pth and sitecustomize.py, running on every Python start on the host ( Upwind MDR Post ).
-
Oct 212026
new GitLab integer overflow RCE behavioral detections (CVE-2026-110264)
GitLab, CVE-2026-110264. An integer overflow in the regular-expression compiler, rated CVSS 10.0, that could let an unauthenticated user run code on a self-managed GitLab server. It reaches every version back to 7.0, and GitLab shipped two behavioral detections alongside the patch ( what we published ).
-
Oct 132026
new Cursor Origin integration
With Origin Marketplace
Upwind is now integrated with Origin. Every pull request and every push to the default branch is scanned, whoever or whatever opened it, with results delivered inside the pull request.
Editors & IDEs 1
Other 1
Nothing first seen in this window. That doesn't mean Upwind shipped nothing, only that we found no record of it.
How we count
Read from 3 of 14 release notes and docs updates we hold for Upwind. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Upwind'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
14 entries
No entries match these filters.
- October 20266
- September 20264
- August 20264
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.