Skip to content


Applications play a vital role in Taubyte’s environment as they act as containers grouping together various resources. They essentially define the scope of accessibility and interactions between these resources.

In Taubyte, an application’s boundary creates a clear demarcation that separates its resources from others. For instance, a function that belongs to ‘AppA’ will not have access to a Database in ‘AppB’. This encapsulation helps manage permissions and control interactions between different resources, ensuring an efficient and secure environment.

However, it’s worth noting that resources not associated with a specific application, also known as ‘global’ resources, can be accessed across applications. A function in ‘AppA’ can access a ‘global’ database as these resources are not bounded by any specific application.

In the configuration repository, each application is represented by a folder under the ‘applications’ directory, and it’s characterized by a YAML file that might look something like this:

id: QmT7wxkYsNDz6XC1vwXGoQCWRQjSauh6rCZ6cM62zPyNSN
description: ""
tags: []

The ‘id’ field is a unique identifier for the application, the ‘description’ provides a brief explanation about the application, and ‘tags’ are to be used for provisioning.

This structure makes it easier to manage and organize the project’s resources effectively, ensuring a clean, intuitive, and secure development environment. Remember, the way you structure your applications in Taubyte plays a key role in how resources interact and how effectively you can manage your project.