MyScale · FinOps Profile

Myscale Finops

FinOps view of MyScale Cloud spend. MyScale bills on a pod-based model rather than per-API-call: cost is driven by the number and size of provisioned pods (capacity-optimized and performance), replica count for high availability, and metered storage. A free Development tier carries no charge but is capacity- and inactivity-limited, and the open-source MyScaleDB engine (Apache-2.0) can be self-hosted with only infrastructure cost. Spend is therefore optimized by right-sizing pods, controlling replicas, and using the free or self-hosted paths for non-production workloads.

Myscale Finops is the FinOps profile for MyScale on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 3 billable meters, billed in USD, on a monthly cycle, and pricing category usage-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Vector Database, SQL, ClickHouse, Vector Search, and FinOps.

Category: Databases Pricing: Usage-Based Billing: Monthly FOCUS v1.3
Vector DatabaseSQLClickHouseVector SearchFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
MyScale
PricingCategory
Usage-Based
ProviderName
MyScale
PublisherName
MyScale
ServiceCategory
Databases
ServiceName
MyScale Cloud

Meters

pod_hours
Unit: pod-hours
Provisioned pod runtime (capacity-optimized or performance), billed per pod per month / hour.
replica_pods
Unit: pod-hours
Additional replica pods provisioned for high availability, billed like base pods.
storage_gb
Unit: gigabytes
Persistent storage consumed by tables, vectors, and indexes, metered per GB.

Sources