Skip to content


Portal is a virtual private server that is marketed directly to consumers. You can write Portal apps that run on users' Portals. They are as versatile as web-applications and as private as locally installed apps.

Portal Architecture

A Portal-app runs on a user's personal Portal and is accessed via any device that the user has paired with their Portal, we call them terminals.

You can write your own Portal app and have users install and run it. Since Portal is based on well-established concepts and technology, this is very easy and straightforward.

How to think about your App

When developing a Portal-app you need to think a little differently about it compared to web-apps, desktop applications or mobile apps. A Portal-app has a unique combination of features and paradigms.

As it runs on a Portal which is a virtual machine on cloud infrastructure, it has the benefits of the cloud:

  • your app can be always on and always online, which is great for serving content like a blog or continually monitoring something like sensor readings,
  • your app is present on all the user's terminals, so you can create an omni-device experience, making it equally mobile for a smartphone and complex for a desktop computer or even combine multiple terminals simultaneously in new and unique workflows,
  • your app keeps its single source of truth on the Portal.

However, since a Portal is a single user's private space, a Portal-app also has aspects of a local application:

  • each running instance serves a single user, there is no user management,
  • there is a local file-system on the Portal that belongs to the user and to which your app can request permission,
  • the infrastructure that runs your app is already there, no need to think about hosting.

What the Portal does for you

The Portal core software stack that manages the whole Portal including your app already does a lot of things for you. Things that usually you would have to do yourself. For example:

  • Encryption and certificates
  • User management and authentication
  • Contact lists/friend lists
  • Hosting
  • Backups
  • Compensation/Payment


A Portal is not rocket science. We use lots of established technology, not only to make our own lives easier and development quicker but also to make Portal more reliable and secure and to make your life as a Portal-app developer simpler: you have to learn only very few new concepts to get started.

A Portal app is published as a Docker image containing a web server that listens for HTTP and serves the static and dynamic content that makes up your app's GUI. The HTTP endpoint is routed and authenticated by Portal, so there is no need to concern yourself with that. When a user installs your app, it will be available at a subdomain of the user's Portal: <app-name>.<portal-URI>. It will only be accessible from the user's paired devices.

Giving your app more capabilities is easy. You can request a part of Portal's file-system or add views that are public or only accessible to peers or listen and react to Portal-wide events.