Pricing and billing
mountable.io usage prices for storage, downloads and operations, monthly spending caps per filesystem and organisation, and how billing works.
mountable.io invoices storage, downloads and stored file count after each month ends. There is no free allowance: all usage is billed, from the day the organisation saves a payment method.
mountable.io prices
| Usage | USD | EUR |
|---|---|---|
| Storage | $0.20 per GiB-month | €0.17 per GiB-month |
| Downloads | $0.02 per GiB delivered | €0.017 per GiB delivered |
| File count | $0.50 per million entries/month | €0.425 per million entries/month |
A GiB is 1,073,741,824 bytes (2³⁰), the unit df -h and filesystem
quotas use. Storage and entry counts are averaged over
the calendar month; downloads are bytes delivered by the gateway. The entry
count includes directories. File count pays for metadata capacity; storage
pays for retained content, and downloads pay for serving it. Uploads and
individual filesystem operations have no separate fee. Prices exclude taxes.
An account can own ten organisations, and an organisation can have up to 10,000 filesystems. Downloads have no cap once a card is saved. The limits page states the caps, including the copy-out limit while a bill is overdue.
Downloading a full 100 GiB file costs €1.70 (USD 2.00). Opening a file or reading a range does not imply downloading it all. Local cache hits do not download it again; another remote read can incur another charge.
Storage/file counts are sampled daily. A missing sample reuses the last recorded value, including a previous-month sample. If no earlier sample exists, the first available sample backfills from filesystem creation, never before the organisation's card-saved date. Until any sample exists the estimate can be incomplete and change when that first sample arrives. An estimate can be higher or lower than actual usage during a gap. Month-to-date averages use elapsed days; a closed month's averages use all its calendar days. Deletion takes a final sample; storage and file-count charges stop after the deletion day. Downloads use recorded delivered bytes.
Spending caps
An owner or admin can set a monthly spending cap on the organisation's Billing page after saving a payment method. Enter the amount in the organisation's USD or EUR currency and choose Save spending cap. The same limit repeats each calendar month in UTC. There is no monetary cap until you set one; choose Remove spending cap to remove it.
The cap covers this month's usage charges before tax. Earlier invoices, balances carried from other months and taxes remain payable. API keys and agents cannot change your cap. To cap each end user of your app separately, set a cap per filesystem: see limits per end user.
Files keep costing money after workers disconnect. To keep them stored, the budget reserves a full month at each filesystem's peak stored size and file count, plus downloads. Uploads reserve room before they start; unused room returns when a smaller upload completes. Accepted creates reserve file-count room until their result is confirmed. The Billing page shows how much is Available for new usage and the minimum cap. Your measured invoice estimate can be lower than the amount counted toward the cap.
For example, 10 GiB stored for a full month reserves $2.00 in USD, before file count and downloads. A $5.00 cap leaves the difference available for more usage. The invoice still uses the storage and file-count measurements described above. When a creation-day sample exists, it also records later writes that day at their measured peak, even if the cap is removed, so an initially empty filesystem does not get free creation-day usage. Caps create this initial sample; the daily job can also create one on an uncapped filesystem’s creation day. Later days keep the normal daily schedule.
If an operation would exceed the cap, new charge-increasing usage pauses.
Files stay stored. HTTP file/chunk requests return 402 spending_cap_reached;
mounts return ResourceExhausted with the same code. Mounted lookups, listings
and change notifications can contain downloadable data, so traversing a mount
can pause too. You can still use the console/control plane and HTTP deletion
routes to clean up. Deleting files does not free this month's peak reservation.
Raise or remove the cap to resume on the next operation; existing sessions do not need to be reissued. At the start of the next UTC month, the reservation is recalculated for retained files and any in-flight work. If that already fills the cap, raise it before adding usage. An upload/create whose outcome is unknown can conservatively keep budget reserved until its result is reconciled; contact support if reserved budget appears stuck.
Compared with mounted GCS, S3 and Azure Blob Storage
Checked 10 October 2026. Public USD pay-as-you-go first-tier rates, before allowances, taxes, discounts and trial credits. These are object stores accessed through mount adapters, with different filesystem behaviour and redundancy from mountable.io.
| Charge / setting | mountable.io | GCP | AWS | Azure |
|---|---|---|---|---|
| Service and mount | mountable.io filesystem | GCS Standard + GCS FUSE | S3 Standard + Mountpoint/s3fs | Blob Hot + BlobFuse2 |
| Configuration | USD price list | Iowa, single region, flat namespace | Northern Virginia, general-purpose bucket | East US, LRS, flat namespace |
| Storage / month | $0.20/GiB | $0.020/GiB | $0.023/GiB, first 50 TiB | $0.0208/GiB, first 50 TiB |
| Monthly stored entry count | $0.50/million average entries | No basic count fee | No basic count fee | No basic count fee |
| Read/metadata requests / million | Included | $0.40 Class B | $0.40 GET/other Tier 2 | $0.40 Hot read |
| Write requests / million | Included | $5 Class A | $5 PUT/COPY/POST | $5 Hot write |
| List requests / million | Included | $5 Class A | $5 LIST | $5 list/container |
| Internet downloads, first paid tier | $0.02/GiB | $0.12/GiB to US/Europe, first 10 TiB | $0.09/GB, first paid 10 TB | $0.087/GB, next 10 TB; Premium Global Network |
| Incoming traffic | Included | Free network; writes billed | Free network; writes billed | Free network; writes billed |
| Additional retrieval fee for selected class | None | None | None | None |
| Minimum storage duration for selected class | None | None | None | None |
Units: mountable.io, GCP, AWS and Azure all price storage per GiB, so the storage rates compare directly; GCP and AWS bills label it GB. AWS and Azure list Internet transfer per GB, and Azure specifies 1 TB = 1,000 GB. A GiB is about 7.4% more than 1,000,000,000 bytes.
mountable.io's storage rate is higher than these basic object-storage rates; its paid Internet-download rate is lower, with no per-request charge. Total cost depends on storage, reads, metadata activity, caching and compute location.
Allowances and compute location
| Case | mountable.io | GCP | AWS | Azure |
|---|---|---|---|---|
| Monthly usage allowance | None | Eligible Always Free: 5 GiB-month, 5,000 Class A, 50,000 Class B in selected US regions | New-account credits excluded here | Trial offers excluded here |
| Internet-download allowance | None | 100 GB from North America per qualifying destination; free-tier conditions apply | First 100 GB shared across AWS services/regions, excluding China/GovCloud | First 100 GB/month, not per mount |
| Reads by same-region/location cloud compute | Normal download rate | Free transfer within same location under GCS rules | Free transfer to AWS services in same region, including another account | Free transfer between Azure services in same region |
GCS Always Free usage is aggregated across us-west1, us-central1 and
us-east1; qualifying transfer excludes Australia and China. Laptop reads,
other clouds and external sandboxes can incur Internet egress. Request charges
remain when transfer is free. Cross-region traffic uses different rates.
Azure ISP-network routing instead costs $0.08/GB from North America/Europe;
the table uses Premium Global Network pricing.
Mount software has no separate provider fee, but its API calls are billed. One file action may generate multiple calls; GCS FUSE documents several object lookups/inserts for some actions. Caching, ranges and multipart uploads affect counts. Cooler tiers, optional indexing, CDNs and cache disks can add charges.
The adapters have different rename, overwrite, locking and consistency limits. S3 Standard spans multiple availability zones; Azure LRS is locally redundant. mountable.io's current stage has no live volume replication and uses backups. Compare our filesystem contract as well as prices.
Comparison sources
Retrieved 10 October 2026. Recheck for your region and account:
- GCS pricing and GCS FUSE operation mapping.
- S3 pricing, US East storage/request rates, US East transfer rates, and Mountpoint semantics.
- Azure Blob pricing, Retail Prices API, Blob units, bandwidth pricing, and BlobFuse2.
Azure storage/request rates were read from the Retail Prices API for
Storage, eastus, Consumption, General Block Blob v2, SKU Hot LRS:
Hot LRS Data Stored (tier 0), Hot Read Operations, Hot LRS Write Operations,
and LRS List and Create Container Operations.
Card and currency
When billing is configured, owners/admins save a payment method (a card,
Apple Pay, Google Pay or Link) before creating their first filesystem, and
mounting also needs one. Payment details go to Stripe. Without a saved payment
method the API returns 402 payment_required with a url to the Billing page
for the human. Usage is billed from the day the payment method is saved, and
saving it sends the person who saved it a welcome email that links to the
Terms. Opening or abandoning the form does not mark a
method ready: wait for the console's confirmation. If the form or confirmation
fails, use its Try again action, or contact support if it keeps failing;
creation and mounting remain gated until readiness is confirmed.
Only owners/admins can open Billing or manage the payment method. Members should contact an owner/admin when payment prevents mounting.
You choose USD or EUR when you add the organisation's first payment method, from any country. The console preselects EUR when your browser's time zone is in the EEA or Switzerland, and USD otherwise; switching reloads the secure card form. The currency stays the same afterwards; the console and the welcome email name it. VAT follows your billing address, whichever currency you pay in.
Invoices and unpaid balances
Once live billing begins, the previous month's usage is invoiced at the start of each month. Each invoice line is rounded up to the cent. A combined balance below €5/$5 carries forward until it reaches that amount. The Billing page shows month-to-date usage, the carried balance and recorded previous months. Each past month's usage charge excludes balances carried in from earlier months. Use Manage billing for Stripe's invoices and payment method settings.
An invoice unpaid 14 days after finalization suspends the organisation, and its owners get an email at each step:
- Read-only, for 14 days. Read-write mounts are refused and live read-write sessions end. Read-only mounts keep working, so you can still copy data out.
- Blocked, after 14 days. All mounts are refused and live sessions end. Files are kept.
- Terminated, 14 days later. The organisation is deleted and the agreement for it ends; amounts already owed remain payable. Its files are scheduled for erasure on or after 30 days after termination, subject to applicable retrieval requests and retention duties. Contact support for retrieval where the Terms and law allow.
Stages are processed by the billing job; a missed run or failed notice can delay progression rather than skip a notice. The console remains available until termination, including owner/admin billing and key management. The organisation's nonpayment notice links owners/admins to Billing; members are directed to an owner/admin.
During the first two steps, paying all overdue invoices lifts the suspension when payment confirmation is processed. An unpaid older invoice keeps it suspended even if a newer one was paid. Already-revoked sessions are not restored: create a new mount after access is available again. For retrieval and erasure after termination, follow the Terms and Privacy Policy; console deletion is not itself physical erasure.