Object storage
The Storage page shows each bucket’s total file count, including files in subfolders. A dash means the count is currently unavailable. Ornn drives use regional, standard-class object storage. Object storage is billed by calendar month (US Pacific time) for all data your organization stores in each location, in GiB-months (1 GiB is 1,073,741,824 bytes). A month’s charge for a location is the average GiB stored that month times its price:
Deleted files stay billed for 7 days after deletion. The Billing page shows
this month’s estimate so far, with the last measured day, and, from the 4th of
the next month (Pacific time), that month’s storage invoice by location. The
charge is per location. Usage that is reported after its month ends is on the bill of
the month in which it is reported, on its own line marked “reported late”. A
correction to measured usage is a Credit line. When credits cover a month’s
storage cost, the bill shows one Credit line equal to that cost and a total
of $0. Open a location to see an estimate per volume, with one Other data
row for the rest: deleted files kept for 7 days, uploads in progress, and
rounding. Volume amounts are estimates. Every member of the organization sees
the same bill.
Each volume shows its current name. A deleted volume is marked (deleted) and
keeps what it used before. Volumes with no usage that month are counted on one
line instead of listed.
Object-storage prices are subject to change.
Ornn shared filesystems support datasets, checkpoints, and shared home directories across nodes. Kubernetes and Slurm use them at
/workspace on Private clusters. See the access guide for your mode before provisioning.
Shared filesystem cost is based on provisioned capacity. An empty filesystem still uses that capacity. Detaching storage or tearing down a cluster does not delete the filesystem; review and delete unneeded storage separately after exporting your data. Do not treat ornn filesystems delete as a data-preserving detach. Confirm deletion and the end of charges with Ornn. Monthly reference prices below assume a 730-hour month.
Available Ornn tiers
Use these tier keys withornn filesystems deploy:
Available regions and accepted capacity depend on the selected tier. The reference tables include infrastructure tiers that are not all offered in Ornn’s provisioning controls. A listed region does not confirm that your reservation can attach storage there. Confirm the tier, region, capacity, and quoted rate with Ornn support before committing.
Reference service tiers
With custom performance enabled on the Zonal and Regional tiers, provisioned IOPS are decoupled from capacity and billed separately. You pay a per-instance fee plus a per-IOPS rate on top of the per-GiB price.
Instance pricing
Prices below are indicative estimates in USD per provisioned unit. Select a region to compare them. They are not a live quote or a promise of availability; confirm current Ornn rates before provisioning. N/A means the table has no rate for that item. Infrastructure pricing can change; see the filesystem pricing reference.- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
- Monthly
- Hourly
* Basic HDD instances below 1 TiB are charged a per-instance fee, which is waived once the instance reaches 1 TiB of provisioned capacity.
Example
Using the reference rate for Basic HDD in Oregon of $0.168 per GiB per month, a 2 TiB estimate is 2,048 GiB × $0.168, or $344.06 per month. Have questions about storage pricing or need capacity in a region not listed here? Talk to our team.Browsing your storage
The Storage page loads buckets one page at a time, with the most recently updated first. Search matches literal text across all your buckets. Provider and deployment filters also cover the full catalog. Use Previous and Next to browse, or open a bucket’s link directly. Volume selectors offer Load more buckets to browse further results. In Browser view, the bucket you’re inspecting stays open when you change filters or pages. Its files and current folder remain available even when its row is outside the visible results. Detach shows progress and stays disabled until the operation completes, both in Browser and on the bucket’s detail page. Direct bucket mounting requires an active node or cluster. If none are available, choose Go to Nodes to manage your compute. The Managed fileshare tab shows sizing guidance and Contact Ornn, even when you have no active nodes or clusters. Open a bucket to view its files. Select a folder to browse its contents, and use the Files breadcrumb to return to the root. Search files, Upload, and the per-file download and delete actions are available on the detail page. Choose Deploy in the bucket header, then select a reservation. Storage mounts all nodes in that reservation together, so there is no individual node selector. Choose Read only or Read/write, then Mount. To change a mounted bucket’s access, choose Detach and wait for completion. Then choose Deploy, select Read only or Read/write, and mount it again. A duplicate copies its files in the background. Its size is reported when the copy finishes. Detaching a bucket refreshes its size after mounted writes have finished. If that measurement fails, a later periodic measurement can correct the total. Sizes can lag changes made from mounted compute while files are still changing.Manage volumes through the API
Create volumes, upload files, and attach a volume to a reservation from your own tooling with an API key. A volume belongs to the person who created it in one organization; an API key sees the volumes of its creator, not those of teammates. Volumes are billed at the object-storage rate for the data stored. Detaching keeps the volume and its data; deleting a volume is permanent. The Storage API reference lists every request and response field.1. Create a volume
- CLI
- REST
- Python
201. Creation is not idempotent; after a timeout, list your volumes with q set to the name before retrying. To copy an existing volume, add source_drive_id; the files copy in the background.
2. Upload files
Upload before you attach the volume. While a volume is mounted, direct uploads and file deletions return409 with storage_drive_mounted; write from your machines instead.
For a file up to 32 MiB, send the bytes to Upload a small file. For larger files, use a staged upload: start it, send the bytes to the returned short-lived upload_url, then complete it. Send only the returned headers to upload_url, never your Ornn API key. The session expires after about 15 minutes.
- CLI
- REST
- Python
{} is enough). Repeating the start request with the same Idempotency-Key and unchanged input returns the same session, or state: complete if it already finished. Deriving the key from the file’s SHA-256, as above, makes a retry of the same bytes safe and gives changed contents a new upload. Uploading to an existing path replaces that file.
3. Attach the volume to a reservation
Attaching mounts the volume on every machine in the reservation; you cannot choose individual machines. Every machine in the reservation must be online. A reservation holds one volume at a time, and a volume attaches to one reservation at a time. The default mount path is/home/tenant/volume. To change the access mode or mount path later, detach first.
- CLI
- REST
- Python
attachment.state moves from pre_positioning, while Ornn prepares a copy near your machines, to ready. Each machine then mounts the volume; continue when every entry in the volume’s active_mounts is mounted. On failed, read attachment.error or the mount’s error. A 409 with storage_reservation_node_offline means a machine in the reservation is offline. Verify from a machine before starting a workload:
4. Detach and delete
Detach before you delete the volume, change its access mode, or attach it to another reservation. Detaching ends access from the machines and keeps the data. It does not change reservation billing.- CLI
- REST
- Python
attachment.state: detaching; the reservation’s attachment becomes null when the machines have released the volume. Deleting returns 204 and cannot be undone. Deleting an attached volume returns 409 with storage_drive_attached_to_reservation; add ?detach=true to detach and delete it in the background, which returns 202. Poll Get a volume until it returns 404.