Aether AI
Platform

Plans and usage

How Aether AI meters offensive and defensive coverage through pentest capacity and per-asset ASM tiers, with negotiated enterprise plans.

Aether AI charges for the work it actually does against your attack surface, not for a fixed bundle of seats. Coverage comes in two forms: pentest capacity for the frontier offensive engine, and per-asset ASM tiers for continuous discovery, monitoring, and validation. Understanding how the two meter helps you match spend to the surface that matters and to the depth of assurance you want on it.

Why usage is metered this way

Different parts of your attack surface deserve different depths of attention, and each depth costs a different amount to run. A domain you simply want to watch for change is cheap to keep an eye on. Actively validating what a commodity attacker could exploit against it costs more. Turning autonomous frontier agents loose to chain weaknesses and work through authentication is heavier and slower again. Aether AI meters at the level where the cost lives, so you can be precise: monitor broadly, validate where it counts, and spend the expensive frontier capacity where the stakes justify it.

Pentest capacity

The Autonomous AI Pentest is the frontier engine. Autonomous offensive agents chain weaknesses, work through authentication, and surface novel and business-logic flaws that generally-available tooling cannot reach. This is the heaviest work Aether AI does, and it runs only against scope you have explicitly authorised.

Because a frontier pentest is far more intensive than continuous monitoring, it is metered as capacity rather than per asset. A plan carries an amount of pentest capacity, and each authorised engagement draws against it. This keeps the most expensive form of assurance deliberate: you decide which scope earns a full frontier engagement, and the capacity you hold reflects that.

Per-asset ASM tiers

Everything in your attack surface starts as a discovered asset. From there, you choose how much attention each asset gets by setting its monitoring status, and that status is what meters ASM cost. The statuses form a closed set: Discovered, Confirmed, Monitor, Monitor Plus, and Ignored. Two of them carry ongoing cost, because two of them do ongoing work.

Monitor

Monitor is passive coverage. An asset on the Monitor tier gets continuous Port Analysis (an open-ports inventory built from a port sweep) and Technology Detection (a technology and version fingerprint). Both alert you when they change, and both feed the validation layer above them. Monitor tells you what is exposed and what is running on it, and it tells you the moment either shifts.

Monitor Plus

Monitor Plus adds active exploitability validation on top of passive monitoring. This is where the Conventional Attack Surface capability runs: continuous, non-destructive validation of what a commodity adversary could exploit, using generally-available tooling. It checks, it does not exploit, and it costs more than Monitor because it is doing real validation work on every pass.

Tiers meter cost per asset, so the number of assets you hold at each tier is what drives ASM spend. Because the tier lives on the asset, you control it directly: promote an asset to Monitor Plus when you want it validated, and downgrade it when you do not. Downgrading stops the deeper work, and the metered cost stops with it.

For risk owners and budget holders

The per-asset model means ASM cost is legible. Every dollar maps to a specific asset at a specific tier, and promoting or downgrading an asset changes what you pay in a way you can see and defend. There is no crown-jewels guesswork built into pricing: you decide which assets warrant validation, and the meter follows that decision.

Negotiated enterprise plans

Aether AI supports negotiated enterprise plans. Rather than a fixed public tier, an enterprise plan combines the pentest capacity and the per-asset ASM allowance that fit your organisation, and pricing is agreed against that shape. Usage is metered against the plan so that consumption stays visible over time and both sides can see how coverage tracks to what was agreed.

The pieces you are metering against are the same ones described above: pentest capacity for frontier engagements, and the count of assets held at Monitor and Monitor Plus for continuous ASM. An enterprise plan simply sets the allowances and the terms around them.

What you control

  • Which assets sit at Monitor versus Monitor Plus, and therefore how much continuous ASM work is running and being metered.
  • Which scope earns an Autonomous AI Pentest, drawing against your pentest capacity.
  • Downgrading any asset to stop the deeper work and its cost immediately.

Coverage is a set of choices you make asset by asset and engagement by engagement, and the meter reflects those choices rather than a flat subscription.

On this page