Operations add-on
RLX Telemetry Infrastructure
Self-hosted normalized telemetry capture, hashed source identity, payload integrity, retention controls, and Studio bridge observability.
About this add-on
RLX Telemetry Infrastructure for LifeRaft OS
RLX Telemetry Infrastructure is the engine-neutral, self-hosted event normalization layer for LifeRaft OS Studio bridges. It listens after a connector has validated and stored an Unreal, Unity, VRChat, or Roblox event, then records a privacy-aware source identity, event type, integrity hash, source event reference, and retention timestamp.
Self-hosted normalized telemetry capture, hashed source identity, payload integrity, retention controls, and Studio bridge observability. Use it when staff need a controlled operating surface for reporting, approvals, planning, security, automation, and decision support instead of another spreadsheet habit.
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Turns admin work into a controlled process instead of a spreadsheet habit
Capabilities and outcomes
How RLX Telemetry Infrastructure improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Structured normalized event types for a clearer day-to-day workflow
Structured payload integrity hashes for a clearer day-to-day workflow
Structured optional payload retention for a clearer day-to-day workflow
Structured event-prefix controls for a clearer day-to-day workflow
Structured unreal, Unity, VRChat, and Roblox bridges for a clearer day-to-day workflow
Add-on-specific scope
Own the normalized event layer between game clients and community systems.
RLX Telemetry Infrastructure receives already-validated Studio bridge events, hashes source identity, preserves payload integrity, and applies operator-controlled retention. Raw payload storage remains off by default, while connector signature and nonce validation stays with each canonical bridge.
Standalone value
What it does by itself
RLX Telemetry Infrastructure can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX Analytics, RLX Unreal API, RLX Unity API, RLX VRChat API, and RLX Roblox API, RLX Telemetry Infrastructure can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Operations builds that need RLX Telemetry Infrastructure without forcing it into every install
Workflow
How it fits into a real build
- Activate one or more Studio connectors, register their trusted clients, enable signed endpoints, activate Telemetry Infrastructure, review privacy and retention settings, then monitor normalized sources and recent events from the Operations admin area
Works well with
The strongest builds connect the right modules
RLX Telemetry Infrastructure becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Analytics, RLX Unreal API, RLX Unity API, RLX VRChat API, RLX Roblox API, depending on the customer package and what the site needs to accomplish.
Admin setup
Confirm settings, navigation placement, permissions, and any required starter content before launch.
Public QA
Review the public page, empty states, mobile layout, and activated/deactivated states.
Data QA
Check exports, filtering, retention, audit visibility, and staff-only permissions.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX Telemetry Infrastructure
What does RLX Telemetry Infrastructure do?
Self-hosted normalized telemetry capture, hashed source identity, payload integrity, retention controls, and Studio bridge observability.
Who is RLX Telemetry Infrastructure best for?
Operations builds that need RLX Telemetry Infrastructure without forcing it into every install.
Can RLX Telemetry Infrastructure run by itself?
RLX Telemetry Infrastructure can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Telemetry Infrastructure should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX Analytics, RLX Unreal API, RLX Unity API, RLX VRChat API, and RLX Roblox API, RLX Telemetry Infrastructure can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Telemetry Infrastructure?
RLX Telemetry Infrastructure commonly pairs with RLX Analytics, RLX Unreal API, RLX Unity API, RLX VRChat API, RLX Roblox API. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Telemetry Infrastructure?
RLX Telemetry Infrastructure should be launched with its real data model and public routes in mind. Optional integrations: rlx-analytics, rlx-unreal-api, rlx-unity-api, rlx-vrchat-api, rlx-roblox-api, rlx-milsim-operations, rlx-milsim-after-action.
How much does RLX Telemetry Infrastructure cost?
RLX Telemetry Infrastructure has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Telemetry Infrastructure?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Telemetry Infrastructure for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Telemetry Infrastructure fit into a real LifeRaft OS build?
Activate one or more Studio connectors, register their trusted clients, enable signed endpoints, activate Telemetry Infrastructure, review privacy and retention settings, then monitor normalized sources and recent events from the Operations admin area.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Telemetry Infrastructure in your LifeRaft OS build?
RLX Telemetry Infrastructure is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.