Skip to content

About

A cloud you can understand

Fog breaking over an alpine peak, black pines on a snow slope
46°41′ N · 7°51′ E

Most clouds ask you to learn them before they do anything for you: a hundred services, a vocabulary of acronyms, a bill that only makes sense in hindsight. Interlaken starts from the other end. Describe what you want to run and get a URL that answers.

Underneath that URL is real infrastructure — machines, private networks, replicated disks, managed databases — and none of it is hidden. The simple path is the default. The whole machine is still there the day you need it.

01 The name

Between two lakes

  1. 01 / 03

    A place named for where it stands

    Interlaken is a small place in the Central Highlands of Tasmania, Australia, whose name says exactly what it is: the ground between the lakes. A strip of level country between Lake Sorell and Lake Crescent, with the highland plateau stretching away on every side. Two bodies of water, one piece of level ground in between.

  2. 02 / 03

    The ground between two kinds of user

    That is the position the platform holds. On one side, the person who has never opened a terminal and wants a URL that answers. On the other, the systems engineer who wants to see the machines, the routes and the disks. Interlaken is the ground between them, and it runs the same way: you declare the state you want, and control loops keep taking steps towards it — reconciling, retrying, correcting drift — until what exists and what you asked for meet.

  3. 03 / 03

    The mark is that idea, drawn small

    The symbol in your browser tab is the same picture: two shores facing each other, and the bar of level ground where they meet.

02 What we believe

Four commitments

Opinions the product is built on. They are commitments about how we build, not claims about how big we are.

  1. 01

    Novices deserve real infrastructure

    Being new should cost you knowledge, not capability. The platform that answers a one-line description also runs private networks, replicated block storage, load balancers and Kubernetes clusters. You grow into it. You do not migrate off it.

  2. 02

    Boring reliability over shiny demos

    A demo has to work once, on stage. Infrastructure has to work at three in the morning with nobody watching. We would rather ship the unglamorous version that repairs itself than the impressive one that needs a human to nurse it back.

  3. 03

    You should be able to see how it works

    Every abstraction here opens. The URL you got from a prompt is backed by a machine you can list, a network you can inspect and logs you can read. Nothing is a sealed box you are asked to trust on faith.

  4. 04

    The bill should never be a surprise

    Usage is metered continuously and shown in the console as it accrues, not revealed at the end of the month. You should be able to answer “what is this costing me” without building a spreadsheet.

03 The company

Only what we can verify

We would rather leave this section visibly empty than fill it with things that are not true yet. Four blanks, named but not filled: each is completed here the moment it can be verified.

01 Legal entity Pending
Pending
02 Founded Pending
Pending
03 Team Pending
Pending
04 Headquarters Pending
Pending
Get in touch

Try it

Believe it after you try it

Sign up, describe something you want to run, and see what comes back. The beginner path and the full platform are the same account.

Get started See what the platform does