That single fact is why most people never touch RAM disks — one crash, one unmount, one reboot and the data evaporates. Persist exists to remove that risk entirely. Here’s how. ↓
Other RAM disk tools hand you a fast volume and walk away. Persist treats persistence as the whole point — your data flows to and from real storage automatically, so a RAM disk feels exactly like a normal folder that just happens to be lightning fast.
Drag a folder onto the app and it spins up a RAM disk pre-loaded with that folder’s contents. Your project caches, build folders, or scratch space are instantly fast — with zero migration.
Work entirely in RAM, then eject. Persist syncs everything back to a folder (or an S3-compatible storage) before the RAM disk disappears — powered by a bundled rclone engine that only moves what changed.
You can configure Persist to run incremental backups at the frequency of your choosing — so data loss from a kernel panic, forced halt, or any other incident has limited impact.
Every time you unmount a synchronised RAM disk, Persist lists every application still touching it — and hands you the call. Nothing is written until the RAM disk is truly idle, so the backup you get is whole, not a half-finished snapshot.
Mount it right before you open the app that needs it, eject it when you’re done — your data is saved back to disk either way. The memory is only borrowed for as long as you’re actually working.
The size you set is a ceiling, not a reservation. A RAM disk grows as you fill it and uses exactly as much memory as the files it holds — 2 GB of build artifacts in a 10 GB RAM disk costs you 2 GB.
Create, mount, back up and unmount RAM disks without leaving the terminal — handy for scripts, automation and integration into development workflows, such builds, tests or CI/CD workflows. The same Persist engine under the hood, the same performance guarantees.
No subscription, no account, no upsell.
Try every feature free for two weeks.

