Black AirplaneProtectionPlan

24/7 monitoring, critical security fixes on a written deadline and upgrades before support ends, done by our senior engineers.

Why now

Attackers now turn a published fix into an attack in days.

Most apps get that fix weeks later. On Proactive, the plan most apps need, we install it within 3 days.

How long an app stays open after a flaw is published

  1. First attacks arrive 3 to 5 days after a flaw is published, on average
  2. Web apps and APIs, Average time to fix a serious flaw: 54.8 days
  3. The typical business, To fix a flaw already under attack: 43 days
  4. A monthly round of updates, Up to a month, for a flaw published just after one: 30 days
  5. Essential, Critical security fixes: 7 days
  6. Proactive, Critical security fixes: 3 days
  7. Critical care, Critical security fixes: 24 hours

Sources Edgescan 2026 Vulnerability Statistics Report, Verizon 2026 Data Breach Investigations Report, Rapid7 Q3 2026 Threat Update, Google Cloud, Time-to-Exploit Trends 2023

The two-minute caseThe full report

What’s included

Everything your app needs to stay safe and current

For web apps, mobile apps and APIs, whatever they’re built on. Every plan watches your app and fixes serious flaws. Proactive and Critical care add error monitoring, mobile apps and the upgrades.

  • 01

    Critical security fixes, on a deadline

    Most businesses take weeks to install a critical fix. We do it by the deadline in your plan, and anything under active attack goes first.

    • A written deadline in every plan
    • Headline flaws tracked the day they break
  • 02

    Updates every month

    Most apps run packages with known flaws, and the fix almost always exists. We check every package, from npm to pip, NuGet and Cargo, and install the updates monthly.

    • Every package checked for known flaws
    • Updates tested and deployed
  • 03

    Upgrades before support ends

    Languages, frameworks, servers and the app stores all retire old versions on published dates. After that, new flaws in them stay open. We move your app onto supported versions first.

    • Languages and frameworks, on Proactive and Critical care
    • Servers, databases and operating systems, on Proactive and Critical care
    • iOS and Android store requirements, on Proactive and Critical care
  • 04

    24/7 monitoring

    We check your site, app and API from outside every minute, so we know it’s down before your customers tell you. We also see the errors real people hit, and why.

    • Uptime, checked every minute
    • Certificate and domain renewals
    • Error monitoring, on Proactive and Critical care
  • 05

    Held to our security standard

    We check your app against our own security standard, from tests on every change to HTTPS and email that can’t be spoofed. Every report shows where it stands.

    • Checks against our standard
    • Leaked keys and passwords scanned
  • 06

    A report of the work

    A plain report of what we fixed, upgraded and renewed, with every outage and its cause.

    • Monthly on Essential and Proactive
    • Every two weeks on Critical care

On Proactive and Critical care

Plans

Three plans, sized to what’s at stake

Choose by what an attack could cost you. Most apps hold customer data or earn revenue, so most apps need Proactive. For scale, the average cyber insurance claim costs almost five years of Proactive.

110% off from 4 apps
  • The plan most apps need

    Proactive

    $1,950a month per app, billed yearlyBilled $23,400 a year

    For any app that stores customer or business data, earns revenue, or ships to the app stores. If a leak would hurt, this is the plan.

    Choose Proactive
    Uptime, certificate and domain monitoring
    Security standard checks and leaked key scanning
    Known-flaw checks, with monthly patches and package updates
    Critical security fixes
    Within 3 days
    Error monitoring
    Framework, language and server upgrades
    Mobile apps and app store requirements
    Report
    Monthly
  • Critical care

    $3,950a month per app, billed yearlyBilled $47,400 a year

    Apps where a breach would do serious harm: health, financial or payment data, or customers and auditors who check your security.

    Choose Critical care
    Uptime, certificate and domain monitoring
    Security standard checks and leaked key scanning
    Known-flaw checks, with monthly patches and package updates
    Critical security fixes
    Within 24 hours
    Error monitoring
    Framework, language and server upgrades
    Mobile apps and app store requirements
    Report
    Every 2 weeks
  • Essential

    $750a month per app, billed yearlyBilled $9,000 a year

    Only for apps with nothing sensitive in them, like marketing sites and simple internal tools. If one were hacked, nothing would leak and nothing important would stop.

    Choose Essential
    Uptime, certificate and domain monitoring
    Security standard checks and leaked key scanning
    Known-flaw checks, with monthly patches and package updates
    Critical security fixes
    Within 7 days
    Error monitoring
    Framework, language and server upgrades
    Mobile apps and app store requirements
    Report
    Monthly

Yearly plans are billed a year in advance. Every new plan starts with an assessment and is subject to a one-time onboarding true-up if the app needs work first. Four or more apps take 10% off every app.

How a plan starts

  1. 1

    An assessment

    Every plan starts here. We connect your app and take a full reading: versions, known flaws, certificates and uptime.

  2. 2

    A one-time true-up, if needed

    If your app needs work before we can safely look after it, we quote a fixed price to bring it up to standard first.

  3. 3

    Your plan begins

    We watch, fix and upgrade on your plan’s deadlines, and your first report arrives.

Works with your stack

Whatever your app is built on

Web apps, mobile apps and APIs on the frameworks we see most, and the languages, databases, servers and clouds under them.

Try Django, Rust or Azure.

The frameworks we see most

  • ReactJavaScript
  • Next.jsReact
  • VueJavaScript
  • AngularTypeScript
  • Node.jsJavaScript
  • .NETC#
  • LaravelPHP
  • DjangoPython
  • RailsRuby
  • Spring BootJava
  • FlutteriOS and Android
  • React NativeiOS and Android
The evidence

Fifteen times as many software flaws as a decade ago

In 2016, about 6,400 software flaws were published. Now more than 100,000 are published each year. A fix almost always exists. What’s missing is someone to install it.

101,933

Published in 2026

6,449

In 2016

National Vulnerability Database, through November 20, 2026.

A chart of vulnerabilities published each quarter from 2016 to 2026. 2016 had 6,449. 2026 had 101,933 through November 20, 2026.

Protection Plan FAQ

Questions clients ask first