Asset escrow
Sell your resources on Tebex without giving away your code.

Developer Preview – planned feature. Asset escrow arrives after the Lua runtime and NUI. This page describes how it will work so you can prepare your resources; details may change.
Asset escrow lets you sell your resources without giving away your code. You keep building normal resources. When you publish one, Neighborly encrypts its Lua files and ties it to the buyer's Neighborly account. Buyers can run it on every server whose server key belongs to their account – but they can't read, copy or resell the protected code.
How it works
- Build your resource as usualDevelop and test on your own server with plain files. Nothing changes in how you write code.
- Choose what stays openList files buyers should be able to edit – configuration, translations – in
escrow_ignore. - Upload itUpload the resource folder in My account → Creator. Neighborly checks the manifest, encrypts the protected files and creates an asset.
- Connect a Tebex packageLink the asset to a package in your Tebex store. When someone buys it, the asset is granted to their Neighborly account automatically.
- Ship updatesUpload a new version any time. Buyers see the update in their account and download it with one click.
name = "rtx_cafe"
version = "1.2.0"
author = "RTX Development"
description = "Run a café: brew coffee, serve customers, earn tips"
shared_scripts = ["config.lua", "locales/*.lua"]
client_scripts = ["client/*.lua"]
server_scripts = ["server/*.lua"]
ui_page = "html/index.html"
files = ["html/**"]
escrow_ignore = ["config.lua", "locales/*.lua"]What is protected
| Part | Protected | Notes |
|---|---|---|
| Server scripts | Encrypted | Never leave the server, and are only decrypted in memory by the runtime. |
| Client & shared scripts | Encrypted | Sent to players encrypted, decrypted only inside the game. |
Files in escrow_ignore | Open | Readable and editable – meant for config and translations. |
resource.toml | Open | Server owners must be able to read it. Only a few keys may be changed. |
| NUI files (HTML, CSS, JS) | Not encrypted | The overlay browser has to read them. Keep important logic in Lua, not in JavaScript. |
| Images, sounds, data files | Not encrypted | Delivered as normal files. |

Never put secrets – API keys, Discord webhooks, passwords – in an escrowed config file or any client or shared script. Keep them in convars in server.json and read them with GetConvar on the server.
For buyers
- Buy on TebexSign in with your Neighborly account during checkout, so the purchase is linked to you.
- DownloadOpen My account → Assets and download the resource.
- InstallExtract it into your server's
resourcesfolder (for exampleresources/[paid]/rtx_cafe), add it to"resources"inserver.jsonand runrefreshandensure rtx_cafe. - ConfigureEdit the open files like
config.luaand restart the resource.
The asset works on every server whose server key (nbk_…) was generated in the buyer's account. Starting it elsewhere shows a clear message:
> ensure rtx_cafe
Couldn't start rtx_cafe: this asset belongs to another Neighborly account.
Buy it at https://rtx.tebex.io or use a server key from the account that owns it.Good to know
Do I need to obfuscate my code too?
No. Escrow encrypts the files – obfuscation only makes your own debugging harder. Error messages from escrowed resources still show your file names and line numbers, so you can support your buyers.
Can buyers use an escrowed resource as a dependency?
Yes. Exports, events and state bags work normally, so other resources can integrate with yours. Document your exports for them.
What happens if a buyer moves to a new server?
Nothing to do – they generate a new server key in the same account and the asset works there.
Can I offer a free version?
Yes. Free resources can be shared as plain folders, or published as a free Tebex package to reach buyers through the same flow.
What isn't allowed?
Backdoors, hidden remote code, collecting player data without telling the server owner, and reselling other people's work. Assets that break these rules are removed and the creator loses access to escrow.