Guide · Updated 12 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 three main options compare, written from the position of a team that ships scripts for all of them and runs a server on one.
The short version
| Framework | Best for | Inventory | Script ecosystem |
|---|---|---|---|
| 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. |
| 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. |
| QBCore (QBR) | Teams porting an existing QBCore FiveM setup | qb-inventory | Smaller on RedM; check each script's page for support. |
| RedEM:RP | Servers already on it | None shipped; pick your own | Small. Storage-type scripts need an inventory it does not provide. |
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 the VORP-only scripts in this store (Fishing, Supply Drops, Balloon Taxi, Trash Bins, Scenes, the Auction House) exist because they were built on it for our players. If you want the largest choice of scripts today, VORP is the safe answer.
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.
Witnesses (from $6.99/mo) hooks straight into rsg_core. Poggy Markets ($99), Poggy Badges ($20), Poggy Transform ($9.99) and the free Poggy Storage (Free) detect RSG through poggy_util; Storage uses rsg-inventory stashes and is verified there.
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. In this store, Witnesses, Markets, Transform and Badges run on QBCore, and Storage works with qb-inventory on a best-effort basis because it shares the same API shape as RSG.
RedEM:RP
RedEM:RP is an older framework with a smaller ecosystem. The practical limitation is that it ships no inventory resource of its own, so any script that needs to store items in the framework's inventory has nothing to attach to. That is why Poggy Storage lists it as unsupported while Witnesses, Markets, Transform and Badges, which carry no inventory dependency, run on it.
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, and the script gap is closing.
- Moving a QBCore community: QBR, and budget time to verify each script you rely on.
- Already on RedEM:RP: stay if it works, but expect to skip inventory-dependent scripts.
What "framework agnostic" means on our pages
Several of our scripts say they detect VORP Core, RSG Core, QBCore and RedEM:RP at runtime through poggy_util. That is a free bridge resource: it works out which framework is running, and handles character data, jobs and notifications through it, so there is one download and no setting to change. The console prints which framework it found on first start. The scripts that do not use it are the VORP-only ones, and every product page says which it is under "Works with".
