Yes. Mouzi is MIT-licensed open source. There is no paid tier, no trial and no feature gating. Sponsorship exists to fund development time, not to unlock anything.

No. Mouzi has no server side. Rules run locally and history is stored in a local SQLite database. The only optional network request is an update check against GitHub’s public releases feed.

Open History and click undo on that entry. Mouzi records successful moves and can move the file back when it still exists at the recorded destination. Then adjust the rule, or add the file to .mouziignore.

Mouzi reduces that risk by waiting through a grace period, skipping browser temporary files such as .crdownload and .part, ignoring zero-byte placeholders and checking whether another process has locked the file. Manual and scheduled cleans process files immediately, so use them after downloads finish.

Public version 0.1.5 is unsigned while production signing through SignPath Foundation is being prepared for a future release. Windows may therefore show an unknown-publisher warning. Download Mouzi only from mouzi.cc or the official GitHub release, and check the security guide before running it.

Windows 10 and 11 (x64) and Linux (x86_64, as AppImage, DEB and RPM). A macOS build exists experimentally but is not yet supported.

Yes. Any folder can be watched, and you can watch several at once, each with its own rules.

Mouzi moves files with normal file-system operations, so folders synced by cloud clients generally work, with the sync client picking up the change. Test with non-critical files first.

Uninstall the app, then delete the configuration folder: %APPDATA%\Mouzi on Windows or ~/.config/mouzi on Linux. That removes all rules and history. The portable build only needs its file deleted.

Code, translations, documentation and bug reports are all welcome. Start at the GitHub repository; the issue tracker has the current priorities.