Pricing

Pay for what runs.

No seat licences. No minimum commitment. Interlaken meters the resources you actually have running, charges by the hour, and sends one itemized invoice a month.

Get started See the rates

Metered: every minute Every live resource is sampled and accrued into the current month.
Billed: by the hour Pro-rated from the time actually accrued. Ninety minutes costs ninety minutes.
Invoiced: once a month One itemized invoice per billing account. Credits are applied first.
Elapsed: 00:00:00.0 Time is the unit every line on this page is measured in.

per instance-hour per GiB-month per GiB per million tokens per hour no minimums one invoice

01 / 04 Rate table

Every line, its unit, its rate.

Everything Interlaken Cloud can bill you for, in the unit it is measured in. The figures arrive from the platform API when this page opens — nothing here is typed in by hand.

01 08

Compute

Virtual machines, microVMs and containers bill their instance type for every hour they run.

Usage rates for Compute, fetched live from the platform API.
Resource	SKU	Unit	Rate
VM · xsmall1 vCPU · 1 GB RAM. The size every agent sandbox boots.vm-xsmallper instance-hour	vm-xsmall	per instance-hour	Rate not published yet
VM · small1 vCPU · 2 GB RAMvm-smallper instance-hour	vm-small	per instance-hour	Rate not published yet
VM · medium2 vCPU · 4 GB RAMvm-mediumper instance-hour	vm-medium	per instance-hour	Rate not published yet
VM · large2 vCPU · 8 GB RAMvm-largeper instance-hour	vm-large	per instance-hour	Rate not published yet
VM · xlarge4 vCPU · 16 GB RAMvm-xlargeper instance-hour	vm-xlarge	per instance-hour	Rate not published yet
VM · 2xlarge8 vCPU · 32 GB RAMvm-2xlargeper instance-hour	vm-2xlarge	per instance-hour	Rate not published yet
VM · 4xlarge16 vCPU · 64 GB RAMvm-4xlargeper instance-hour	vm-4xlarge	per instance-hour	Rate not published yet
Container · small1 vCPU · 2 GB RAMct-smallper instance-hour	ct-small	per instance-hour	Rate not published yet
Container · medium2 vCPU · 4 GB RAMct-mediumper instance-hour	ct-medium	per instance-hour	Rate not published yet
Container · large2 vCPU · 8 GB RAMct-largeper instance-hour	ct-large	per instance-hour	Rate not published yet
Container · xlarge4 vCPU · 16 GB RAMct-xlargeper instance-hour	ct-xlarge	per instance-hour	Rate not published yet
Container · 2xlarge8 vCPU · 32 GB RAMct-2xlargeper instance-hour	ct-2xlarge	per instance-hour	Rate not published yet
Container · 4xlarge16 vCPU · 64 GB RAMct-4xlargeper instance-hour	ct-4xlarge	per instance-hour	Rate not published yet

02 08

Storage

Capacity held, per GiB-month, pro-rated across the real length of the month. Replicas count.

Usage rates for Storage, fetched live from the platform API.
Resource	SKU	Unit	Rate
SSD · 1 replicaBlock storage on SSD, no replication.ssd_rc1per GiB-month	ssd_rc1	per GiB-month	Rate not published yet
SSD · 2 replicasReplicated synchronously to a second host.ssd_rc2per GiB-month	ssd_rc2	per GiB-month	Rate not published yet
SSD · 3 replicasReplicated synchronously to two more hosts.ssd_rc3per GiB-month	ssd_rc3	per GiB-month	Rate not published yet
HDD · 1 replicaBlock storage on HDD, no replication.hdd_rc1per GiB-month	hdd_rc1	per GiB-month	Rate not published yet
HDD · 2 replicasReplicated synchronously to a second host.hdd_rc2per GiB-month	hdd_rc2	per GiB-month	Rate not published yet
HDD · 3 replicasReplicated synchronously to two more hosts.hdd_rc3per GiB-month	hdd_rc3	per GiB-month	Rate not published yet
Object storageS3-compatible buckets, per GiB stored.object_storageper GiB-month	object_storage	per GiB-month	Rate not published yet
Disk snapshotA point-in-time copy of a disk, per GiB held.snapshotper GiB-month	snapshot	per GiB-month	Rate not published yet
Machine imageA published golden image, per GiB held.imageper GiB-month	image	per GiB-month	Rate not published yet

03 08

Networking

Load balancers, addresses you hold, and traffic that leaves the platform.

Usage rates for Networking, fetched live from the platform API.
Resource	SKU	Unit	Rate
Load balancerPer managed load balancer, in any mode.load_balancerper hour	load_balancer	per hour	Rate not published yet
Public IPv4 addressPer allocated address, bound or not — an address you hold is one nobody else can have.public_ipper hour	public_ip	per hour	Rate not published yet
Public IPv6 addressA single address leased from the platform pool.public_ipv6per hour	public_ipv6	per hour	Rate not published yet
Public IPv6 prefixA /56 held by a VPC for as long as it owns it.public_ipv6_prefixper hour	public_ipv6_prefix	per hour	Rate not published yet
Egress trafficTraffic leaving the platform, per GiB.bandwidth_egressper GiB	bandwidth_egress	per GiB	Rate not published yet
Object storage egressTraffic leaving your buckets, per GiB.object_egressper GiB	object_egress	per GiB	Rate not published yet

