Simple, Infrastructure-Based Pricing

Plans & Prices

Five published sizes, the same $0.24/vCPU/hour rate on both products. 8 vCPU is the entry plan — smaller instances are no longer sold. Save up to 40% with annual commitment.

Software fee only, at $0.24/vCPU/hour × 8,760 hours. Deployments are Bring-Your-Own-Cloud: your AWS or Azure account is billed separately by the cloud provider for the VM, storage, and networking. Term discounts are delivered as a published annual plan (self-serve); private offer for negotiated terms and channel resale.

Term prices are delivered as a private offer — an AWS Channel Partner Private Offer (CPPO) or an Azure Multiparty Private Offer (MPO). A publisher cannot discount a published marketplace metered rate, so the commitment price is issued as an offer against your account rather than as a change to the $0.24 meter. Request a private offer.

vCPU Sizing Guidance (SAT)

vCPU size is driven by campaign throughput — targets per send wave and concurrent campaigns — not by headcount. One marketplace instance handles unlimited users, so the target counts below are throughput profiles, not seat caps.

Software fee only, at $0.24/vCPU/hour × 8,760 hours. Deployments are Bring-Your-Own-Cloud: your AWS or Azure account is billed separately by the cloud provider for the VM, storage, and networking.

Target counts come from SAT’s own VM scaling guide. The 8, 16, and 32 vCPU figures are documented; 12 and 24 vCPU are interpolations between documented rungs and are marked as guidance, not specifications. Neither 12 nor 24 vCPU is a standard Azure Dsv5 or AWS m5/m6i shape, so those two are sized to order.

MSSPs: size per instance, not per client. A dedicated instance per client only pencils out for a client large enough to justify about $20,160/year all-in (software plus its own cloud) — roughly 576 seats against a $35/seat incumbent rate. For a book of smaller clients the pattern is consolidation: one instance carries multiple client organizations when the MSSP operates the platform, with row-level data isolation, per-client sending identities, and per-client hostnames. Clients that require their own branding, their own identity provider, or self-service administration need a dedicated instance. We do not publish a tenants-per-size figure — there is no measured basis for one, so size on campaign throughput and hold the per-client economics separately. See Pricing for MSSPs below.

vCPU Sizing Guidance (ASM)

ASM instance size is driven by scan volume — how many scheduled scans run per day across the monitored surface — not by employee count. As with SAT, one instance handles unlimited targets and findings.

Software fee only, at $0.24/vCPU/hour × 8,760 hours. Deployments are Bring-Your-Own-Cloud: your AWS or Azure account is billed separately by the cloud provider for the VM, storage, and networking.

Scan volumes come from ASM’s hardening and scheduled-scan guides. 8 vCPU is ASM’s documented Production (recommended) size on both clouds; its documented technical minimum is 4 vCPU, which sits below the entry plan, so for ASM the entry size is the recommended production size rather than a floor we invented. Above 16 vCPU the guides do not differentiate scan volume further — very high scan cadence is sized case by case. The hourly rate stays $0.24/vCPU at every size.

How ASM uses a larger instance. ASM derives its scan-worker limits from the host, so the cores you buy go to scanning: the worker gets half the machine’s CPU and 40% of its memory, which is 4 cores on an 8 vCPU instance, 8 on a 16, and 16 on a 32. Concurrent scan capacity scales with it. Instances deployed before August 2026 keep their original limits until the next update, when the installer rewrites them to match the machine — if you are running an older deployment and sizing up, check with us so the update happens alongside the resize. SAT scales the same way by memory, sizing its heap limit from the host automatically.

Deployment Shape Costs

The plans above size a single instance. Topology is a separate axis: the same marketplace image deploys into one of three reference shapes, and HA / auto-scaling add managed Postgres, Redis, and load balancing. The $0.24 meter rate is identical across all three — what changes is the metered vCPU count and the infrastructure you run it on. Every shape is built from 8 vCPU instances, the entry plan size.

The $0.24/vCPU/hour meter is the software fee only. HailBytes is Bring-Your-Own-Cloud: the VM, storage, database, and networking run in your own AWS or Azure account and are billed to you by the cloud provider. The infrastructure column is indicative — roughly $35/vCPU/month for the base stack (VM + PostgreSQL + Redis + storage) taken from our own scaling guidance, priced on Azure before reserved-instance discounts. The load balancer and cross-AZ data transfer that HA and auto-scaling add are not estimated here; price them in your cloud provider’s calculator. Auto-scaling fleets are N × 8 vCPU instances, so the 10-instance row is 80 metered vCPU across the fleet, not a single instance above the 32 vCPU plan.

See the three deployment topologies on the marketplace page for what ships in each shape and who runs which, and the side-by-side cost shapes reference (AWS + Azure) in the Terraform modules repo for per-resource infrastructure detail. Where the two differ on price, the figures on this page are the current ones.

Total Cost of Ownership vs. per-seat platforms

A 5,000-employee org running HailBytes SAT on the 8 vCPU Essential plan vs. typical per-seat list pricing for incumbent platforms. Our figure is all-in — software plus the cloud infrastructure you run it on — because a per-seat vendor’s licence fee is their whole bill. Per-seat numbers are list ranges; private-offer discounts narrow but rarely close the gap.

