Features

Twelve blocks that make up the work with files. Some belong to the core and are available from day one, the rest grow on top of the same data model without rebuilding the foundation.

The core, from day one

An object with a permanent identifier, a holder table, the quota owner, permissions on objects and integration permissions, the storage contract and file delivery through a short signed link. This part cannot be added later: rebuilding it means rewriting the data access layer in every product at once.

The object and file_id as a permanent identity
Holders: direct ownership and product bindings
Quota owner and a usage ledger keyed by A3.ID
Permissions on objects and integration permissions
A contract of four methods: put, get, bind, unlink
One response format and a short signed link

Core, from day one

File identity

file_id is created once and never changes. The link to the content is short lived and is issued again each time with permissions checked.

Learn more

Core, from day one

Company, employee and project drives

A physical tree curated by people. System attachments from products never land in it and live on a separate axis.

Learn more

Core, from day one

Product bindings

Several entities from different products hold one object. These are not copies: the weight is counted once and unlinking is addressed.

Learn more

Core, from day one

Permissions on files and folders

A3.Drive is the single source of truth about access. Products add meaning on top, but the question of who sees an object is answered here.

Learn more

Core, from day one

Space, quotas and cleanup

You can see what fills the space and what can be removed safely. System storage is a separate axis rather than something that disappears from the ledger.

Learn more