04 08

Databases

Managed instances, per replica, for the hours they are up. The volume underneath is block storage.

Usage rates for Databases, fetched live from the platform API.
Resource	SKU	Unit	Rate
Database · small1 vCPU · 2 GB RAM, per replicadb-smallper instance-hour	db-small	per instance-hour	Rate not published yet
Database · medium2 vCPU · 4 GB RAM, per replicadb-mediumper instance-hour	db-medium	per instance-hour	Rate not published yet
Database · large2 vCPU · 8 GB RAM, per replicadb-largeper instance-hour	db-large	per instance-hour	Rate not published yet
Database · xlarge4 vCPU · 16 GB RAM, per replicadb-xlargeper instance-hour	db-xlarge	per instance-hour	Rate not published yet
Database · 2xlarge8 vCPU · 32 GB RAM, per replicadb-2xlargeper instance-hour	db-2xlarge	per instance-hour	Rate not published yet
Database · 4xlarge16 vCPU · 64 GB RAM, per replicadb-4xlargeper instance-hour	db-4xlarge	per instance-hour	Rate not published yet

05 08

Kubernetes

No line of its own. Worker nodes are billed as the machines they are, under Compute.

Usage rates for Kubernetes, fetched live from the platform API.
Resource	SKU	Unit	Rate
Billed under Compute

06 08

Deploy

The managed deploy server and managed WordPress sites. The apps themselves run on machines, disks and addresses billed under their own lines.

Usage rates for Deploy, fetched live from the platform API.
Resource	SKU	Unit	Rate
Deploy serverThe managed control plane your apps deploy through, billed as a medium database-class instance.db-mediumper instance-hour	db-medium	per instance-hour	Rate not published yet
WordPress siteOne flat line per managed WordPress site.wpsiteper instance-hour	wpsite	per instance-hour	Rate not published yet

07 08

Agents

Sandboxes for AI development agents — a microVM each, billed while it runs.

Usage rates for Agents, fetched live from the platform API.
Resource	SKU	Unit	Rate
Agent runtimeA microVM per sandbox, billed while it runs and idle when paused.vm-xsmallper instance-hour	vm-xsmall	per instance-hour	Rate not published yet

08 08

AI

Tokens through the platform's AI assistant. Per-model rates appear here when the API publishes them.

Usage rates for AI, fetched live from the platform API.
Resource	SKU	Unit	Rate
LLM tokensPrompt and completion tokens through the platform's AI assistant, per million.llm_tokensper million tokens	llm_tokens	per million tokens	Rate not published yet

02 / 04 Estimator

Sketch a month.

Move the sliders. Each line multiplies a live rate from the table by what you would hold. Where a rate is not published, nothing is estimated.

Machines

Running all month

Size

Count

Managed databases

One replica each, up all month

Size

Count

Block storage

GiB held for the month

Tier

GiB

Egress

GiB leaving the platform

GiB

Public IPv4 addresses

Held all month

Count

Load balancers

Running all month

Count

LLM tokens

Through the AI assistant

Million tokens

03 / 04 Billing

Three steps. Nothing to estimate.

None of them asks you to commit to anything in advance.

01 / 03

Metered every minute

A metering worker samples every live resource on your account on a short interval and accrues the time into a usage record for the current month. That is what makes a workload that lived for twenty minutes billable at all.

Compute stops accruing when it stops. Disks and reserved addresses keep accruing until you delete them — they are still being held for you.

02 / 03

Billed by the hour

Rates are quoted per hour — or per GiB-month for capacity — and pro-rated from the time actually accrued. Ninety minutes of a machine costs ninety minutes, not two hours.

The hour is the readable unit, not the rounding unit.

03 / 03

Invoiced once a month

When a month closes it becomes one itemized invoice per billing account: each resource, the quantity accrued, and the rate that produced the line. Credits are applied first; what is left goes to a saved payment method.

Credits, payment methods and past invoices all live in the console.

04 / 04 Questions

Asked before signing up.

An invoice that is not covered by credits is collected from a saved payment method. If it stays unpaid it is marked overdue and shown in the console well before anything changes. An account that remains unpaid has its public access cut — public addresses and gateways stop serving traffic — while your disks, data and configuration stay exactly where they are. Settling the balance restores access.

Metered since you arrived 00:00:00.0

The same lines, in the console.

Create an account and look around — the same resources, the same units, the same rates you see above, with your own usage against them.

Get started Talk to us

Pay for what runs.

Every line, its unit, its rate.

Compute

Storage

Networking

Databases

Kubernetes

Deploy

Agents

AI

Sketch a month.

Three steps. Nothing to estimate.

Metered every minute

Billed by the hour

Invoiced once a month

Asked before signing up.

01 How granular is the metering?

02 Do stopped resources still cost anything?

03 What does an invoice look like?

04 What happens if my credits run out?

05 Why do some rates show a dash?

06 Is there a charge for Kubernetes?

The same lines, in the console.