qbcore Server Hosting

qbcore does not need a special host. It needs a host that has already solved the database, because that is where a qbcore install actually fails. Every plan here ships MySQL provisioned and connected before the first resource loads, with txAdmin waiting on its own address. From $9.91 a month.

What qbcore needs from a host

A database that exists before the framework starts

qbcore stores characters, jobs, vehicles and inventories in MySQL through oxmysql. If the database is not created, reachable and populated with the framework SQL when the server boots, qbcore fails on the first query and txAdmin restarts it in a loop. This is the single most common failed install, and it is a hosting question, not a framework one.

Enough memory for a script-dense server

A bare qbcore install is light. A real one is not: ox_lib, ox_inventory, pma-voice, a dispatch system, a phone, a handful of MLOs and a job pack. Budget from the resource list rather than from the framework, and remember that FiveM is single-threaded where it counts, so clock speed beats core count.

txAdmin, with the recipe deployer

The quickest clean install is the txAdmin recipe, which pulls the core resources, installs oxmysql and runs the SQL for you. That only works if txAdmin is reachable on its own address and the database credentials are already valid, which is exactly what a host either hands you or leaves you to arrange.

qbcore, or qbox?

Worth knowing before you commit, because it changes what you install rather than where you host it. qbox is a community fork of qbcore, built around ox_lib, ox_inventory and oxmysql from the start, and it keeps compatibility with most qbcore scripts. Original qbcore is still very widely deployed and has an enormous script ecosystem behind it.

Both install the same way on the same server, and both want the same thing from the infrastructure: a database that is already there, and a panel that can run the recipe. Nothing on this page pushes you towards either. If you are undecided, install one, and if you change your mind the server underneath does not have to change with it.

Installing qbcore on a Flux server

  1. Deploy a plan and open txAdmin on the address the dashboard gives you.
  2. Paste your cfx.re licence key, which is free and issued to your own Cfx.re account.
  3. Run the recipe for qbcore or qbox from the deployer. The database credentials are already in place, so the SQL step does not stall.
  4. Add your own resources and restart. The database, the ports and the panel stay as they were.

The step people lose an evening to, having a working MySQL user and schema before the framework first queries it, is done before you arrive. See the full self-hosting guide for what that step looks like when you do it yourself.

Sizing a qbcore server

The slot number on a plan describes what the hardware comfortably serves, not a licence we sell per head. A qbcore city with a heavy resource list uses considerably more memory per player than a light one, so size from your resource list. Plans run $9.91, $13.28 and $16.39 a month for 32, 48 and 64 slots, with the MySQL database and its sync operator in every tier.

One ceiling that is not ours and applies wherever you host: FiveM caps a server at 48 slots unless your licence key carries a Cfx.re Element Club Argentum subscription, at $15 a month paid to Cfx.re with OneSync enabled. Past 48 without it, the server keeps running but drops out of the public server browser.

Deploy a server for qbcore

Database provisioned, txAdmin running, ports published. First month free if your Flux account is new.

Frequently asked questions

Do I need special hosting for qbcore?

No. qbcore is a set of FiveM resources, so any host that runs a standard FiveM server runs it. What varies is whether the MySQL database is included and already connected, because qbcore will not start without one. On Flux the database ships with every plan rather than as an add-on.

Why does my qbcore server restart in a loop?

Almost always the database or the licence key. If oxmysql cannot reach MySQL, or the framework SQL was never imported, qbcore throws on its first query and txAdmin restarts it. If the cfx.re key is missing, FXServer exits before qbcore is even reached. The console names which of the two it is on the first pass.

How much RAM does a qbcore server need?

Size from the resource list rather than the framework. A modest city is comfortable on the 6GB game server in the 32-slot plan; a script-dense one with large MLOs and a full job pack wants the 8GB or 12GB tiers. FiveM is single-threaded where it matters, so clock speed helps more than extra cores.

Can I switch from qbcore to qbox later?

Yes, and the server does not change. Both are resource sets on a standard FiveM install using the same MySQL database through oxmysql, so a migration is a resources and schema job rather than a hosting one. Take a dump before you start.

Is the cfx.re key mine?

Yes. It is free from the Cfx.re portal, issued to your own account, and pasted into txAdmin after deploying. That is what keeps the server registered to you, so moving hosts later costs you nothing but time.

Keep reading