Architecture and cloud-cost modeller
Data Plane Calculator
Model in-account, SaaS-hosted and hybrid scanning architectures. Separate compute, egress, storage, platform and operating costs, compare saved scenarios and test which assumptions move the outcome.
Make architecture economics visible
Monthly cost composition
ComputeEgressStoragePlatformOperations
Selected architecture
Architecture comparison
—
—
Approximate scale indicator based on marginal assumptions, not a procurement quote.
Non-financial considerations
Data residencyWhere raw data and extracted metadata are processed and retained.
Blast radiusImpact of compromised workers, credentials or control-plane access.
Operational ownershipWho patches, scales and observes workers and connectors.
Time to valueDeployment, networking, secrets and certificate dependencies.
Sensitivity analysis
Shows the approximate monthly movement when a key assumption increases by the percentage used in the model.
Interpretation
Large bars identify assumptions that deserve validated benchmarks or contractual caps. Egress usually matters more in SaaS-hosted designs, while operational effort matters more in customer-managed deployments.
Calculation method
- Total source volume is multiplied by scan coverage.
- Monthly processing combines a twelfth of the initial scope with change-rate-driven incremental runs.
- Filtering and compression reduce the effective processed volume.
- Architecture determines what percentage is assumed to leave the customer environment.
- Compute, egress, storage, platform, operating and amortised implementation costs are added.
Rates are illustrative and should be replaced with current provider, vendor and staffing assumptions.
What this does not model
- Reserved-instance and committed-use discounts
- Connector-specific API pricing and rate limits
- Tax, currency movement and negotiated commercial terms
- Downtime, incident and compliance-risk costs
- Performance differences found only through workload benchmarking