Introduction to Hippo: the WebAssembly PaaS

deislabs.io
4 min read
fairly easy
Hippo makes it easy to run applications and services at scale
The Deislabs team is really excited about WebAssembly. In fact, we've been experimenting and sharing our knowledge by developing new technologies in the WebAssembly space, such as Krustlet, WAGI, bindle, yo-wasm, and wasi-experimental-http.

While experimenting with these new technologies, it became clear that we need to make it easy for developers to deploy and test out their new ideas. Today, we're thrilled to announce a new project. We call it Hippo, an Open Source self-hosted Platform as a Service (PaaS).

Hippo takes a fresh spin on the PaaS ecosystem, taking advantage of the technology WebAssembly brings to the space.

Hippo works like this: An application is packaged as a bindle. Bindles are collected together in a bindle server that you can search. Hippo uses bindle under the hood for storing and organizing applications.

Hippo uses a concept called "Channels" to perform automatic deployments of your applications. More on that later.

Using the hippo command line interface, you can upload new releases or prepare a bindle for local development. In the future, you can use this CLI to create applications, configure channels, gather logs, attach TLS certificates, and other commands you'd expect to use with a PaaS.

Hippo provides a web interface for users to register new accounts, access their applications, and create new environments for testing.

.

Hippo's Goals

We built Hippo to help with two things.

First, we want to make it simple to develop applications and services. Hippo provides a suite of tools that make it easy to scaffold and test out new ideas. We also make it easier for newcomers to start writing…
Read full article