The Framework Compatibility Problem
Most FiveM scripts ship with one framework hard-coded in. If you run QBCore, you use QBCore scripts. ESX users are stuck with ESX scripts. Standalone users mostly hack things together. Agency Scripts were built with the opposite philosophy: the framework is an adapter, not an assumption.
The Adapter Pattern
Every Agency script exposes a small set of lookup functions: getPlayerData, getInventory, addMoney, removeItem, getJob. We ship adapters that map these to QBCore and ESX implementations out of the box. For standalone, you implement the four or five functions yourself — typically a morning's work — and every Agency script is compatible.
What This Means in Practice
When you switch your server from QBCore to ESX (which does happen every few years as frameworks evolve), Agency scripts don't need to be reinstalled or reconfigured. You swap the adapter, everything else keeps working. This is incredibly rare in the FiveM ecosystem and it's the main reason server owners standardize on our tooling for the long haul.
Which Framework Label on Our Product Pages Means What
When a product page lists "QBCore, ESX" it means we ship ready-made adapters for both. When it says "Standalone" we mean the script is framework-agnostic — it needs no adapter and runs on any server. In practice almost every Agency script is usable on standalone setups with a small compatibility shim.
When to Ask Before Buying
If you run an unusual setup — custom framework, heavily modified QBCore, or something bespoke — open a ticket on our Discord before buying. We'll tell you honestly what will work, what needs light adaptation, and what isn't worth the trouble. No sales pressure; we'd rather you buy one script that fits than three that don't.