Game Engines add-on
RLX OrB Engine
Secure, failure-isolated transport between OrB Engine projections and LifeRaft OS.
About this add-on
RLX OrB Engine for LifeRaft OS
RLX OrB Engine is the private transport boundary between OrB Engine and
Secure, failure-isolated transport between OrB Engine projections and LifeRaft OS. Use it when a customer package needs a focused capability that should stay optional, sellable, and supportable.
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Keeps the core install lean while preserving room for specialized customer requirements
Capabilities and outcomes
How RLX OrB Engine 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.
Adds a sellable capability without forcing unrelated workflows into every package
RLX OrB Engine can be packaged as an optional upgrade, bundle component, or project-specific module
Game Engines builds that need RLX OrB Engine without forcing it into every install
Standalone value
What it does by itself
RLX OrB Engine can run as its own Game Engines 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 People, RLX Notifications, RLX Related, and RLX MyOrB, RLX OrB Engine 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
- Game Engines builds that need RLX OrB Engine without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX OrB Engine and review its add-on settings
- Configure the module settings and permissions
- Add the records, content, media, or rules this module manages
- Review public pages and backend empty states before launch
Works well with
The strongest builds connect the right modules
RLX OrB Engine becomes more valuable when it is paired with the workflows around it. Common pairings include RLX People, RLX Notifications, RLX Related, RLX MyOrB, 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.
Package QA
Confirm the module fits the selected product package and does not expose unused workflows.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX OrB Engine
What does RLX OrB Engine do?
Secure, failure-isolated transport between OrB Engine projections and LifeRaft OS.
Who is RLX OrB Engine best for?
Game Engines builds that need RLX OrB Engine without forcing it into every install.
Can RLX OrB Engine run by itself?
RLX OrB Engine can run as its own Game Engines 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 OrB Engine 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 People, RLX Notifications, RLX Related, and RLX MyOrB, RLX OrB Engine 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 OrB Engine?
RLX OrB Engine commonly pairs with RLX People, RLX Notifications, RLX Related, RLX MyOrB. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX OrB Engine?
RLX OrB Engine should be launched with its real data model and public routes in mind. Routes: Event delivery uses the OrB hook contract:, Command poll and acknowledgement requests use:, For a GET poll, the exact body is the empty string. Query parameters are not, part of the signature and are independently clamped and validated. Optional integrations: rlx-people, rlx-notifications, rlx-related.
How much does RLX OrB Engine cost?
RLX OrB Engine 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 OrB Engine?
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 OrB Engine for deployment?
Preview module: available for evaluation and scoped deployments while runtime evidence and product polish continue to mature.
How does RLX OrB Engine fit into a real LifeRaft OS build?
Activate RLX OrB Engine and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.
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 OrB Engine in your LifeRaft OS build?
RLX OrB Engine 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.