specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Aqua Security
providerId: aqua-security
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
- Cloud Native
- Containers
- Kubernetes
- Runtime Protection
- Security
- Vulnerability Scanning
- FinOps
- Cost Management
- FOCUS
description: FOCUS-aligned FinOps placeholder for Aqua Security. No public billing-model details, meters,
  or invoice schema are published; this artifact records the absence so consumers know to source commercial
  terms from the provider directly.
notes: Aqua Security uses consumption-based enterprise pricing — Dev Security is priced per code repository
  and Cloud Security per workload (EC2 instance, Fargate container, Lambda function, etc.). No public
  per-tier prices, free tier, or quotas are published; the pricing page directs prospects to Request a
  Trial / Get a Demo.
sources:
- https://www.aquasec.com
- https://focus.finops.org/focus-specification/v1-3/
- https://www.aquasec.com/pricing/
- https://docs.aquasec.com
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
publisherName: Aqua Security Software Ltd.
serviceCategory: Security
billingModel:
  pricingCategory: Custom / Contract
  billingFrequency: Per-Invoice
  billingCurrency: USD
  chargeCategories:
  - Usage
  - Purchase
  - Adjustment
focusColumns:
  ServiceName: Aqua Security
  ServiceCategory: Cloud Native Security
  ProviderName: Aqua Security
  PublisherName: Aqua Security Software Ltd.
  InvoiceIssuerName: Aqua Security Software Ltd.
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
- name: contract_usage
  description: Catch-all meter for contract-governed consumption. Replace with provider-specific line
    items once an invoice or usage schema is available.
  unit: varies
  aggregation: sum
  dimensions:
  - contract
  - consumer
principles:
- name: Visibility
  description: Because the provider does not publish a usage API or self-serve billing dashboard, request
    invoice copies and contract usage exports directly from the account team and load them into your own
    FinOps tooling.
- name: Allocation
  description: Allocate spend by tagging invoice line items to consuming business units in your ERP /
    FinOps store; no provider-side tagging surface is available.
- name: Optimization
  description: Optimization levers are commercial — renegotiate volume commitments, consolidate accounts,
    or align contract scope with actual usage at renewal.
- name: Accountability
  description: Assign a contract owner who reviews invoices against the negotiated agreement, since usage
    drift cannot be detected from a published meter feed.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com