LifeRaft OSTM
← All add-ons

Operations

RLX Defender

Security, abuse reporting, audit, blocking, watchlist, and bad-actor protection management for RLX communities.

ProductionVersion 1.0.0
Product images coming soonA closer look at RLX Defender.

What it does

Features at a glance

  • Gives admins a controlled backend workflow instead of spreadsheets or off-platform tools
  • Makes the platform easier to operate after launch
  • RLX Defender can be packaged as an optional upgrade, bundle component, or project-specific module
  • Risk-scoring criteria for early suspicious-activity triage
  • Case, snapshot, and chargeback dispute support PDF exports

Built for your workflow

Who it’s for

  • Teams replacing scattered records with a shared operational workflow
  • Administrators responsible for day-to-day coordination

Setup and fit

Compatibility

Requires a valid LifeRaft OS core license and a supported installation.

No additional add-on is listed as a required dependency.

From setup to everyday use

A straightforward starting point

  1. Activate RLX Defender and review its add-on settings
  2. Configure the module settings and permissions
  3. Add the records, content, media, or rules this module manages

Before you choose

Common questions

What does RLX Defender do?

Security, abuse reporting, audit, blocking, watchlist, and bad-actor protection management for RLX communities.

What does RLX Defender need to run?

RLX Defender runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.

How ready is RLX Defender for deployment?

Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.

Review the launch checklist
  • 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.

Make RLX Defender part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk