A distributed storage solution that runs on your infrastructure.
Native file access, time travel, forks, and version history, built into distributed storage you run yourself.
Built in, not bolted on.
Local file access, time travel, forks, version history, and immutable data are native to the storage, not separate systems you run.
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 your existing applications and tools run without modification.
Forks
Fork an entire volume in one call. Work in isolation, fork again, then keep it or drop it. Nothing is copied.
Time travel
Open the volume as it was a minute ago, an hour ago, or last week. No snapshots to configure.
Version history
Every file keeps a rolling history automatically, down to the minute. Rapid saves are collected so the history stays useful.
Recently deleted
Open files removed by accident and copy them back out, with no backup to pull from.
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 user-level access tokens for scoped access.
AI MCP connector
Each client ships an MCP connector so AI agents can work with your mounts.
Metadata
Metadata runs on its own isolated plane, served from a Raft-backed 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
Run it your way.
Pick a surface and go. Every path is a handful of commands against your own infrastructure.
Self-host free. Talk to us to scale.
Every capability is in every plan. Talk to us when you need more capacity or support.
Run the entire suite yourself, on infrastructure you operate.
- Every capability, no feature limits
- All client surfaces (mounts, S3, WebHDFS, CSI)
- Forks, time travel & version history
- Single self-hosted deployment
no account · no sign-up
More capacity and support, arranged with us directly.
- Capacity beyond the free tier
- Priority support and licensing
support@mountos.io
Questions, answered.
Why mountOS?
mountOS enables infrastructure providers to deliver production-ready native file access without building and maintaining a distributed filesystem themselves.
Where does my data live?
On infrastructure you operate, your servers and your S3-compatible or Azure storage.
How is it licensed?
Free up to 10 TiB for a single self-hosted deployment, with every capability included. For more capacity or 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 unchanged.
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 one-minute granularity, time travel, and recently-deleted recovery are built into the storage. Open any version or deleted file and copy it out, with no backup to pull.
Can it support analytical workloads? Beta
Yes. An Iceberg Catalog volume type presents your 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.