SlashPeak prices your warehouse from catalog metadata alone, on BigQuery today and on Snowflake and Databricks next. The scanner never asks for dataViewer or SELECT on your tables.
bigquery.jobs.create, bigquery.jobs.listAll, bigquery.datasets.get, bigquery.tables.get, bigquery.tables.list, bigquery.reservations.list, resourcemanager.projects.get, bigquery.readsessions.create, bigquery.readsessions.getData. Keys encrypted with AES-256-GCM. Scanner jobs excluded from your findings.
BigQuery productComing soon: IMPORTED PRIVILEGES on the SNOWFLAKE database for ACCOUNT_USAGE. No SELECT on user databases. Same encryption and server-side-only credential handling.
Snowflake productComing soon: SELECT on system.query.history and system.compute.warehouses. No SELECT on user catalogs. Same recommend-only contract.
Databricks productShown in-product before a key is pasted. Nothing extra.
Google confirms every grant before the first scan. No query runs, and no table is read.
If a finding needed table contents, we would not ship that rule.
system.query.history and system.compute.warehouses rank full scans, idle warehouses, and shuffle-heavy jobs. SlashPeak never needs SELECT on your tables.
Photon speeds up a shuffle join; it does not shrink it. Adaptive execution helps at the edges, but an unclustered join key still burns DBUs every run.
ZORDER and liquid clustering write min/max stats so Photon can skip files. The wrong columns, or a stale table, means it still reads everything.
A serverless warehouse with a 10-minute auto-stop bills 10 minutes after the last query. Oversizing is a separate leak, and system tables show both.
Understand, reduce and govern your cloud data spend with SlashPeak — starting today.