File systems.
Managed shared file systems — POSIX and high-throughput parallel options for training data.
Fully managed shared file systems with POSIX semantics — from elastic NFS for general workloads to high-throughput parallel file systems that keep a GPU cluster fed.
- Category
- Storage
- Deployment
- Managed → air-gapped
- Governance
- IAM · encryption · audit
Three steps to running.
Pick elastic NFS for general use or a parallel file system for GPU clusters.
Shared POSIX access across many instances with standard semantics.
Capacity scales automatically; snapshots and backup are built in.
File systems, in full.
Mount the same file system across many instances with standard file semantics.
Scale-out file systems that saturate GPU clusters during training.
Grows and shrinks automatically; pay for what you store.
Point-in-time snapshots and managed backup built in.
Provision it in a few lines.
Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.
import { aether } from "@aether/sdk";
const store = aether.storage.file_systems("training-data");
await store.put("run-42/weights.safetensors", file);
const url = await store.presign("run-42/weights.safetensors", { ttl: "1h" });At a glance.
- Semantics
- POSIX, shared
- Throughput
- Parallel, saturates GPU clusters
- Capacity
- Elastic, pay-per-use
- Protection
- Snapshots + backup
- Access
- Many-instance concurrent
Built for real work.
Shared training datasets
HPC scratch space
Lift-and-shift file workloads
On one model, not stitched together.
The usual stack runs file systems in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.
No stitching a vector DB to one place, a warehouse to another and a model to a third — file systems sits next to the rest of the catalog, one identity, one bill.
The provider that runs Aether runs your file systems — so the data and the model never leave the same governed boundary to talk to each other.
Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.
Good to know.
Managed shared file systems from elastic NFS to high-throughput parallel — sitting next to GPU compute.
Yes — the parallel option delivers the throughput training jobs need.
No — it grows and shrinks automatically; you pay for what you store.
Your boundary, your choice.
Pairs well with.
Exabyte-scale, eleven-nines-durable object store with lifecycle tiering and presigned access.
High-IOPS network block storage that attaches to any instance, with snapshots and encryption.
Low-cost archival tiers for compliance and long-term retention, with fast restore when you need it.
A governed lakehouse over object storage — open table formats, cataloged and query-ready.
Run File systems on Aether Cloud.
Managed shared file systems — POSIX and high-throughput parallel options for training data. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.