FAQ
Main answers for operators choosing a FiveM framework. Deep dives: Compare, Getting Started, migrate cheat sheet.
FiveM · GTA V · Roleplay
Framework answers for Los Santos cities — stack, migrate, license, and ops.
Atlas is a premium independent native FiveM framework for GTA V roleplay servers. It provides a complete commercial foundation — identity, sessions, permissions, economy contracts, and a growing premium resource ecosystem — built from the ground up, not a QBCore or ESX fork.
No. Atlas is a native stack with its own identity, money, jobs, and Atlas.* APIs. We publish migrate guides from QBCore, ESX, and vRP — remounting gameplay onto Atlas contracts, not running those frameworks underneath.
Commercial GTA V roleplay cities that want a long-term foundation: clean APIs, server-authoritative gameplay, a premium stack, and controlled distribution. Not weekend dump servers or leaked Tebex stacks.
Yes. Atlas targets modern FXServer with OneSync enabled. Run a valid Cfx.re license and a healthy MariaDB backend before going live.
Core gameplay and resources are Lua on the FiveM runtime, with premium NUI surfaces across the stack. Docs and tutorials walk the Atlas.* Lua contracts.
Atlas focuses on native identity, one inventory door (Atlas.Inventory), server-authoritative money, and production habits like migration locks and audited admin. QBCore has a huge script market; Atlas is a cleaner commercial foundation with QBCore migrate how-tos.
ESX is a mature open ecosystem with many legacy patterns. Atlas ships a single licensed stack — identity through verticals — with explicit money/item APIs and no client-trusted economy. Use our ESX remount tutorial when you switch.
Qbox leans on an open ox-centric ecosystem you assemble. Atlas ships as an all-in-one licensed stack with one brand language and public migrate paths from other frameworks.
Not as drop-in. Scripts that call QBCore/ESX exports need remounting onto Atlas.* (money, items, jobs, player). Many ox_* resources still fit because Atlas already wires ox_lib, ox_target, and ox_inventory behind Atlas.Inventory.
A framework owns identity, sessions, permissions, money, and inventory contracts so every vertical speaks the same language. Script packs alone leave you gluing conflicting player/item systems every update.
Yes. Atlas publishes image-led tutorials for remounting money, items, and jobs from QBCore, ESX, and vRP onto Atlas.* APIs without trusting the client for economy actions.
Yes. Follow the From QBCore tutorial and the framework cheat sheet: map GetPlayer / money / items / jobs to Atlas APIs, then retire QBCore once gameplay is remounted.
Schema and identifiers differ per framework. Atlas uses its own tables via AutoSQL. Expect a planned cutover or import path — not a silent overnight convert of every legacy column. Contact access review if you need migration coaching.
Depends on city size and custom scripts. A lean city with clear money/item/job boundaries remounts faster than a decade of forked QB resources. Start with install docs, then the matching From QB / ESX / vRP guide.
Yes. Gameplay talks to Atlas.Inventory; only atlas_inventory touches ox_inventory. ox_lib and ox_target are wired and themed for Atlas slim-premium UI.
Yes. atlas_multichar provides cinematic character selection and Atlas spawn is server-authored so clients cannot freely trust privileged placement.
Yes. Atlas ships a slim premium HUD and ACE-audited admin tools as part of the core commercial stack — not a random third-party paste.
Yes. Cash/bank (and related economy actions) go through server Atlas APIs. Do not trust the client for balances, payouts, or item grants.
AutoSQL is Atlas’s idempotent schema runner: CREATE TABLE IF NOT EXISTS and ensureColumn-style upgrades so restarts are safe. You don’t ship numbered migration dumps per resource for core Atlas tables.
Yes. Player-facing strings live in a central locales hub (atlas_extras). Set atlas:locale (and keep ox:locale in sync). Docs cover L() / AtlasLocale for Lua and NUI.
Atlas’s roadmap includes deep verticals (phone, garages, fuel, and more). Some surfaces are live in the stack; showcase marks others as coming soon. Request access for current build contents.
Yes. That’s the point. Use documented Atlas.* exports/events, keep economy on the server, and follow creating-a-resource + scripting tutorials.
FXServer with txAdmin, MariaDB (or MySQL-compatible), a valid Cfx.re license key, and OneSync enabled. Healthy boot order starts with oxmysql → ox_lib → atlas_core.
Both work. Most production cities run Linux FXServer. Atlas resources are standard FiveM artifacts — follow your host’s FXServer + MariaDB setup, then Atlas getting-started.
Roleplay cities need CPU, RAM, and a fast MariaDB disk like any serious FiveM server. Atlas doesn’t replace bad hosting — it expects a stable FXServer and database.
Start at /docs/getting-started, then configuration and atlas-health. Tutorials cover first boot, character/spawn, and first admin.
Check boot order (oxmysql → ox_lib → atlas_core), MariaDB credentials, OneSync, and the atlas-health docs. Discord support is for approved licensees after access.
Atlas is proprietary with controlled commercial distribution. Public list prices are coming soon. Request access on the site; approved licensees receive builds through authorized channels.
Submit the Get Access form with your city details. We review fit, then follow up (typically via Discord). Builds are not published as public dumps.
Premium tiers are listed conceptually on /pricing; dollar amounts are coming soon / not published yet. Join the access list to be notified when SKUs drop.
No. License terms forbid redistribution, leaks, and unauthorized Tebex-style resale. Violations revoke access. See Legal → License and community Rules.
Distribution is invite-controlled. Showcase stills and docs are public; full builds go to approved operators. Ask during access review if a guided walkthrough is available.
Approved licensees get Discord operator channels and docs/tutorials. Network/Custom tiers (when quoted) can include deeper onboarding — see Pricing.
No framework replaces a good anti-cheat and staff process. Atlas reduces common exploit surfaces by keeping money/items/spawn server-authoritative and auditing admin actions.
No. NUI is untrusted. Validate every economy and ownership action on the server with Atlas APIs — same rule as any serious FiveM stack.
Atlas admin is designed around ACE permissions and audited staff tools. Exact log destinations depend on your ops setup — follow admin docs after you have a build.
Atlas