Escrow

Escrow lets a resource author ship code that the buyer can run but not read. The protected files are decrypted at runtime by the server against the licence linked in Keymaster, so a leaked copy will not start on another account.

For a buyer this has consequences worth knowing before the purchase. You cannot edit escrowed files, which means you cannot fix a bug, cannot change a string, and often cannot rebrand the resource — the parts you can edit are whatever the author deliberately left open, usually a config file and sometimes the UI. Renaming a resource can break it outright, because the escrow binding includes the resource name.

It also means a resource can stop working if the author's account or the key relationship changes, which is a real dependency on a third party for anything load-bearing.

None of this is a reason to avoid paid resources. It is a reason to check how much of a given resource is open before you build your server's identity on it.