Cloud storage. Local drive.
mountOS changes complex cloud infrastructure into a secure local drive. The drive is dataless. Use standard operating-system tools to access object storage. mountOS presents the data as a native, POSIX-compliant filesystem. It works on macOS, Windows, Linux, and Kubernetes. The filesystem has no fixed capacity limit.
mountOS keeps a time-based history of each volume. Open a volume as it was at an earlier time. A fork can start from that time too. The fork is an independent filesystem. Set a retention period to control when old history expires.
Access
Use the S3-compatible API, the HDFS interface, or the Kubernetes CSI driver. These interfaces connect mountOS to existing data pipelines and clusters.
Events
mountOS reports file and directory changes. Use these events to start preprocessing when new data arrives. The feed replaces polling.
Data tools
Use the Iceberg catalog for lakehouse workloads. Use the sync tools to upload and download data. Use mountos sink to send HLS video streams from cameras to object storage.
Management
Use the desktop client or the admin SDK to manage mountOS. The admin portal is open source, so it can be adapted to a specific environment.
Sandbox mounts
Mount a temporary, writable fork of a volume. Use its current state or select an earlier time. Test changes in the fork. On unmount, mountOS discards the changes.
For businesses that need cloud-scale storage and native filesystem access.
The free tier supports up to 10 TiB. For more capacity, select a capacity limit and pay a fixed fee. The fee follows the limit, and it stays the same as usage moves inside it. Customers provide the infrastructure and run it themselves.