Operations add-on
RLX Defender
Security, abuse reporting, audit, blocking, watchlist, and bad-actor protection management for RLX communities.
About this add-on
RLX Defender for LifeRaft OS
## Why It Exists
Security, abuse reporting, audit, blocking, watchlist, and bad-actor protection management for RLX communities. Use it when staff need a controlled operating surface for reporting, approvals, planning, security, automation, and decision support instead of another spreadsheet habit. The practical win: admin-managed content and settings.
- 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 Defender 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.
Gives professional teams cleaner visibility, repeatability, and post-launch operating confidence
Operations builds that need RLX Defender without forcing it into every install
Standalone value
What it does by itself
RLX Defender 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 Stats, RLX Automation, RLX Forms, and RLX NDA, RLX Defender 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
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Operations builds that need RLX Defender without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Defender 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
- RLX Defender loads from rlx-defender/addon.php and should be configured through the add-on registry, permissions, and
Works well with
The strongest builds connect the right modules
RLX Defender becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Analytics, RLX Stats, RLX Automation, RLX Forms, RLX NDA, 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 Defender
What does RLX Defender do?
Security, abuse reporting, audit, blocking, watchlist, and bad-actor protection management for RLX communities.
Who is RLX Defender best for?
Admin-managed content and settings. Public pages with clean presentation. Designed to run as an optional RLX module.
Can RLX Defender run by itself?
RLX Defender 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 Defender 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 Stats, RLX Automation, RLX Forms, and RLX NDA, RLX Defender 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 Defender?
RLX Defender commonly pairs with RLX Analytics, RLX Stats, RLX Automation, RLX Forms, RLX NDA. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Defender?
RLX Defender should be launched with its real data model and public routes in mind. Routes: RLX Defender is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold. Add admin screenshots, reporting examples, export behavior, retention policy, permissions, and examples of decisions the module helps staff make. Operations pages should emphasize control, visibility, and repeatable process
How much does RLX Defender cost?
RLX Defender 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 Defender?
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 Defender for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Defender fit into a real LifeRaft OS build?
Activate RLX Defender 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 Defender in your LifeRaft OS build?
RLX Defender 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.