Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

CloudClerk. We struggled with BigQuery finops, so we decided to fight

Details

External ID
46734333
Source
HN
Company
—
Product
CloudClerk. We struggled with BigQuery finops, so we decided to fight
Website domain
cloudclerk.ai
Launched
Jan. 23, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.09617918313570488
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

Hello HN, Lucas here.I’ve been working with BigQuery for ~5 years, mostly in large (petabyte-scale) environments. Over time we ended up spending a lot of money and engineering effort just trying to understand where costs were coming from, why and how to optimize them.At some point we decided to stop, leverage all our past experience and spend a full cycle building tooling focused on cost visibility and optimization. The main goal was to regain ownership of cost data and make it possible to understand our cost structure in under a minute, while aligning the views of engineering and FinOps at the project level. To complement these, and given the recent rise of AI, we also built agents that review usage patterns and selected KPIs to surface issues and suggest concrete optimizations (always through an encoding layer for privacy).This ended up working well for us: we reduced monthly BigQuery spend by ~43% and made cost considerations part of normal engineering workflows instead of a separate FinOps exercise. After validating it with a few other teams facing similar problems, we decided to ship it publicly in November.Some transparency items to consider: - We only work with bigquery related information, not all gcs. - While we already support most sources of cost, the project is in constant development. If you use an uncommon feature it may not be covered, but we will implement it for you. - The larger the company the larger the impact, since there tends to be larger technical debt. Nonetheless, we've seen significant impact in lower scale startups. - We dont need labels. Labels are great, and should be taken care of, but we do not depend on them to provide insights.Happy to share details, lessons learned, or tradeoffs if this is interesting to others dealing with large-scale data warehouse costs. Check us out at https://www.cloudclerk.ai/

Enrichment

Theme
database infrastructure and developer tools
Vertical
Fintech
Function
Analytics & BI
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
bigquery cost optimization
Manually corrected
False

Could you build this?

No Analyzing, profiling, and optimizing petabyte-scale BigQuery finops requires deep distributed database internals, parsing BigQuery information schema/audit logs, and domain expertise in query execution plans.

What it would actually take: A production BigQuery finops platform requires ingestion pipelines for GCP audit logs, query execution plan DAG parsers, slot contention modeling, and cost attribution algorithms. The stack typically combines GCP Cloud Pub/Sub, Dataflow or Go ingestion workers, a timeseries/OLAP storage layer (like ClickHouse), and automated recommendation engines. The hardest challenge is building deterministic, reliable query AST/execution plan analyzers that recommend safe partition/cluster changes without breaking production workloads.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 127 launches clear the similarity bar, closest 8 shown.

Attention rank: #122 of 128 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 86 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a analytics & bi tool for Legal yet.