A3.Drive is part of the platform and every customer has it. Paid axes are added on top and do not overlap, so the same thing is never charged twice.
Five independent axes. The size of a physical object counts once, the number of bindings is a separate axis, and growth in one does not inflate the other.
The sum of physical objects that have at least one user binding. Duplicates linked instead of copied do not double the bill.
How many versions are kept and for how long. Frozen versions under a signature follow the document workflow rules, not the plan period.
The integration load: how many product entities hold files. This axis reflects the storage working as a shared platform layer.
The number and validity period of permissions issued to products. A3 products register in the registry on the same terms as external ones.
Public links and video conversion. Exceeding a limit returns a dedicated response code rather than a generic error.
The limits below set the order of magnitude. Exact figures and the price are fixed in the commercial offer for the volume and region of your account.
Included in the platform
Available to every A3 customer
The core contract, personal drives for employees and a company drive. Enough for products to stop storing files themselves.
LimitsSubscription
Billed per user per month
Working together: project drives, public links for outside parties and migration of archives from external clouds.
LimitsSubscription
Billed per company with add on volume
The full set for a working contour: online editing, locks, video conversion and managed integration permissions.
LimitsOn request
A separate installation in the country you need
A dedicated regional cluster, your own object storage and retention periods matched to the regulator.
LimitsQuota and storage usage are tracked per company account in A3.ID. Employees sign in to the storage through it, and the storage region is tied to the account, not to where a request comes from.
Once. The quota counts the physical object, not the bindings. Three entities from three products are three holders of one object, and its size is counted a single time.
No, as long as only system bindings hold them. They do not fall out of accounting though: system storage is counted separately, with its own limit per product and its own retention period. Once an employee moves a recording into “My files”, the object starts counting toward the user quota.
The account first moves to read only: uploads are blocked, all data stays in place and remains available. If payment still does not arrive, space is freed in a published order: trash, system storage above its limit, old versions, files not opened for a long time. The order is known in advance rather than a surprise.
No. The retention period outranks non payment: a document with an unexpired legal retention period is not deleted even if the account stays above its limit because of it. In that case the account simply remains read only.
Yes. The region is set when the account is created and does not change afterwards without an explicit migration procedure. Backups stay in the same region, and object identifiers are global, so a move creates no conflicts.
Its bindings become orphaned and the files stay while other holders remain or a retention period applies. The link back into the entity stops working, and the quota owner is reassigned to another product or to the shared account pool.
Tell us the expected volume, the number of employees, the products that will hold files and the account region. We will come back with a breakdown by axis and a rollout plan.