Most FiveM server owners buy a script, drop it in their resources folder, and never read the licence. That works until they try to run the same purchase on a second server, pass files to a friend, or sell their community — and the asset stops working or their Cfx.re account gets flagged. Understanding what you actually own when you buy a FiveM script will prevent expensive mistakes.
What a Licence Actually Grants You
Buying a FiveM script does not give you ownership of the code. It gives you a licence — a permission to use the script under conditions set by the seller. The default condition on virtually every Tebex-distributed script is a single-server licence: one purchase covers one live server key.
That means:
- You may run the script on one Cfx.re server (identified by its server key).
- You may not copy it to a second server you own without buying a second licence.
- You may not share the files with another server owner, even if that server is in your own network.
Some sellers offer unlimited-server or multi-server licences at a higher price point, explicitly allowing installation across multiple keys you control. If the product page does not say so, assume it is single-server.
How Cfx.re Keymaster Enforces the Licence
Cfx.re’s Keymaster system ties an escrowed asset to the account that purchased it. When you buy through Tebex, the asset appears in your Keymaster dashboard and is bound to one server key at a time. The encrypted code checks against Cfx.re at startup — if the key does not match the account, the resource refuses to start.
This is why transferring a purchase is not as simple as copying files. The licence must be transferred at the account level through Keymaster, not just by handing over a folder. If you sell your server or pass management to someone else, the new owner needs the asset re-granted to their Cfx.re account — which requires the original seller’s cooperation.
Escrowed vs Open-Source Scripts: A Critical Difference
Scripts sold through Cfx.re’s asset escrow are delivered as obfuscated or encrypted Lua. You receive a working resource but cannot read, edit, or redistribute the underlying code. Licence terms almost universally prohibit:
- Decompiling or reverse-engineering the encrypted files.
- Modifying the script beyond configuration files the seller explicitly exposes.
- Redistributing any part of the resource, paid or free.
Open-source scripts — typically under MIT or Apache licences — work differently. The source is readable, you can fork and modify it, and redistribution is usually permitted as long as you retain the licence header. A script sold on Tebex with a price tag is almost never open-source unless the seller explicitly states it and links a public repository. Stores like scripts-tebex.io list licence type and Keymaster-escrow status on each product page — check that before buying if modification rights matter to you.
What You Cannot Do With a Standard Single-Server Purchase
These actions are prohibited under virtually every proprietary script licence and will typically result in consequences:
- Reselling — selling the files or a cracked version to other server owners.
- Redistribution — uploading to forums, Discord, GitHub, or any file share.
- Leaking — receiving and using leaked files is a violation on your side, even if you did not do the leaking.
- Running on a second server key — including a publicly accessible dev box, unless the licence explicitly permits it.
- Editing escrowed code — attempting to strip or bypass encryption is a violation regardless of outcome.
Sharing With a Friend’s Server
One of the most common misconceptions: buying a script does not cover a separate server owned by someone else, even if that person is a friend, co-owner, or network partner. Each distinct Cfx.re server key is a separate licence unit. If your friend wants the same script on their server, they need their own purchase — and the same applies across different Cfx.re accounts you control. The licence follows the account, not the person.
Transferring a Licence When You Sell a Server
When a server changes hands, the scripts on it are not automatically transferred. The seller must contact each script developer to request a licence transfer to the buyer’s Cfx.re account. Some sellers charge a transfer fee or decline entirely — check terms before promising scripts as part of a server sale. Escrowed assets must be re-granted in Keymaster; handing over the files alone will not make them run. If you are buying a server with scripts included, confirm each transfer is complete before finalising the deal — files with no valid Keymaster grant will stop working at the next verification cycle.
Consequences of Licence Violations
Violations are taken seriously across the ecosystem:
- Asset revocation — Cfx.re can revoke Keymaster access, disabling the script immediately.
- Tebex account suspension — repeat violations can suspend your buyer account, cutting off access to all past purchases.
- Cfx.re bans — redistribution and leaking are bannable offences on the official forums.
- Blacklisting — some developers share blacklists; a violation with one seller can lock you out of others in the same network.
Reading the Licence Before You Buy
Every reputable Tebex product page includes licence terms — usually in a “Terms of Service” or “FAQ” section. Before purchasing, confirm: how many servers are covered, whether config-file editing is allowed, what the transfer policy is, and whether the script is escrowed or open-source. If the page is vague, message the seller directly before you pay. Ambiguity in a licence resolves in the seller’s favour.
Stores with clearly listed terms include cfx-tebex.store and vortexscripts.co.uk — read the licence section before you commit.
