Cloud Cost Engineering and Open Source FinOps
Notes from the team building C3X. Cost estimation for Terraform, the economics of cloud infrastructure, and how to ship FinOps tooling without a SaaS gate.
Status page cost: hosted services vs self-hosted
Status pages communicate incidents and uptime to users, via hosted SaaS (per-subscriber or feature tiers) or self-hosted (open-source plus hosting). For most, hosted is cheap; self-hosted suits scale or customization. Here is the model.
Data pipeline cost optimization: moving and transforming data for less
A data pipeline's cost is the compute that ingests and transforms data, the storage it lands in, and the data transfer between stages. Processing only what changed, right-sizing compute, and efficient formats cut it. Here is how.
ETL vs ELT cost: where you transform changes the bill
ETL transforms data on separate compute before loading it; ELT loads raw data into the warehouse and transforms there using warehouse compute. Which is cheaper depends on your warehouse pricing and transformation load. Here is the tradeoff.
Streaming vs batch data processing: the cost of freshness
Streaming processes data continuously for low-latency freshness, keeping compute always running; batch processes in scheduled bulk runs on transient compute. When data does not need to be fresh instantly, batch is far cheaper. Here is the tradeoff.
Data warehouse cost optimization: compute and storage discipline
Data warehouse cost is compute (queries and transformations) plus storage, whether Snowflake credits, BigQuery bytes scanned, or Redshift nodes. Scanning less, right-sizing compute, and auto-suspend cut it. Here is how.
Data lake cost optimization: storage tiers and query efficiency
A data lake's cost is object storage (often huge volumes) plus the query engines that read it. Storage tiering, lifecycle policies, compaction, and efficient formats cut it. Here is how to keep a growing lake affordable.
Kafka cost optimization: brokers, storage, and managed vs self-hosted
Kafka cost is the broker compute, the storage of retained messages, cross-AZ replication transfer, and (if managed) the service premium. Retention, right-sized brokers, and tiered storage cut it. Here is how.
Change data capture cost: streaming database changes efficiently
CDC streams inserts, updates, and deletes from source databases to downstream systems, priced by the volume of change data plus the connector compute. High-change sources and full-table snapshots drive the bill. Here is how to keep it lean.
Data orchestration cost: the scheduler is cheap, the tasks are not
Orchestration tools (Airflow, Dagster, Prefect, Step Functions) schedule and coordinate data workflows; the orchestrator itself is modest, but the tasks it runs are the real cost. Efficient tasks and right-sized orchestration cut it. Here is how.
Airflow cost in the cloud: managed vs self-hosted
Running Airflow costs the always-on scheduler, webserver, and workers plus the metadata database, whether self-hosted or on a managed service (MWAA, Cloud Composer) that adds a premium. Right-sizing and worker autoscaling cut it. Here is the model.
dbt cost: the tool is cheap, the warehouse compute is not
dbt transforms data with SQL in your warehouse; dbt Core is free and dbt Cloud has per-seat pricing, but the real cost is the warehouse compute your dbt models run. Efficient models and incremental builds cut it. Here is the model.
Reverse ETL cost: syncing warehouse data back to tools
Reverse ETL syncs data from the warehouse into operational tools (CRM, marketing, support), priced by rows synced or per destination, plus the warehouse queries that extract the data. Sync frequency and volume drive the bill. Here is the model.
Data observability cost: monitoring pipelines without overspending
Data observability tools monitor data quality, freshness, and pipeline health, priced by tables or volume monitored plus the queries they run to check data. Scoping monitoring to critical data and efficient checks cut it. Here is the model.
Vector database cost: what powers similarity search
Vector database cost is storage of embeddings plus query compute, whether managed (Pinecone, managed pgvector) or self-hosted. Dimension count, vector count, and query volume drive the bill. Here is the model.
Embedding cost optimization: cheaper vectors at scale
Generating embeddings costs per token via an embedding model, and re-embedding large corpora or every query adds up. Caching embeddings, choosing right-sized models, and batching cut the bill. Here is how.
Fine-tuning cost in the cloud: adapting models for less
Fine-tuning a model costs training compute (GPU-hours) plus data preparation, and serving a fine-tuned model may cost more than a base model. Parameter-efficient methods and right-sized runs cut it. Here is the model.
AI agent infrastructure cost: the price of autonomous loops
AI agents make many LLM calls per task as they reason, use tools, and iterate, so their cost is LLM tokens times the loop length, plus the tools and infrastructure they invoke. Long loops and large context drive the bill. Here is how.
Prompt caching cost savings: paying once for repeated context
Prompt caching lets an LLM API bill repeated input context at a large discount after the first call, so a big shared system prompt or document sent many times costs far less. For repeated-context workloads, savings are substantial. Here is how.
ML feature store cost: online and offline storage plus serving
A feature store's cost is the offline store (bulk feature data for training), the online store (low-latency serving for inference), and the compute that materializes features. The online store and materialization drive the bill. Here is the model.
Data labeling cost: budgeting the least glamorous ML expense
Labeling training data, human annotation, managed labeling services, or model-assisted labeling, is often a large and underestimated ML cost. Active learning, pre-labeling, and scoping the labeled set cut it. Here is how.
Model registry cost: versioned models are mostly storage
A model registry stores versioned model artifacts and metadata; its cost is mostly the storage of those artifacts, which can be large for many versions of big models. Lifecycle policies and pruning old versions cut it. Here is the model.
SageMaker cost optimization: training, endpoints, and notebooks
SageMaker cost spans training jobs (GPU-hours), inference endpoints (always-on serving), notebooks and Studio (idle compute), and processing. Endpoints and idle notebooks are the biggest waste. Here is how to cut it.
Vertex AI cost optimization: training, prediction, and pipelines
Vertex AI cost spans custom training (compute-hours), prediction endpoints (always-on nodes), pipelines, and notebooks. Idle endpoints and workbench instances are the biggest waste. Here is how to cut it.
Azure Machine Learning cost optimization: compute is the bill
Azure ML cost is the compute it orchestrates, training clusters, inference endpoints, and compute instances (notebooks), plus storage. Idle compute instances and always-on endpoints are the biggest waste. Here is how to cut it.