How Xon Sight fits together

Overview

Nothing here gives a website a live video feed - Xon Sight (the in-game resource) has no documented way to stream actual camera frames out of the game. What moves between the pieces below is: finished clips (uploaded after the fact), a schematic position feed ("who's recording and roughly where"), and the portal's own pages, which the tablet and phone app simply display in a window rather than rebuilding.

Multiple servers, one portal

One Xon Sight deployment can host more than one FiveM server, each in its own dedicated MySQL database - nobody's evidence, live roster, or alerts end up in anyone else's. Each of these communities gets its own API token; point your bodycam script at that token instead of the shared webhook key and everything it sends lands in that community's own database from then on.

Scope today: only Dashboard/Evidence/Live are tenant-aware. Cases, the Assistant, the public Community tip line, Analytics, and Admin itself still run against this portal's own original database regardless of which community you're on - a deliberate, incremental rollout rather than a half-migrated everything-at-once. A self-signed-up community's admin sees their own tenant data as soon as they're logged in, on this same primary URL - dedicated subdomains (<slug>.opslabsystems.cloud) work too once the operator points a wildcard DNS record here, but aren't required to get started.

Xon Sight's webhook contract is generic - it doesn't require OPS Phone or any other specific resource, it just needs something to POST evidence to it. OPS Phone is the reference bodycam implementation this portal was built against: a bodycam app on an officer's in-game phone. When they stop recording, the finished clip uploads to wherever LB Phone's camera upload is configured to put it (Fivemanage, S3, etc. - this site never touches the raw video), and a webhook tells the portal the clip exists, who submitted it, and a caption. The LB Phone App below can submit evidence the same way, straight from LB Phone's own camera, if you'd rather not run a separate bodycam resource at all.

• Sends the device serial automatically, so the Evidence viewer's Metadata tab fills itself in
• Fires an alert (shots fired, weapon drawn) the instant it happens - raises the banner on the Live page
• Pushes the live roster on start/stop, not just on a timer - a new recorder shows up on /live within ~1s
• Optional chest-mounted camera mode for a true body-worn-camera angle instead of free-look

Everything OPS Phone sends lands here. It's the one place all of it gets reviewed, organized, and searched - the tablet and phone app don't have their own separate view of this data, they just open these same pages. Everything below needs a staff login except the public tip line.

A stock in-game prop an officer holds and reads from without tabbing out of GTA. It's the real portal in a window, not a reimplementation of it.

• Stock GTA prop (prop_cs_tablet) - no custom model to source or stream in
• Opens on a configurable key (F6 by default); closes with the same key, the on-screen ×, or Esc
• Logs in once and stays logged in between uses, same as a normal browser tab

Installed as a proper app icon on an officer's LB Phone - open it from the home screen like any other app. It's the only piece that's two things at once: a viewer onto the portal, and - with a tap of its "Record evidence" button - an independent way to submit evidence too, using LB Phone's own camera. Third-party phone frameworks work with Xon Sight through this same path: nothing about the webhook cares what recorded the footage.

• Records video with LB Phone's camera and posts it straight to the evidence webhook - no bodycam resource required
• The webhook key stays server-side (server.lua) - never exposed to the NUI/browser layer
• Capture can be turned off (Config.AllowCapture = false) to ship this as a viewer-only app instead
• Registers itself via lb-phone's own AddCustomApp export - nothing to edit in lb-phone's config
• Free, paid, or installed on every phone automatically - your choice per server
• Same persistent login as the tablet, inside the phone's own NUI browser

Requirements

Xon Sight can host the portal for you - there's nothing to deploy, patch, or keep online yourself. With a hosted portal, the only real requirement is the FiveM side: a server to add resources to, and something sending it evidence over its webhook - OPS Phone is the reference implementation, but it's not mandatory; the LB Phone app can submit evidence directly from LB Phone's own camera instead. Self-hosting the portal instead is supported too, if you'd rather run your own.

Self-hosting behind multiple gunicorn workers? Point RATELIMIT_STORAGE_URI at a shared backend (e.g. redis://...) - the default in-memory limiter counts per worker, not per actual visitor, once you're past a single process.