Priced on the only thing that grows

Files are compressed before they are uploaded, which takes roughly half the size off typical game binaries — measured at 50% on a 12 MB executable. Skipping unchanged files is the bigger win on top of that: files that didn't change transfer nothing at all, so a rebuild touching ten files costs ten compressed files, not a whole client folder.

No. Every client runs the identical signed Patcher.exe. The only per-client file is a config whose one meaningful line points at your hosted config, which the exe fetches at startup and overlays over its local copy.

New uploads are refused before they start, with your current usage and your tier limit in the error. Everything already in your storage keeps serving — we do not break a live game client over billing.

No. Branding lives in the remote config at your storage root, which the exe re-reads on every launch with a short timeout and a cached fallback — so a network problem can never strand a client on a broken config.

Each patch version is its own immutable folder, and the live version is a pointer. Change the pointer and the next launch picks it up. No re-upload, no downtime, nothing deleted.

Each account gets its own isolated storage, and every operation resolves it from your signed-in session — never from anything the browser sends. There is no request shape that reaches another account's data.

Yes — 100 MB, two versions kept and one publish per day, served from a shared EasyPatcher subdomain instead of your own custom domain. Enough to wire the whole flow end to end before you pay anything.

Committing one patch version. Dropping in twenty changed files is still one publish. The free tier allows one per day; every paid tier is unlimited.

The compressed size of everything in your storage, summed across every version you keep. The panel shows a running total and reconciles it nightly.

One patch folder. Cloning an existing version copies its unchanged files server-side — that costs storage for the copies, but no upload and no bandwidth.

Yes, in either direction. Downgrading below your current usage keeps existing files serving and blocks new uploads until you prune a version.