Altimate Lite for Snowflake

Reduce Snowflake Idle Warehouse Spend with Altimate Lite

Altimate Lite is a Snowflake Native App that cuts warehouse cost in your own account. It copies nothing out. Turn Auto Tune on and idle time stops billing.

Reduce Snowflake idle warehouse spend with Altimate Lite
TL;DR
  • What it is. Altimate Lite for Snowflake is a Snowflake Native App you install straight from the Snowflake Marketplace in under five minutes. From there, you flip an Auto Tune toggle on any eligible warehouse to let it run.
  • Who it is for. Data platform leads who want to cut wasted compute, and FinOps managers holding a Snowflake budget.
  • What you get. Altimate Lite suspends a warehouse as soon as it goes idle, and scales its clusters back when demand drops. It checks far more often than Snowflake's own settings do.

Altimate Lite Cuts Snowflake Warehouse Cost When Idle

Altimate Lite is a Snowflake Native App. The whole app installs into your own Snowflake account and runs there, on your own compute. Altimate never copies anything out. You open no vendor connection and file no data-residency exception. The Altimate Lite overview has the privileges it asks for and the uninstall path.

Auto Tune is the feature that moves the bill. It is a toggle on the Warehouses page. You turn it on per warehouse, so you pick which ones it manages. Turn it on and that warehouse gets tuned against real usage from then on:

  • Suspended when it goes idle. Within about a minute of the last query finishing.
  • Clusters scaled down when demand drops. Back up again when demand returns.

Two things it never does. It never changes a warehouse's size, and it never touches a warehouse you did not toggle on. Suspend and cluster scale-down are the only two settings it writes.

Why this beats Snowflake's built-in auto-suspend

Snowflake already ships auto-suspend and auto-resume. They work off fixed settings that somebody picked once and rarely revisits.

Snowflake auto-suspendAltimate Auto Tune
How often it looksA fixed probe intervalFar more often, on an interval you configure
What it acts onThe timeout in the warehouse definitionReal usage, read continuously
When it adaptsOnly when somebody edits the settingAs the workload changes, on its own

Auto Tune throttles its own checks back while a warehouse stays quiet. Watching closely costs you almost nothing. The suspend itself still lands within about a minute of the last query finishing.

The Warehouses Page Lists Cost, Savings, and a Toggle

The page gives you two counts, and together they are your to-do list:

  • Eligible. Warehouses Auto Tune could take on today, but nobody has turned on yet. This is the work left.
  • Enabled. Warehouses it already manages. This is the work done.

The Altimate Lite Warehouses page, showing Snowflake warehouse cost for an account with 63 warehouses: $653.40 of 30-day cost, $1,547 per year in potential savings, 3 warehouses eligible but not yet tuned and 9 with Auto Tune already on, a Daily Spend and Savings chart, and COMPUTE_WH showing Saved $70.59 with an estimated annual $859 beside its Auto Tune toggle.

Each day in the Daily Spend & Savings chart stacks three colors:

BandColourWhat it is
SpendYellowWhat that warehouse actually cost that day
Possible SavingsOrangeIdle spend Auto Tune could still recover, where it is off
Auto Tune SavingsGreenIdle spend Auto Tune already recovered

A tall yellow bar with a thick orange cap is uncaptured money. A mostly green bar is a warehouse Auto Tune has already caught up with.

Each row reads either Saved $X, money already captured, or Potential $X, an estimate of what turning it on would recover. Open any warehouse to see its two savings figures together and every decision Auto Tune made on it, timestamped and exportable as CSV. That is the audit trail you hand to whoever asks where the savings came from.

COMPUTE_WH detail page: Key Information, an enabled Auto Tune card reading Saved last 30 days $70.59, Realized Savings of $71 for the window beside Projected Savings of $859 per year annualized, an Agent Decisions chart, and an Auto Tune history of timestamped suspend events.

Realized Savings is actual dollars recovered in the window you picked. Projected Savings is always annualized. The two use different time bases deliberately, so a 30-day number never gets read as a year.

Auto Tune Reports What It Saved, Warehouse by Warehouse

  • It runs where your data already is. Altimate never copies your usage data out, so nobody has to review where it went.
  • Per-warehouse opt-in. Auto Tune acts only on what you toggled on, and one click reverses it.
  • Every savings number is backed by a log. Realized dollars for the window you picked, Projected annualized, and a timestamped record of every decision behind both.
Proof

Across private preview, customers averaged 19% off warehouse cost. Query performance and queue times held steady. The single best day reached 57.5%, usually a weekend, when workloads are least consistent.

Altimate Lite prices two halves of your Snowflake bill. This page covers warehouse compute. The same install also splits your Cortex AI bill by service, user, and model.

The Warehouses guide covers which warehouse classes Auto Tune can manage and the grant a warehouse sometimes needs first.

Talk to us about your warehouse

Frequently Asked Questions