Skip to main content
Providers are the compatibility layer between Atlas resources and your server stack. Most owners can leave providers on auto.

​
Framework providers

ValueResource
autoDetect automatically
qbxqbx_core
esxes_extended
qbqb-core
defaultStandalone/default fallback
customEditable adapter
Auto-detection order: 
qbx_core -> es_extended -> qb-core -> default

​
Inventory providers

ValueResource
autoDetect automatically
oxox_inventory
qbqb-inventory
qsqs-inventory
esxESX legacy inventory
defaultBridge fallback
customEditable adapter
Auto-detection order: 
ox_inventory -> qb-inventory -> qs-inventory -> es_extended -> default

​
UI providers

UI can be set globally: 
setr atlas:ui "auto"
Or per subsystem: 
setr atlas:ui:notify "own"
setr atlas:ui:progress "ox"
setr atlas:ui:input "own"
Common values:
ValueMeaning
autoLet the bridge choose
ownUse Atlas bridge UI
oxUse ox_lib where supported
frameworkUse framework UI where supported
customUse editable custom UI adapter

​
Target providers

The target/interaction provider is set with its own convar, atlas:target (not atlas:ui:target). 
setr atlas:target "auto"
ValueResource
autoDetect automatically
oxox_target
qbqb-target
ownBridge-owned interaction prompt
customEditable adapter
Auto-detection order: 
ox_target -> qb-target -> own

​
When to force a provider

Force a provider when:
  • The resource starts late and auto-detection falls back incorrectly.
  • You have multiple frameworks/inventories installed for migration.
  • You intentionally want bridge-owned UI instead of ox_lib.
  • You are using a custom adapter.
Example: 
setr atlas:framework "qb"
setr atlas:inventory "ox"
setr atlas:ui "own"

​
Startup order matters

Auto-detection reads resource state when atlasBridge starts. If your inventory starts after the bridge, detection can miss it. Correct: 
ensure ox_inventory
ensure atlasBridge
Wrong: 
ensure atlasBridge
ensure ox_inventory
If you cannot control start order, force the provider manually.