Most FiveM servers die in the first week. It's never because the game is too hard or the market is saturated. It's because the launch sequence was wrong, a $200 script stack installed on a $5 VPS, or a public launch before the economy works, or a Tebex store that goes live three weeks after the Discord hype peaks.
This is the exact seven-day order we walk Academy Server Owner path students through. It's not theoretical, it's the order because we've seen every alternative order fail.
The single biggest predictor of whether a FiveM server survives month one is not the script budget. It's whether Days 4-5 (script stack compatibility + Tebex setup) happened before the public launch on Day 6.
Day 1, Decide what the server is, then buy the VPS
Before you touch a terminal, write three sentences:
- Who is this server for? (Age range, RP seriousness level, language.)
- What's the one-sentence pitch you'll give a stranger?
- How is it different from the top five already-running servers in your language?
If those three sentences don't exist, go no further. A VPS bought before the pitch is a pure cost burn.
Once they exist, buy the VPS. Minimums for 32 slots: 4 vCPU (3.5 GHz+), 8GB RAM, NVMe SSD, low-latency region. The region matters more than the CPU benchmark, latency to your target players is the metric, not GHz. Elite members get one month free on our partner host, included, which covers the entire VPS cost during the Day 1-30 survival window.
Day 2, Boot FXServer and txAdmin
First, generate a free server license key from the Cfx.re Portal (portal.cfx.re) — it replaced the old Keymaster in late 2025 and you need a key even for a local test boot. Then download the recommended FXServer artifact and run it: txAdmin ships bundled inside FXServer (since 2020), so it launches automatically on first run — no separate install. Open the printed localhost:40120URL to finish the setup wizard. If you get through Day 2 with txAdmin running and reachable from your browser, you've cleared the single biggest infrastructure gate. The other 95% of Day 2 failures are firewall rules or the VPS provider's port-blocking policy (ports 30120 and 40120), all faster to solve with someone on voice in the Academy Discord than alone at 3am.
Day 3, Pick and install the framework
This is the decision that locks in the next year of your script purchases, your configs, and your support burden. See the full ESX vs QBCore vs QBox comparison for the decision tree. For most 2026 launches we default to Qbox (the actively developed, QBCore-compatible framework) or QBCore if you want the largest ready-made catalog; ESX if your audience or existing scripts are already there.
Install the framework, start the server, connect with your Cfx account, walk around. If you can't walk around by end of Day 3, escalate before Day 4. Days 4-7 compound on top of a working base.
Day 4, The core script stack (the gate most servers fail)
The average survival-grade server runs roughly eight core resources: inventory, housing, phone, dispatch, garage, jobs, core HUD, and a money/banking system. The failure mode is not picking the wrong resources, it's picking resources that don't work well together.
Defaults we'd pick for a QBCore server launching today:
- Inventory, ox_inventory (open-source, high quality) or qs-inventory (Quasar Store) if you want the phone/ housing integrations bundled.
- Housing, qs-housing is what most of our students pick after trying three alternatives. Not because it's free; because the conflicts are fewer.
- Phone, the modern consolidated phones (npwd-derived or commercial) save more support tickets than they cost.
- Dispatch, sleek or linden-style dispatch. Don't cheap out here, a broken dispatch is an immediate RP breaker.
Spend Day 4 installing the stack, config-mapping shared tables, and stress-testing with a small alt-account rotation. Don't launch if two resources are producing errors in the console. That's tomorrow-you's ticket queue.
Day 5, Tebex store, branding, rules
Stand up the Tebex store with at least three packages: a cheap supporter tier, a priority-queue tier, and a vehicle/cosmetic cap bundle. Get the Tebex icon/cover branded properly, a blank Tebex is a conversion killer. Then write the server rules. Then take the screenshots you'll use for Discord and FiveM's server list.
If you skip Day 5 and launch on Day 6, you will lose the one week of peak Discord hype without having anything to sell. Every Academy Server Owner path student has this tattooed on their brain by the second milestone.
Day 6, Soft launch to a small audience
Not a public launch. A soft launch: invite 20-50 people from your Discord, your local friends, your regulars from a previous server. Give them a priority role. Watch what breaks. Fix it live.
The soft launch is the stress test. If your VPS falls over at 20 players, you will not survive 80 on Day 7. Better to find out on Sunday evening with friends than Monday at peak hours with strangers.
Day 7, Public launch, then iterate
Open the server to the FiveM server list. Open the Tebex store. Post in the relevant communities. Then do not leave, the first 12 hours post-launch is where your retention rate is set. Be in the server, in the Discord, and on voice.
After Day 7, the game changes: launch-week survival becomes retention-grind. That's the next playbook.
What we'd change if you have Academy Elite or Enterprise
Most of the Day 2, Day 4, and Day 6 failure modes are the reason the Academy Elite tier exists. When we review a launch plan on a weekly call, the single most common intervention is condensing this 7-day plan into 3-5 days without losing the Day 4 compatibility audit.
If you're launching in the next 30 days and the Day 4 stack audit is what you need most, apply through the Enterprise track.