Guide · Updated 14 Sep 2026
VORP vs RSG Core vs QBCore: which RedM framework should you build on?
A RedM framework is the base layer every other script talks to: characters, money, jobs, inventory. You pick it once, and every script you buy afterwards has to support it. This is how the main options compare, written from the position of a team that runs a server on one and ships scripts that run on all three.
The short version
| Framework | Best for | Inventory | Script ecosystem | Poggy Scripts |
|---|---|---|---|---|
| VORP Core | The widest choice of scripts, and teams that want a proven base | vorp_inventory | The largest. Most paid RedM scripts target VORP first. | Supported. Every script; the server we run. |
| RSG Core | Developers who know QBCore from FiveM and want the same shape on RedM | rsg-inventory | Growing quickly; many scripts now ship VORP and RSG together. | Supported. Every script, same build, through poggy_core's RSG adapter. |
| QBCore RedM (QBR) | Teams porting an existing QBCore FiveM setup | qbr-inventory | Smaller on RedM; check each script's page for support. | Supported. All of them, same build, through poggy_core's QBR adapter. |
VORP Core
VORP is the longest-running RedM framework and the one most third-party scripts are written against first. Its pieces are separate resources: vorp_core for characters and money, vorp_inventory, vorp_character, vorp_menu, vorp_inputs and so on. That modularity is why so many scripts list "vorp_core, vorp_inventory" as requirements, and why replacing one piece is possible.
Our own server runs VORP, and every script in this store is played there before release. If you want the largest choice of scripts today and the most people who have seen your error before, VORP is the safe answer. Poggy scripts on VORP do not need vorp_menu or vorp_inputs: Poggy Core (Free) draws menus, text inputs and notifications itself.
RSG Core
RSG Core follows the structure of QBCore from FiveM, rebuilt for RedM. If you or your developer already know qb-core, the resource names, exports and config style will feel familiar, which shortens the time to a working server. Its ecosystem has grown fast, and a lot of newer scripts, ours included, detect RSG at runtime rather than shipping a separate build.
Every Poggy script runs on RSG Core. poggy_core's RSG adapter, written against rsg-core and rsg-inventory and proven in game, handles characters, money (cash, bank and gold), jobs with RSG's built-in duty, items and stashes, ACE-based admin levels and notifications. Witnesses (from $6.99/mo) reaches your deputies through it, Poggy Markets ($99) moves money and stock through it, and the free Poggy Storage (Free) keeps its containers as rsg-inventory stashes. Two features are VORP-only for now: Poggy Transform ($9.99)'s admin character-appearance browser and Poggy Util (Free)'s government stipend. The rest of each script works. One RSG-specific step: add RSG's stock law jobs (vallaw, rholaw, blklaw, strlaw, stdenlaw) to LawJobs in poggy_core/config.lua.
QBCore for RedM (QBR)
QBR is the QBCore port to RedM. It makes sense if you are moving an existing QBCore community across and want to keep tooling. The trade-off is a smaller pool of maintained RedM scripts; check each product page rather than assuming. Every Poggy script runs on QBR. poggy_core's QBR adapter, written against qbr-core and qbr-inventory and proven on a live server (the full self-test passes), handles characters, money, jobs, duty, items, stashes, ACE-based admin levels and notifications from the same build as VORP and RSG, so there is nothing to re-download and nothing to configure. The same two VORP-only features apply as on RSG: Poggy Transform ($9.99)'s character-appearance browser and Poggy Util (Free)'s government stipend. One QBR-specific step: scripts that keep items in a stash (Poggy Storage (Free), Trash Bins, Poggy Markets) use qbr-inventory stashes, which need the stashitems table. poggy_core checks for it at start and prints the CREATE statement if it is missing.
RedEM:RP is not on this list because Poggy Scripts does not support it and no adapter is planned.
How to decide
- Starting from nothing, no developer: VORP. The most scripts, the most tutorials, the most people in Discords who have seen your error before.
- You know QBCore from FiveM: RSG Core. Same mental model, the script gap is closing, and everything in this store runs there.
- Moving a QBCore community: QBR. Keep your tooling, budget time to verify each third-party script you rely on, and everything in this store runs there.
What "framework agnostic" means on our pages
Every Poggy script talks to the framework through one thing: Poggy Core (Free), a free resource that works out which framework is running and translates one set of calls (character, money, jobs, duty, items, stashes, permissions, notifications, menus) into that framework's own. A script is written once against poggy_core; a framework is supported by writing one adapter file inside poggy_core. Today there are three adapters, VORP Core, RSG Core and QBCore RedM, and all three are proven on a live server, so every script's "Works with" line says exactly those three.
On a server with no framework, or one poggy_core has no adapter for, Core.HasAdapter() reports false and every framework call is refused with a clear error rather than silently doing nothing. Adding a framework is a poggy_core update, not a script update: the QBR adapter arrived that way and no script changed. The console prints which framework it found on first start, and /poggycore shows the framework, version and capability map on any server.
The two exceptions are features, not scripts, and each product page says so under "Works with": Poggy Transform's character-appearance browser and Poggy Util's government stipend are VORP-only today. If you are a developer, Using Poggy Core in Your Own RedM Scripts shows how to build on the same layer.
