The QBCore ecosystem and its platforms
For most readers of this site, QBCore means one thing: the Lua framework you run on a FiveM server. That is still what the rest of this documentation covers, and nothing on this page changes how a FiveM server is built today.
The project itself now describes a wider scope. This page records what the QBCore project states about that scope, when it was checked, and what it means in practice for someone running a FiveM server.
Provenance and limits of this page
Everything in the status table below is a summary of public statements on qbcore.org as read on 2026-09-11. These are project statements, not verified shipping software. Unlike the resource pages on this site, there is no commit to pin, because for the non-FiveM platforms there is no public implementation to read.
Treat every row other than FiveM and RedM as a plan of record, and re-check the source before acting on it.
qbcore.net is an independent community site. It is not affiliated with, endorsed by, or funded by the QBCore project, and it reproduces none of that project’s sponsor, partner, or funding relationships.
What QBCore says it is
The project describes QBCore as a roleplay architecture layer that sits between a host platform and the world a creator builds, rather than as a game engine, host, or marketplace. In that split:
| Layer | Responsibility |
|---|---|
| Platform | Runtime, networking, hosting, player identity, tools, player ecosystem |
| QBCore | Characters, roles, accounts, permissions, persistence, roleplay systems |
| Creator | World, rules, content, stories, gameplay |
On FiveM this is a description of what the framework already does. qb-core does not provide the
runtime or the networking, and everything on this site about scope and authority follows from that.
See OneSync, scope, and networked entities for where the platform’s
responsibilities end and yours begin.
Platform status as stated on 2026-09-11
| Platform | Stated status | Language and APIs |
|---|---|---|
| FiveM | Established | Lua, FiveM APIs |
| RedM | Established | Lua, RedM APIs |
| Roblox | In active development | Luau, Roblox services |
| UEFN | Research and development | Verse, UEFN and Fortnite APIs |
| CyberMP | Under evaluation, no commitment made | Redscript and a C# .NET SDK |
Read the status column literally. Only the first two rows describe software you can run today. “In active development” and “research and development” are not release announcements, and the CyberMP row is explicitly described as an evaluation that has not been committed to. CyberMP itself is described as a multiplayer modification for Cyberpunk 2077 currently in semi-open beta.
Native implementations, not portable code
The most important technical point for a FiveM developer is what “cross-platform” does not mean here.
The project’s stated position is that each platform receives its own native implementation written in that platform’s language against that platform’s APIs, and that these are not ports of one another. What is shared is the philosophy, the concepts, and a specification. The phrasing the project uses is to standardize semantics rather than syntax.
The practical consequence:
- A
qb-resource written in Lua for FiveM does not run on Roblox or UEFN, and there is no compatibility layer that would make it. - Skills transfer, code does not. A developer who knows how QBCore models characters, roles, and accounts will recognize the architecture elsewhere while writing different code.
- Nothing about this changes the FiveM APIs.
QBCore.Functions.GetPlayer(source)keeps working the way Server functions describes.
RedM is the exception worth naming: it is described as reusing the FiveM Lua foundation and much of its architecture, adapted for RedM’s APIs, because both sit on the same Cfx.re foundation.
Selective expansion
The project states it does not intend to implement QBCore on every possible platform, and lists the conditions it weighs: a meaningful user-generated content ecosystem, developers able to build substantial experiences, roleplay fitting naturally, QBCore providing genuine value, and the platform supporting a native implementation.
This is relevant when reading announcements about any additional platform. Evaluation is a documented step in this project’s process, not a commitment.
What this means for your FiveM server
- Your existing resources keep working.
- The FiveM APIs documented on this site are not deprecated by it.
- There is no migration to perform and no version to upgrade to.
If you want to understand where the architecture is headed, and how to read specification language against the concrete APIs you actually call, continue to QBCore architecture and the specification draft.
Source
- qbcore.org , read 2026-09-11. Status labels, platform list, language and API pairings, and the selective expansion criteria are summarized from that page.