Storage
Files, providers, spaces, quotas
Storage isn't part of this workspace
This org has no storage tenant. Add the Storage product to your plan to enable it.
Plan & Invoices Files
—
across all collections
Used
—
—
Quota
—
—
Uploads
—
— in
Downloads
—
— out
Deletes
—
files removed
Traffic window
all time
ledger figures
Quota usage —
—
Traffic by product from the operations ledger
| Product | Uploads | Downloads | Bytes in | Bytes out |
|---|---|---|---|---|
| Loading… | ||||
By collection whole org
| Collection | Files | Size | Share |
|---|---|---|---|
| Loading… | |||
Recent files newest first
| File | Product | Collection | Space | Size | Created |
|---|---|---|---|---|---|
| Loading… | |||||
Spaces
A space is a container for ONE of your customers: it has its own storage quota and its own
API keys, and every upload, download and byte is metered per space. Hand a space key to a
customer integration and it can only ever see that space.
| Space | Name | Used | Quota | Files | |
|---|---|---|---|---|---|
| Loading… | |||||
Create a space
Lowercase, digits, dashes. Fixed once created.
API keys
Keys are scoped to one space and shown exactly once at mint time - only a hash is stored.
Pick a space above to manage its keys.
New key - copy it now, it is never shown again
| Name | Key | Scopes | Status | |
|---|---|---|---|---|
| Pick a space | ||||
How a customer uses a space key
The key goes in
X-Api-Key on /v1/files; the service pins every call to the key's
space. The org must be resolvable - in the host, or as X-Org-Slug through the API gateway.
Without it the key cannot be found and the answer is 401 Invalid API key.
GET /v1/files/lists only this space -?space=is ignored.- A file in another space is
404, not403; uploading withspace=otheris403. - Uploads with no
spacefield land here. Read-only keys cannot upload; revoked keys are401. /v1/admin/*is never reachable with a space key.
Storage providers
Register each backend once - FlowPrime-managed storage, your own S3/MinIO/R2 bucket, or an
Azure Blob container. Credentials are encrypted at rest and never shown again. New uploads
land on the default provider unless a routing rule
says otherwise; existing files always stay readable from the provider they were stored on.
| Provider | Type | Target | Cap | Status | |
|---|---|---|---|---|---|
| Loading… | |||||
Add a provider
Account-key connection string; needed for signed URLs.
Routing rules
Route NEW uploads by product and/or space to a registered provider; the lowest priority
number wins and anything unmatched lands on the default provider. Rules never move
existing files - reads always follow the provider a file was stored on.
| Priority | Product | Space | Provider | |
|---|---|---|---|---|
| Loading… | ||||