Introduction

A namespace is a logical container that helps you organize, isolate, and manage your files within a project. Think of a namespace as a dedicated space where related files live under a common label and configuration.

Namespaces make it easy to separate files based on purpose, environment, team, or any structure that fits your workflow. For example, you might create separate namespaces for development, staging, and production, or for different clients or projects.

Every file you upload must belong to a namespace. This keeps your data structured, ensures isolation, and gives you fine-grained control over storage regions and access.

A namespace can be either private or public:

• Private namespaces keep your files secure by requiring signed URLs for access. These URLs can expire and restrict permissions.
• Public namespaces generate a shareable link that anyone on the internet can use to access the files — perfect for assets you want to share publicly.

You can also set a region for each namespace to control where files are physically stored — by default, us-east-1 (AWS) is used, but you can choose another if needed.

Each namespace has a name, which acts as a label to help you identify it later. Names don’t need to be unique, so you can use patterns that work for your team.

Namespaces can be created using the project dashboard UI or programmatically via the API or SDK — giving you the flexibility to manage your data however you prefer.