Freally MIDI Master

The engine is rule-based, not trained

There is no AI in this product. No models, no training data, no inference, no network calls during generation. The engine is deterministic procedural code reading hand-authored style parameters derived from published research.

That is a legal architecture as much as a technical one: nothing here is copied MIDI, sampled audio, or a transcription of anyone's record, and there is no feature that recreates a specific song. Artist names are descriptive style references only.

The music you make with it is yours, with no royalty and no attribution requirement. Freally MIDI Master itself is proprietary, All Rights Reserved, and its source code is private — you may not redistribute it. It is not open source.

Privacy

No accounts. No telemetry. Nothing about you, your projects or your output is ever transmitted. Generation, playback, import and export are entirely local.

The plugin makes no outbound connections at all. The two that used to exist — a launch-time update check and an opt-in crash report — belonged to the desktop app and were removed with it. A plugin is installed and updated by whoever installs plugins.

The web app is delivered over the network; what you make is not. A page has to be fetched — the app itself, and the style data it generates from. That is the whole of it. Generation runs on your own machine, in your own browser; your beats, your seeds and anything you import stay there and are never uploaded. After one visit the tab works with the network switched off, which is closer to offline than most software manages.

Collaboration is the one exception, and only if you use it. Rooms connect your machine directly to the people you invite. If you save someone as a buddy, a small service can tell you when they are online — and it is told nothing worth knowing: a key that changes every few minutes, and an address encrypted to a secret only the two of you hold. It cannot read it, cannot list who is there, and cannot work out who knows whom. Turn it off, or never save a buddy, and you paste a code instead — which is how rooms work anyway.

Enforced by two build gates rather than promised: no HTTP client is compiled into the plugin — still true, because the collaboration service is reached by a separate program, never by the plugin your DAW loads — and the interface itself is driven through a generation on every commit and fails if it attempts a single request off the machine. Crash reports are written to your own disk and never sent anywhere.

One thing that is coming, said now rather than when it ships. The collaboration feature — rooms, in development and not installed by anything today — needs to learn your machine's public address before two people can connect directly, which is what a STUN server is for. When it lands, opening or joining a room will contact one; this build names Cloudflare and Google. Such a server learns only that some address is using a WebRTC application — not who you are talking to, and not what you send — and nothing is contacted until you open or join a room. The sentence above stays true for the plugin as it ships today.