Local versioning made simple.
Pick a folder, initialize once, and save as you work.
For files, assets, and large folders.
Why Rinne?
Initialize once, then keep saving as you work.
Keep the whole project in one local, non-destructive workflow. Text, binaries, assets, and large files all fit the same workflow.
Built around four simple actions
01
Save as you work
Every save adds a new snapshot to a Space, preserving the current state as you go.
02
Store everything efficiently
Text, binaries, assets, and large files are handled together. Chunk-level deduplication keeps repeated saves lean.
03
Restore or extract what you need
Put a snapshot back into the workspace, or write it out to a separate folder for inspection or reuse.
04
Combine safely
Create a new snapshot from two existing ones. Both originals stay untouched.
The Workflow
Select a workspace, choose a Space, then save a snapshot.
Select a workspace
Pick the project folder. Initialize runs once per workspace.
Choose a Space
Switch between independent snapshot timelines for experiments and variants.
Save a snapshot
Record the workspace as it is in the selected Space. Simple, direct, and repeatable.
If the first save hits locked or denied files, add ignore rules for temp files, caches, build outputs, or lock files before retrying. Read docs
UI Explorer
These slides form one connected workflow. Browse all of them to see the full picture.
Where Rinne fits
For work that moves through trial, rollback, and repetition.
Version binaries and text right away
Jump straight into local versioning. No server planning, cloud signup, or complex setup. Snapshot source files, binaries, assets, and build outputs together, without switching to a team-oriented workflow.
When exploring multiple game ideas and iterating on concept, mechanics, and game feel
Version heavy creative work by direction
Keep large creative files such as PSDs, AI files, source images, and exports versioned locally and offline. Manage A/B directions, before/after revisions, and pre-delivery return points on your own terms.
When versioning alternate directions and revisions across design, illustration, and asset work
Version drafts and research by milestone
Keep papers, books, technical manuscripts, and research notes versioned locally and offline at each meaningful revision point. Capture pre-cut, pre-rewrite, and pre-submission states whenever they matter.
When preserving revision milestones across books, papers, technical zines, and personal research
Core actions
The core loop, from save to restore.
If you can manage folders, you already understand the basics.
Save snapshots
Like saving the current folder state as a reusable point in time.
Save the workspace into the selected Space as a new snapshot. Scan everything or just what changed. Chunk-level deduplication and compression keep saves efficient.
Split into Spaces
Like keeping separate timelines for different directions of the same project.
Each Space keeps its own timeline, so experiments and production states stay separate. Storage is shared across Spaces, with chunk-level deduplication and compression to keep it efficient.
Compare and fuse
Like comparing two saved states, then layering one onto the other.
Compare snapshots or the current workspace. Fuse two snapshots into a new one, then save it in any Space.
Extract and restore
Like taking saved files out, or putting a saved state back into the workspace.
Extract writes a snapshot, or selected paths from it, into an external output folder. Restore writes the selected snapshot state back into the workspace.
Verify and validate
Like checking that what was saved is still intact and correct.
Verify checks snapshot integrity. Validate confirms that stored files still match their expected hashes, for a whole snapshot or just the paths you choose.
Maintenance
Like cleaning up storage and tuning how Rinne works on your machine.
Delete snapshots, reclaim unreferenced CAS data with garbage collection, and tune parallelism, compression, and rinneignore.json for your machine and workflow.
Script the same workflow
The same save, extract, restore, verify, and validate flow is available in the CLI for scripting and automation.
PS C:\WorkSpace> rinne save -m "update rinneignore.json" Saving (CAS). completed. done 137254 found 137254 14.1/14.1 GiB Mode : CAS (incremental) Space : main Snapshot : 20260307T231112652Z_019cca91-b50c-7b1b-9712-56b125c1994d ManifestDB : C:\WorkSpace\.rinne\store\manifests\manifest.db ZstdLevel : 4 Parallel : 8
Get started with Rinne
Get the desktop app and CLI in one download.
Start free and keep your project local-first.