The user interface is still under development and therefore does not offer so many features yet. However, we are working on it to support more and more features. If you find ideas for new features or bugs post an issue in the GitHub repository.

Creating a service

Creating a service is the main task of the dashboard, as described in other parts of the documentation, an SLA definition must be created for it. This can be easily done using the various input fields in the dashboard.

To do this, first, create an application, then you can create a service in this application by entering the various values in the form. The dashboard then creates the SLA deployment descriptor based on your input and sends it to the root orchestrator.


Organizations ensure smooth collaboration within a team in Oakestra. Members of an organization have access to all applications created within that organization, and they can use the resources provided within the organization to deploy new services.

Root Organization

When the root orchestrator is started for the first time, a root organization is also created with the admin, and each user is automatically part of this root organization. However, users can also be part of other organizations. The root organization has specific properties. Unlike other organizations, where a user can view all applications within the organization and share resources, in the root organization, only the applications that a user has created can be viewed.


After a successful login, the user receives a JWT token that authenticates the user. The token contains the user’s roles and the organization ID in which the user is currently logged in. We distinguish between the following different roles.


The admin is created at the start of the root orchestrator. He can create new users, create organizations, add users to organizations and change settings in the complete system.

Organization Admin

A user with this role is the admin of an organization he can add new users to the organization and manage their roles within the organization.

Infrastructure Provider

A user with this role can add resources that can then be used to deploy applications there.

Application Provider

This is the default role of a user, he can create applications and services and manage them accordingly.

E-mail Configuration

The admin of Oakestra can configure an SMTP server in the settings.

If no SMTP server is configured, the official Oakestra mail service can be used in the future.

Currently, mails are sent in the following scenarios:

  • When creating a new user, the user receives a mail with the password previously set by the admin.
  • When changing the password of a user
  • And to reset the password of a user.

If nothing is configured, no mails are sent and the admin must reset the password for the user.