Storage and egress
Included Tensorant storage and monthly egress, overage pricing from credits, and how to connect your own S3 storage bucket for free.
Your data has to live somewhere. By default it lives in Tensorant storage, and Tensorant charges for what you keep there past the 5 GB every organization includes, and for data that leaves it for you, such as downloads, past a monthly allowance. If you connect your own storage instead, Tensorant does not measure or charge anything for storage or egress. This page lists the prices and says exactly what is counted.
Where your data lives
- Tensorant storage is the default. Tensorant keeps your sources, examples, images, versions, evaluation answers and adapters, separately for each organization. Storage and egress are metered and charged from credits.
- Your own S3 bucket is the privacy option. It is available to every organization, free, with no subscription. Your data stays in your cloud, and Tensorant never meters, caps or charges it. See Connect S3 storage. Your storage provider bills you for the bucket and its requests and transfers.
- A RunPod network volume in your own RunPod account is not metered or charged by Tensorant either, and RunPod bills it. A RunPod network volume comes with your RunPod account, so it needs the Own compute subscription, or works until 31 Dec 2026 if you connected RunPod before the change. See Your own accounts.
Each training run, trials included, also keeps the files its machine reads: the job bundle, which holds a copy of the run's data, and the runner program. They stay after the run ends, and in Tensorant storage they count toward what you store. In Tensorant storage a finished run keeps one copy of its adapter or model: the checked one you download and serve. In your own bucket or volume Tensorant leaves both files, for you to keep or delete.
Prices
| What | Amount |
|---|---|
| Storage included on every organization | 5 GB |
| Storage past what is included | $0.10 per GB a month |
| Egress included on every organization | 5 GB a month |
| Egress past what is included | $0.05 per GB |
- Storage is measured every 5 minutes, and each measurement charges 5 minutes of the part above what is included. The monthly price is spread over a 720-hour month, so an hour costs 1/720 of it. Every organization includes 5 GB. Enterprise includes what its plan sets, and a Pro subscription keeps its 50 GB until it ends (see If you were on Starter or Pro).
- Egress is counted each calendar month in UTC, starting again on the 1st. Every organization includes 5 GB a month, and the rest is charged per GB.
- A GB is 1,000,000,000 bytes everywhere: in these prices, in the allowances and in the console. Sizes show one decimal, such as 3.4 GB.
- Charges come out of your credit balance as one Storage line and one Egress line for each day, which you can read under Plan and billing.
Storage and egress are separate from GPU time and the training-token fee. Compute is in GPU pricing, and everything else you pay for in Pricing and billing.
What counts as egress
Egress is data leaving Tensorant storage on your behalf. These count:
- Downloads from the console, the API, the CLI or an agent over MCP: adapters, bundles, dataset files, splits and reports, whether Tensorant gives you a download link or streams the file to you.
- Pushes to Hugging Face from Tensorant storage, counted once for each push by the size of the archive.
- Files handed to a machine in your own GPU account when a run launches: the dataset bundle, the runner and a starting adapter, counted once for each launch.
A download counts in full when it is handed out, at the size of the file, whether or not it finishes. A download you retry counts again, because the file is handed out again.
These do not count:
- Console pages and API answers, which are small JSON.
- Answers from your published models.
- Tensorant compute machines reading and writing your organization's data.
- Imports and uploads into Tensorant storage.
- Project images shown in the console.
Without credits
An organization without credits cannot buy any, or has run out. It is held to what is included:
- A write that would take storage past the included amount is refused. Uploads, Hugging Face imports, generation, new versions, run launches and evaluations are checked this way. Small edits and work already queued or running are not.
- A download that would take egress past the monthly allowance is refused until the next month.
- Both come back as HTTP
402with the codestorage_limitoregress_limit. The message says how much you store or took, what is included and what to do: add credits, or connect your own storage. The console, the CLI and agents over MCP show that message. - Nothing is charged for a refused action.
With credits, a download whose egress past the allowance costs more than the balance is refused the same way, so a download never takes the balance below $0.
The first time an organization without credits reaches its storage limit or its egress allowance in a month, its owners get an email. See Emails.
At $0
If an organization holds more than is included and its credits reach $0, its storage is frozen, never deleted:
- New writes past the included amount and downloads past the allowance are refused. Work already running finishes.
- Storage past the included amount keeps being charged if the organization can hold credits, so the balance can go below $0, down to -$10, where storage charges stop. Owners get warning emails. Add credits to continue.
- Tensorant never deletes your data because of an unpaid balance. When a larger allowance ends without credits, such as a Pro subscription's 50 GB with 60 GB stored, the organization is frozen at its new limit: writes are refused, nothing is charged unless the organization is approved for Tensorant compute, and nothing is deleted.
Credits and the hours they cover include what storage costs an hour. See Credits.
Move to your own storage
Any organization can switch to its own S3 bucket, free and without a subscription, but only while it has no projects, because changing location does not move data. A RunPod network volume comes with your RunPod account, so it needs the Own compute subscription, or works until 31 Dec 2026 if you connected RunPod before the change. If you already have projects, keep using Tensorant storage, delete what you do not need, or start a new organization on your own bucket. Steps are in Connections and Connect S3 storage.
Limits
| Limit | Value |
|---|---|
| Storage measured | Every 5 minutes; 5 minutes that could not be measured are not charged |
| Egress allowance | Calendar month in UTC |
| Organizations not metered | Shared organizations, and organizations with their own storage |
Need a hand? Visit troubleshooting