Per-seat figures are indicative list-price ranges, not quotes. None of these vendors publish per-seat list pricing, so the ranges are synthesized from publicly reported RFP responses, partner channel quotes, and analyst/peer comparisons current as of June 2026; your negotiated or private-offer rate will differ and should be confirmed by a direct quote before use in procurement. Each vendor name links to our detailed head-to-head comparison. Where HailBytes SAT lands relative to the per-seat platforms gets more favorable as headcount grows — and there is a real floor below which it does not win at all. Break-even is stated all-in, including your cloud infrastructure ($16,800 of software plus ~$3,360/year of cloud, about $20,160/year), because a per-seat vendor’s licence fee is their whole bill and comparing software-only against it would flatter us. On that basis break-even is about 806 seats against the cheapest per-seat rate in the table ($25/seat) and about 576 seats against the $35/seat blended rate used in the MSSP table below; the advantage becomes decisive above roughly 1,000 seats. A 1-year commitment ($11,760 software, ~$15,120 all-in) moves those break-evens to about 605 and 432 seats. For vCISOs and MSSPs running a dedicated instance per client, the comparison is a flat ~$1,680/month all-in against that client’s per-seat cost, which favours us once the client is above roughly 576 seats at $35/seat; below that, put several clients on one instance you operate instead.

Pricing for vCISOs

vCISOs embed per-client platform cost into a fixed retainer rather than reselling via CPPO/MPO. Two shapes are available, and the choice is a capability question rather than a client-count question.

One instance carries multiple client organizations when you operate the platform, with row-level data isolation, per-client sending identities, and per-client hostnames. Clients that require their own branding, their own identity provider, or self-service administration need a dedicated instance. Because that relationship is linear, the consolidated per-client figure is roughly the same at every plan size — we deliberately publish no tenants-per-size number, because there is no measured basis for one. A dedicated instance is hard to justify for a client under roughly 576 seats, which is most vCISO clients — a 300-seat client costs $10,500/year at a $35/seat incumbent rate against about $20,160/year all-in for a dedicated instance, so on price alone we lose that comparison and the reason to run a dedicated instance is isolation, not cost. The retainer fee on top is the vCISO’s to set, with no CPPO/MPO resale mechanics involved (see Pricing for MSSPs for that model). See the vCISO resources hub for the full retainer model discussion.

Pricing for MSSPs

Model the cost of running HailBytes across a managed client base. Two shapes: a dedicated 8 vCPU instance per client, or one instance you operate that carries several client organizations. Which is right is a capability question first and a size question second — a dedicated instance needs a client of roughly 576 seats or more to beat that client’s own per-seat licence on an all-in basis.

*Illustrative comparison assuming an average of 1,000 seats per client at a $35/seat blended list rate ($35,000/client/year). Your client mix and negotiated rates will differ. The dedicated column is client count × $16,800 of software, and the all-in line adds each client’s own cloud at ~$280/month. The consolidated column is a per-client figure and it is the same at every plan size, because the relationship is linear — we publish no tenants-per-instance count. Be clear-eyed about which column you are in: all-in, a dedicated instance per client costs roughly 40% less than the per-seat equivalent at 1,000 seats a client, while MSSP-operated consolidation is roughly 10–32× cheaper per client ($35,000 ÷ $3,400 and ÷ $1,100). The dedicated shape beats a per-seat licence for any client above roughly 576 seats all-in; below that the client belongs on an instance you operate.

ASM sizes differently: one instance per monitored client. — $16,800/year at the 8 vCPU entry plan plus that client’s own cloud, about $20,160/year all-in. Projects remain how your own analysts keep engagements separate on a single instance; they are not a per-client billing boundary. If a shared-instance ASM book is what you are modelling, talk to us before you price it.

Run your own numbers with the MSSP ROI calculator.

On top of the platform math, AWS Channel Partner Private Offers (CPPO) and Azure Multiparty Private Offer (MPO) let you resell the HailBytes platform at up to a 20% margin through each client’s own marketplace bill — their purchase draws down their EDP / MACC commit, and you capture platform margin on top of your managed-service fee. The 20% is calculated on the post-discount net the customer pays, not on list price. For operational mechanics (provisioning, instance branding under your own name, and how client data is kept separate), see the MSSP resources hub and the MSSP margin economics deep dive.

Committed private offers improve the wholesale baseline: per the partner-resell program, a 1-year commitment paid annually upfront is 30% off list, a 2-year commitment is 35% off, and a 3-year commitment is 40% off. Because the resale margin is taken on the net, a 20-client book of dedicated 8 vCPU instances at the 1-year rate is $235,200 of net rather than $336,000 of list, so the 20% ceiling is up to $47,040 — not the $67,200 a margin-on-list reading would imply. Per-client volume discounts also step the wholesale rate down as your client count grows; exact thresholds and wholesale rates are set in the partner-resale authorization issued at enrollment. See /partner-resell/ for the full discount mechanics.

What’s Included

Support Tiers

The marketplace price covers the platform. Optional Cloud Support Hub tiers add SLAs, deployment assistance, and dedicated security engineers.

Estimate Your Costs

Model the marketplace meter for any published plan size at the $0.24/vCPU/hour rate. This is the metered, pay-as-you-go software charge — annual plan prices and commitment rates are in the plan table above. All math runs in your browser — nothing is sent anywhere.

Estimates only, not a quote. This is the metered software charge on a single instance at $0.24/vCPU/hour; it does not include your cloud infrastructure, which AWS or Azure bills you separately (see Deployment Shape Costs). Published plan prices round the monthly figure to the nearest $100, so the 8 vCPU plan lists at $1,400/month and $16,800/year against a metered $1,401.60/month — and commitment discounts apply to plan pricing, issued as a private offer, not to the metered rate.

For multi-vCPU and topology modeling, use the full interactive calculator on the marketplace page.

Common Pricing Questions

Need a structured rollout? Walk the proof-of-concept process for evaluation stages and success criteria, or see how to buy through AWS or Azure Marketplace.