RedM Frameworks Compared: VORP vs RSG vs RedEM

RedM roleplay frameworks compared in 2026: VORP vs RSG-Core vs RedEM:RP vs QBR, features, popularity and which to choose.

Published on 14 juin 2026

What a RedM framework is (and why it's your first decision)

RedM is the Red Dead Redemption 2 equivalent of FiveM: a multiplayer modification platform built by Cfx.re that lets you run custom roleplay servers for RDR2. An empty RedM server, though, is just a barren frontier — it has no jobs, no economy, no inventory and no character system. A framework is the base layer that adds all of that, so players can create a character, earn money, hold a job, run a gang and live in a persistent Wild West world.

Choosing your framework is the first big decision when you build an RP server, because almost every other resource you install is written for a specific framework. A shop script, a horse system or a job pack is usually built for VORP or for RSG-Core, not both. Pick the framework first, and the rest of your server is built around it.

This guide compares the four main RedM frameworks in 2026 — VORP, RSG-Core, RedEM:RP and QBR — and helps you choose. When you're ready to install, our how to make a RedM server walkthrough covers the full txAdmin setup.

The main RedM frameworks at a glance

All four frameworks do the same core job — character creation, money, inventory, jobs — but they differ a lot in popularity, how many ready-made scripts you can find, and how familiar they feel to developers coming from FiveM.

Framework	Style	Popularity	Resource ecosystem	Best for
VORP Core	RedM-native (ESX-like)	Highest — the de facto standard	Largest by far, very active	Most new servers, beginners, anyone who wants the most scripts
RSG-Core	RedM port of QBCore	Strong and growing	Good and modern, growing fast	Teams who already know QBCore from FiveM
RedEM:RP	Older RedM framework	Declining	Limited, fewer recent updates	Minimal servers, legacy setups
QBR	QBCore-style port	Low / niche	Small, less active	Tinkerers; mostly superseded by RSG-Core

In 2026, VORP is the safest default for a brand-new RedM RP server, and RSG-Core is the natural pick for a QBCore-experienced team. RedEM:RP and QBR are both losing momentum.

VORP — the most popular RedM framework

VORP Core is, by a wide margin, the most popular and actively maintained RedM roleplay framework in 2026. If you join a random RedM RP server, the odds are it runs VORP. That popularity is the whole point: because so many servers and developers use it, VORP has the largest library of compatible resources — inventories, shops, jobs, robberies, horse systems, MDTs and more — and the most documentation, tutorials and community help.

Architecturally, VORP is RedM-native and feels closest to ESX in the FiveM world: a core resource plus a set of official companion resources (vorp_inventory, vorp_character, vorp_hud, and so on). It uses a MySQL/MariaDB database through oxmysql, like every serious framework. For a first-time server owner, the depth of the ecosystem means you can build a full RP server almost entirely from existing scripts without writing much Lua yourself.

Popularity & community

The largest RedM RP community by far. Big active Discord, lots of YouTube tutorials, and the most StackOverflow-style answers when you get stuck.

Resource availability

The biggest catalogue of free and paid RedM scripts. When a new RedM resource ships, it's usually VORP-compatible first.

Ease of setup

Well-documented install, lots of step-by-step guides. Still a real framework — you'll set up a database and edit server.cfg — but it's the most beginner-friendly path.

Dev familiarity

Closest to ESX. Developers from the ESX/FiveM side adapt quickly, and there's plenty of example code to copy.

RSG-Core — the QBCore-style modern option

RSG-Core is the RedM port of QBCore, the framework that dominates the FiveM roleplay scene. If your team has built FiveM servers on QBCore, RSG-Core will feel immediately familiar: the same module structure, the same player.Functions patterns, the same way of defining jobs and items. It's modern, actively developed, and growing steadily as QBCore developers move into RedM.

For a QBCore-experienced team, RSG-Core is often the faster path because you already know the conventions and can reuse your mental model (and sometimes your code). Its resource ecosystem is smaller than VORP's but solid and expanding, with a clean, modern codebase. Like VORP, it runs on a MySQL/MariaDB database via oxmysql and is managed through txAdmin — the framework choice doesn't change the underlying server stack.

Popularity & community

Strong and growing, especially among ex-QBCore FiveM developers. Smaller than VORP's community but active and modern.

Resource availability

A solid, growing catalogue of RSG resources. Fewer total than VORP, but the QBCore heritage means familiar patterns for porting.

Ease of setup

Comparable to VORP — database, oxmysql, server.cfg. Easiest if you already know QBCore; the structure will feel like home.

Dev familiarity

The best choice for QBCore developers. Same architecture, so your FiveM/QBCore experience transfers directly.

RedEM:RP and QBR — the declining options

RedEM:RP was one of the earlier RedM frameworks and powered many of the first RDR2 RP servers. It still works, and it's lighter than VORP, but development has slowed and the community has largely moved on to VORP. The practical problem is the resource ecosystem: you'll find far fewer ready-made, actively maintained scripts, which means more building from scratch. It's fine for a minimal server or a legacy setup, but it's not where the momentum is in 2026.

QBR is another QBCore-style port for RedM. It overlaps heavily with RSG-Core in concept, but it's far less active and has a much smaller resource base — for most QBCore-minded teams, RSG-Core has effectively superseded it. Unless you have a specific reason to use QBR, RSG-Core is the more future-proof QBCore-style choice.

Warning

Framework choice locks in your resources. A script written for VORP won't run on RSG-Core (or RedEM:RP) without a full rewrite. Before committing, check that the inventory, jobs and shops you want exist for your chosen framework — switching later means rebuilding your resource stack.

Which RedM framework should you choose?

For most people, the decision comes down to two questions: do you want the biggest ecosystem, or do you already know QBCore?

The short recommendation

VORP for most new servers: it's the most popular and active RedM framework, with the largest library of compatible scripts and the best documentation — the safest default if you're starting fresh. RSG-Core if your team already knows QBCore from FiveM: the architecture is identical, so your experience transfers directly. Skip RedEM:RP and QBR for new projects — both are losing momentum and have far fewer maintained resources.

How to decide

•Starting fresh and want the most scripts? VORP
•Coming from QBCore on FiveM? RSG-Core
•Want the most documentation and tutorials? VORP
•Running a tiny minimal server and don't mind building from scratch? RedEM:RP works, but VORP is still easier
•Whatever you pick, confirm your key resources exist for that framework first

How to install your framework

The good news: installing any of these frameworks follows the same path, because RedM servers are all managed through txAdmin (the web control panel that ships inside the Cfx.re server artifacts). The framework choice doesn't change how you set up the server — only which resources you start.

Get your server running with txAdmin

First, you need a working RedM server: a free Cfx.re license key, the RedM server artifacts, and txAdmin set up. Our full [how to make a RedM server](/en/guides/redm/how-to-make-a-redm-server) guide walks through every step, from the cfxk_ key to connecting in-game.

Create a MySQL/MariaDB database

VORP and RSG-Core both need a database. Create one, then you'll import the framework's SQL file into it during install. Most managed hosts give you a database in the panel; on a VPS you'll install MariaDB yourself.

Clone the framework into resources/

Download your chosen framework (VORP Core or RSG-Core) and its companion resources from its official GitHub into your server's resources/ folder, then import the provided SQL into your database.

Wire it up in server.cfg

Add the ensure lines for oxmysql, the framework core and its dependencies, and set your database connection string. Restart from txAdmin and your framework is live.

set mysql_connection_string "mysql://user:password@localhost/redm"

ensure oxmysql
ensure vorp_core
ensure vorp_inventory
# start your other resources here

For the complete walkthrough — license key, artifacts, server.cfg and connecting in-game — follow our how to make a RedM server guide.

Does the framework change your hosting needs?

Not really. All RedM frameworks run on the same Cfx.re platform through txAdmin, and what actually drives your RAM and CPU usage is the number of Lua resources you run and your player count — not which framework sits underneath. A heavily scripted VORP server and an equally scripted RSG-Core server want roughly the same hardware.

As a rough guide, a small private RP server (5–12 players) runs on 4–6 GB of RAM, while a semi-public server with a full framework and 12–24 players wants 6–8 GB. RedM is also sensitive to CPU single-thread performance, so favour a host with strong per-core clocks and a node close to your players. For real plans and a full RAM/budget breakdown, see our RedM hosting page.

Same RAM, whichever framework you pick

Don't choose a framework to save RAM — they're roughly equal. Choose it for the ecosystem (VORP) or developer familiarity (RSG-Core), then size your host to your script load and player count.

Ready to launch your RedM server?

Take the 2-minute quiz to find a host for your RP server, or see how to set it up step by step.

Frequently asked questions about RedM frameworks

Which RedM framework is best in 2026?

For most new servers, VORP is the best choice: it's the most popular and actively maintained RedM roleplay framework, with the largest library of compatible scripts and the best documentation. The main exception is if your team already knows QBCore from FiveM — then RSG-Core (the RedM port of QBCore) is often faster because the architecture is identical. RedEM:RP and QBR are both declining and aren't recommended for new projects.

What's the difference between VORP and RSG-Core?

VORP is a RedM-native framework that feels closest to ESX, and it has by far the biggest ecosystem of compatible scripts. RSG-Core is the RedM port of QBCore, so it shares QBCore's structure and conventions — ideal if you come from the FiveM/QBCore world. Both run on the same txAdmin and a MySQL/MariaDB database; the real difference is the size of the script library (VORP wins) versus developer familiarity (RSG-Core wins for QBCore devs).

Is RedEM:RP still maintained?

RedEM:RP still works, but development has slowed significantly and the community has largely moved to VORP. The bigger issue is the shrinking pool of maintained resources — you'll find far fewer ready-made, up-to-date scripts than for VORP. It's usable for a minimal or legacy server, but for a new project in 2026 VORP is the easier and more future-proof choice.

Can you switch RedM frameworks later?

Technically yes, but it's a big job. Frameworks aren't cross-compatible: a resource written for VORP won't run on RSG-Core (or RedEM:RP) without a full rewrite, and player/character data is stored differently. Switching means rebuilding your entire resource stack and likely migrating the database. That's exactly why choosing the right framework up front — and confirming your key scripts exist for it — matters so much.

Does the framework affect server RAM?

Barely. RAM and CPU usage are driven by how many Lua resources you run and how many players are online, not by which framework sits underneath. A heavily scripted VORP server and an equally scripted RSG-Core server need roughly the same hardware — around 6–8 GB for a 12–24 player RP server. Size your host to your script load and player count, not to your framework choice.