Need help? Check our guides or contact support.
Storage Billing
Personal uploads: each user gets 1 GB of free storage. Organisation library: the organisation gets 1 GB free in total (shared across the org), billed from the organisation wallet. Beyond those allowances, storage costs accrue daily from the appropriate user or organisation wallet (see below). When a public resource is saved by multiple parties, the cost is automatically shared.
How storage billing works
1 GB included per user, at no cost
Every user account includes 1 GB of free upload storage. This covers typical usage — documents, images, small videos, and course materials — without any token cost.
1 GB included for the organisation (shared)
Files attributed to the organisation library (organisation wallet) share one 1 GB free allowance for the whole organisation — not 1 GB per member.
Uploads blocked (not deleted) when over the free tier
If you exceed 1 GB and have no token balance to cover storage costs, new uploads are blocked. Existing files are never deleted — they remain accessible. Once you top up your token balance, uploads are unblocked immediately.
BEYOND THE FREE TIER
Storage beyond your free allowance (1 GB per user, or 1 GB total for the organisation) is charged at ~4 tokens per GB per month (0.04€/GB/month)
Daily
Billing cycle
Runs at 3 am UTC via scheduled job
1/30th
Daily cost fraction
Monthly cost ÷ 30 days charged each day
≥ 1
Token flush threshold
Micro-costs accumulate until 1 full token
Micro-cent accumulation
Small files accrue costs in fractions of a token. These micro-amounts are tracked in an accumulator per wallet and only converted into a token transaction once the total reaches 1 token (0.01€). This prevents a flood of tiny transactions for every small file.
ikigize doesn't penalise uploaders when their public resources benefit others. Storage costs are shared fairly across every entity that saves a resource to their library.
PUBLIC RESOURCE — COST IS SPLIT
Uploader (user wallet)
¼ of cost
Course owner wallet
¼ of cost
Campus owner wallet
¼ of cost
Org owner wallet
¼ of cost
Each share is debited from the owning user or organisation wallet (not a separate “course wallet” or “campus wallet”).
PRIVATE RESOURCE — UPLOADER PAYS ALL
OWNER WALLET SETTLEMENT
Each portion of a public resource's storage cost is settled against a user or organisation wallet — whoever owns the campus, course, session, or task library that holds the share. There is no separate wallet per campus or course.
- Private files— full cost to the uploader's user wallet.
- Public shares— each library holder's portion debits the owner wallet for that entity (uploader, course owner, campus owner, or organisation as applicable).
The free tier
- User uploads: the first 1 GB of files billed to your user wallet is free — no tokens required.
- Organisation library: the first 1 GB of storage attributed to the organisation wallet is free for the organisation as a whole (not per member).
Once you exceed the relevant free allowance, additional storage accrues a small daily charge based on how much space your files occupy beyond that tier.
Rate: ~4 tokens per GB per month beyond the applicable free allowance
Billing: Daily at 3:00 am UTC (1/30th of the monthly rate per day)
Daily billing cycle
Storage is not charged in one lump sum. Instead, the platform runs a billing cycle once per day and deducts a micro-amount — 1/30th of the monthly rate — for each GB over the free tier. This means costs accumulate gradually and your balance is always an accurate snapshot of your actual usage.
If a bill amounts to less than one full token in a given day, the fractional cost is tracked and rolls over until it accumulates to a full token.
Files already uploaded are never deleted due to storage billing. If your token balance hits zero, new uploads are blocked until the balance is restored — existing files remain intact.
Cost-splitting for public resources
When a resource is made public and saved to a course, campus, or organisation library, the storage cost share for each “holder” is calculated — for example ¼ each when all four contexts apply:
| Share attributed to | Charged to |
|---|---|
| Original uploader | The uploader’s user wallet |
| Course library | The owning user or organisation wallet for that course |
| Campus library | The owning user or organisation wallet for that campus |
| Organisation library | The owning organisation’s wallet |
Campuses, courses, sessions, and tasks do not have their own wallets. Each share is billed to whoever owns that entity.
If only some parties hold the resource, the cost is divided equally among those who do. A private file is charged entirely to the uploader’s user wallet.
This means that popular public resources become progressively cheaper per holder — the more widely a resource is adopted, the lower the individual cost.
Upload blocking
If the wallet that must pay cannot cover pending storage costs, future uploads may be temporarily blocked where required. To restore upload access, purchase additional tokens, receive an allocation, or free up storage by deleting files.
Next steps
- Wallets & billing — how owner wallets relate to hosting and storage
- Allocation & Limits — move tokens from an organisation wallet to members
- AI Token Usage — how AI costs work alongside storage