Core capabilities
- Service state patterns
- Duty/operation hooks
- Shared service API
- Notification/chat integration hooks
- Bridge ready job identity
- Configurable workflows
NOTWEN / SERVICES
Notwen Services
Operational building blocks for public service roles without turning every service into one oversized resource.
FRAMEWORK BRIDGESESXQBCoreQboxCustom
STATUSIn development
RUNTIMEFiveM / CFX
MODELNotwen native
DOCSIncluded
CURRENT STATEIn development
Open documentation
The resource page is public for architecture and integration context. Purchase will open when the product is ready.
PRODUCT SCOPE
What this resource owns.
Shared operational patterns for police, EMS, mechanics and RP service workflows.
Where it fits
- Police
- EMS
- Mechanic
- Public service operations
INTEGRATION MODEL
Own the domain. Bridge the server.
Framework-specific access stays at the integration edge so product behavior can remain consistent across server stacks.
ESX · QBCore · Qbox · Custom
Framework bridges can map jobs and players from ESX, QBCore, Qbox or custom RP frameworks.
Predictable responsibilities
Each service feature should consume focused shared APIs rather than continuously scanning unrelated state.
Where it makes sense
RP communities that want service systems to share contracts while keeping ownership clear.
TECHNICAL CONTEXT
Read the contract before deployment.
Purchase and delivery will be enabled when the resource is ready. Documentation covers dependencies, installation, configuration, APIs and troubleshooting.