Dependency upgrades for security teams
For engineering teams →

Upgrade dependencies without breaking your security rules.

Olympix checks every upgrade against the rules your product must never break, before it merges. New features and vulnerability fixes alike.

This week7 open upgrades
Your security rules
Checked on 5 feature upgrades and 2 vulnerability fixes before they merge.
Olympix formal check 0 / 18 rules
  • A customer only sees their own filesqueuedchecking…holds
  • Account pages require sign-inqueuedchecking…holds
  • Shared links expire after 7 daysqueuedchecking…breaks
  • 15 more security rulesqueuedchecking…hold
ResultChecking…1 rule breaks
StatusWaitingstorage-sdk 2.8 held
01The problem

Any upgrade can break a security rule.

Feature or vulnerability fix, every upgrade changes code your rules depend on. Scanners don't check those rules, and tests rarely do.

It happened to us: a Chromium security patch also deprecated a flag our PDF generation depended on. We found out when the PDFs failed.

And an upgrade can quietly undo a fix you shipped.

Upgrades already in the queue were never checked against your latest fix. One of them can merge and take it back out.

The median dependency is now 278 days behind. Datadog, 2026
02What changes

Your security rules hold through every upgrade.

Every upgrade is checked against every rule before it merges, and every new rule against every open upgrade.

Works alongside the scanners and upgrade bots you already run.

Upgrades that break a rule don't merge

Features and vulnerability fixes get the same check.

Your fixes stay fixed

An upgrade that would undo a fix is held before it merges.

A record for every upgrade

Each report shows which rules held and what couldn't be checked.

03Our technology

Powered by Deductive Interception.

Scanners tell you what's inside a package. Our formal methods engine checks what an upgrade does to your security rules, and every result shows its work.

  1. 01

    Security rules your team owns

    Your team signs off on every rule, and a coding agent can't edit them.

  2. 02

    Evidence you can hand an auditor

    Every flag comes with the exact input that breaks it.

  3. 03

    Residual risk, named

    Every report names what it couldn't check.

04Building since 2022

Four years of formal methods where one bug costs millions.

2022Building since. Formal methods first proven in web3, where a bug can't be undone.
$155B+Protected across Olympix customers
$710MExploit losses our engine would have prevented

Every upgrade changes your product. None should break a security rule.

Check every dependency upgrade against your security rules. Talk to the formal methods team building it.