
mountOS
Self-hosted POSIX filesystem that mounts S3 and object storage on Mac, Windows, Linux, and…
FreeDevOpsAIAPI914 impressions#16 of its week3 comments
Comments
>log in to comment
kris gu· 14d agoMount object storage as a POSIX drive, the atomicity and consistency of rename has always been the biggest pitfall, and tools like s3fs/goofys basically rely on luck. I want to ask whether your rename is implemented as copy+delete in two steps, or if there is a metadata transaction layer backing it up? Is the one‑minute granularity of time travel achieved via snapshots or event replay?

Thanks for your interest! These are indeed two of the key challenges in designing filesystems over object storage. Rename: mountOS doesn’t use S3 copy+delete. We have a separate metadata service (dataserv), with database transactions ensuring atomic rename. File contents are stored as immutable objects, so rename only updates metadata without moving or copying S3 objects. Time travel: We use versioned metadata rather than periodic full snapshots or event-log replay. Historical versions can be accessed by timestamp, and independent forks can be created from previous points in time. One minute represents the time-selection granularity, not a full snapshot taken every minute. The fundamental design separates POSIX filesystem semantics from the underlying object storage operations
More DevOps tools →80 free dev tools →
Self-hosted POSIX-compliant filesystem that mounts S3 and object storage on Mac, Windows, Linux and Kubernetes with time-travel and forks.
- for
- Developers and ops teams needing native file access to object storage.
- pricing
- freemium
Key features
- Native POSIX mounts — Mount volumes on Mac, Windows, Linux or Kubernetes with full POSIX semantics.
- Time travel — Open a volume as it existed at any minute within the retention window.
- Forks — Instantly create writable copies of a volume for isolated work without copying data.
- Version history — Automatic per-file history with one-minute granularity, configurable to sub-minute.
- Sandbox mounts — Mount temporary writable forks that discard all changes on unmount.
- Multi-protocol support — Access via FUSE, NFS, SMB, FSKit, CSI, S3 and WebHDFS APIs.
Use cases
- Run existing data-intensive applications against object storage without code changes.
- Create isolated test environments by forking a volume and discarding after use.
- Recover accidentally deleted files from built-in recent-deletion history.
- Provide analytical workloads via an Iceberg catalog volume type.
- Stream file-system events to downstream processors or AI agents.
mountOS FAQ
How can object storage be mounted as a POSIX filesystem?+
mountOS runs a native POSIX-compliant filesystem on the host and serves S3/WebHDFS APIs from the same volume, storing data in owned object storage.
Do I need to schedule backups or snapshots?+
No. Version history, time travel and recently-deleted recovery are built-in, allowing you to restore any past version or deleted file.
Can it support analytical workloads?+
Yes. An Iceberg Catalog volume type presents the data as an Apache Iceberg catalog for direct querying by analytical engines.
How is POSIX compatibility verified?+
mountOS is tested with industry suites like pjdfstest, LTP, xfstests, fsx and IOR with mdtest.
Can AI agents work with mountOS?+
Each client includes a read-only MCP connector and drop-in skill so AI agents can interact with mounted volumes.
Edited by the makers, based on mountos.io · Oct 26, 2026. Details may change; check the official site.





