For teams with a warehouse bill

Stop renting the shape. Own the compute.

The SQL surface is worth paying for. The compute is not. Run it in your own account, on your own terms, and see it per query.

Join the waitlist or run it locally

01 / the problemYou are paying for the shape, not the engine.

A large part of a platform bill buys the SQL surface and the operational visibility, not the bytes scanned. The compute is the part you could run yourself, in your account, on spot capacity, metered by the second.

TODAY Managed platform credits Compute you actually use your own AWS account

02 / what changesSame facts, better surface

Today

  • Credits you have to forecast and explain
  • A bill that lags and cannot be attributed
  • Idle capacity you keep paying for

With Flashpoint

  • Your AWS bill, at per-second granularity
  • Live meters beside Cost Explorer
  • Suspend and compute stops

03 / how it worksThree steps

Size it

XS is one executor. Grow when a query needs it, shrink when it does not.

Run it

Metering starts at creation and is written per running warehouse, not per credit.

See it

The cost center fuses live meters with Cost Explorer and projects the month against a budget.

04 / questionsStraight answers

How is it priced?

Per compute-second, on your own AWS bill, only while a warehouse is running. There are no credits and no per-seat fees.

What am I actually paying for?

EC2 for the gateway, Fargate for the driver and executors when they run, and storage. All standard AWS line items.

Does suspending really stop the cost?

Compute stops. Storage and the always-on pieces continue, and the cost center shows both.

Can I see it before I commit?

Yes. Run it locally with the quickstart, or on your own account with the deploy guide.

Join the waitlist

Early access opens in batches. One email when a batch opens, nothing else. Or run the whole stack locally tonight.

One email when signup opens. Stored with our mailing provider, never sold or shared.