A cross-platform, forkable, time-traveling distributed filesystem over object storage.
Mount it natively on Mac, Windows, Linux, and Kubernetes, or reach it over S3 and WebHDFS, on owned infrastructure.
Built in, not bolted on.
Local file access, time travel, forks, version history, and immutable data are native to the storage itself.
Runs everywhere
Mount it natively on Mac, Windows, and Linux, or reach the same data over the S3 API and HDFS. One volume, every surface.
POSIX-compliant
A fully POSIX-compliant filesystem. Standard file and directory semantics let existing applications and tools run as they are written.
Forks
Fork an entire volume in one call. Work in isolation, fork again, then keep it or drop it. Nothing is copied.
Sandbox mounts
Mount a temporary, writable fork of a volume, pinned to any point in its history or its live state. Experiment freely, then unmount and every change is discarded.
Time travel
Open the volume as it was a minute ago, an hour ago, or last week. Any minute inside the retention window.
Version history
Every file keeps a rolling history automatically, one minute by default, configurable down to a sub-minute window. Rapid saves collapse to the latest one so the history stays useful.
Recently deleted
Open files removed by accident and copy them back out, from the volume itself.
Retention policy
One setting per volume controls how far back time travel reaches, how long deleted files stay available, and when old versions age out.
Integration
An open-source dashboard and SDK for custom integration, with scoped access tokens.
AI MCP connector
Each client ships an MCP connector so AI agents can work with mounted volumes.
Metadata
Metadata runs on its own isolated plane, served from an in-memory layer and persisted to PostgreSQL or MySQL-wire-compatible engines.
Protocol support
Mount FUSE · NFS · SMB · FSKit · mountosio · Kubernetes CSI
Compatible POSIX · S3 · WebHDFS
Pick a path in.
Pick a surface and go. Every path is a handful of commands against owned infrastructure.
Self-host free. Talk to us to scale.
Every plan carries every capability. Reach out to grow past the free tier or to add support.
Self-hosted
The entire suite runs on owned infrastructure.
- Every capability
- All client surfaces (mounts, S3, WebHDFS, CSI)
- Forks, time travel & version history
- Single HUB deployment
Business License
Room to grow, arranged with us directly.
- Storage beyond the free tier
- Priority support and licensing
support@mountos.io
Questions, answered.
Why mountOS?
mountOS mounts object storage as a native filesystem. It lets infrastructure providers deliver production-ready native file access as a product of their own.
Where does my data live?
On owned infrastructure: owned servers, and owned object storage.
How is it licensed?
Free up to 10 TiB for a single self-hosted deployment, with every capability included. Beyond that, or for support, a Business License is arranged directly with us.
How do I access my files?
Native mounts on Mac, Windows, Linux, and Kubernetes (FUSE, NFS, SMB, FSKit, mountosio), plus the S3 and WebHDFS APIs the client itself serves. It is fully POSIX-compatible, so existing apps work as they are written.
How is POSIX compatibility verified?
With the industry filesystem suites, each covering a different surface. pjdfstest for POSIX compliance (8,789 tests), the Linux Test Project (LTP) for filesystem and system-call behavior, xfstests for filesystem regressions, fsx for I/O consistency under randomized operations, and IOR with mdtest for I/O throughput and metadata load.
Do I have to schedule backups or snapshots?
No. Version history at a configurable granularity (one minute by default, down to a sub-minute window), time travel, and recently-deleted recovery are built into the storage. Open any version or deleted file and copy it out.
Can it support analytical workloads?
Yes. An Iceberg Catalog volume type presents the data as an Apache Iceberg catalog, so analytical engines can query it directly.
Can I capture file events for processing?
Yes. Every general volume can keep an ordered feed of creates, deletes, modifies, and renames, and the mountos event subcommand streams it live or serves it as a local REST API.
Can AI agents work with it?
Yes. Each client ships a read-only MCP connector, alongside a drop-in agent skill and llms.txt for any MCP-capable client.