Glossary

This page defines concepts in Trelae and how they relate to each other.

Project

A project is the highest unit of organization. It is the first thing you must create to start using Trelae. All usage and billing is associated with a particular project.

You can invite members to a project and create API keys to start building apps on Trelae.

Namespace

Namespaces are the next level of organization within a project. You can create any number of namespaces you need. All files that you upload have to go into a particular namespace. It allows you to isolate data, and apply different configurations as required.

Namespaces have a name that you can define. It is only meant to be a label for you to identify later. It does not need to be unique. You can also specify a region that determines where your data is stored. You can also specify if the namespace will be public or private (default). Private namespaces allow you to have full control over data access. Public namespaces receive a public URL that allows anyone in the internet to access files within it.

File

Files are the core object that you will deal with. We support all file types and sizes upto 5TB.

There is no concept of a folder or directory, however you can simulate this by specifying a location for each file. By default, each file goes into the / location. You can change this as you require. Later when you query files, you can use the location to filter out files.

Folder

Folders are virtual containers that help you organize files using a familiar path structure.

Folders do not store data themselves — they exist to group files by location. You can create folders ahead of time or let them appear automatically when you upload files with paths like images/ or projects/reports/. Deleting a folder removes all files and sub folders under that path.

API key

API keys are tokens you can generate that authenticates and authorizes access to the Trelae APIs. API keys are project specific.