Unit Economics: BigQuery

Tie cloud cost to business outcomes. ZopNight ingests product metrics through Push API, CSV upload, or Pull API and joins them with cost data to produce cost per MAU, per order, per request, and per signup. Recommendations rank by impact on unit economics, not raw dollar savings. Applied to GCP BigQuery, it is one of the most reliable ways to take waste out of non-production without touching how the service runs in production.

Serverless data warehouse bill around the clock, and unit economics is about making sure you only pay for the hours and capacity you actually use. ZopNight Track this against your measured usage, the same FinOps discipline that separates it from dashboard-first tools like CloudHealth.

Why unit economics matters for BigQuery

What unit economics actually buys you:

• Built-in metrics for cost per MAU, per order, per request, per signup.
• Push API for real-time events, CSV for backfill, Pull API for scheduled sources.
• Recommendations ranked by impact on cost-per-unit, not raw dollars.
• Composable with showback for per-team unit economics.

For BigQuery specifically, the win comes from the gap between how long the resource runs and how little of that time anyone is using it.

How ZopNight does it

Connect a read-only role, let ZopNight discover your BigQuery across regions and accounts, and act, scheduling stops and starts on your hours, guided rightsizing for the oversized, idle detection for the forgotten. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147) and 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided. Production is excluded by default and every action is logged.

How ZopNight schedules BigQuery

The loop that does this is deliberately mechanical, and it starts read-only. You connect AWS, GCP, and Azure with a read-only role, and ZopNight discovers every BigQuery across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.

Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.

Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a BigQuery ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.

Getting started

Getting started is intentionally low-stakes:

• Connect AWS, GCP, and Azure with a read-only role. Nothing is scheduled or changed at this stage.
• Let ZopNight discover your BigQuery and review exactly what it found, filtered by account, region, and status.
• Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
• Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.