Produkt

Pricing without surprises: how Kepler’s pricing model works

The cloud bill shouldn't be a mystery. We build pricing on predictability, with no penalty fees for sending out your own data or for leaving.

Many cloud bills are hard to predict because the pricing model is built to be that way. Egress fees, exit fees and a swarm of line items turn the total into a surprise. We took a different route.

Predictability as a principle

Price should reflect actual resource usage, not a maze of add-on fees. We aim for a model where you can work out what a setup costs before you launch it, and where the bill contains no items whose only purpose is to make leaving expensive.

No penalty for owning your data

Taking out your own data shouldn’t cost extra. High egress fees are, in practice, a lock-in mechanism dressed up as pricing. With the EU Data Act, that mechanism is also becoming a compliance problem — we chose not to build it in from the start.

A pricing model that punishes exit is lock-in with a nicer name.

— from Kepler’s product principles

Start before you pay

You get a running VM before you pay a cent. No lock-in period, no hidden staircase. See current prices on the pricing page and do the math yourself.

Bygg på ett moln du faktiskt äger.

Ingen bindningstid. En körande VM innan du betalar en krona.