LifeRaft OSTM

Community add-on

RLX Federation

Optional federation boundary for ActivityPub-style identities, inbox/outbox review, instance policy, moderation, and allow/block controls.

CommunityCategory
0.1.0Version
FoundationRelease stage
$64.85 · AdvancedLicense
Back to catalog
Community add-on

About this add-on

RLX Federation for LifeRaft OS

Optional federation boundary for ActivityPub-style identities, inbox/outbox review, instance policy, moderation, and allow/block controls.

At a glance
  • Admin-managed content and settings
  • Public pages with clean presentation
  • Designed to run as an optional RLX module
  • Keeps member value inside the owned community instead of losing activity to third-party tools
rlx-federation Version 0.1.0 $64.85 · Advanced Foundation

Capabilities and outcomes

How RLX Federation 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.

Keeps member value inside the owned community instead of losing activity to third-party tools

Supports participation, discovery, support, and communication from one coherent product surface

RLX Federation can be packaged as an optional upgrade, bundle component, or project-specific module

Community builds that need RLX Federation without forcing it into every install

Add-on-specific scope

What RLX Federation manages

This module manages federation as its primary customer-facing records.

Standalone value

What it does by itself

RLX Federation can run as its own Community 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 Activity, RLX Notifications, RLX Defender, and RLX Compliance, RLX Federation 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

  • Community builds that need RLX Federation without forcing it into every install

Workflow

How it fits into a real build

  1. pending, approved, quarantined, blocked, delivered, failed, archived

Works well with

The strongest builds connect the right modules

RLX Federation becomes more valuable when it is paired with the workflows around it. Common pairings include RLX People, RLX Activity, RLX Notifications, RLX Defender, RLX Compliance, 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 Federation

What does RLX Federation do?

Optional federation boundary for ActivityPub-style identities, inbox/outbox review, instance policy, moderation, and allow/block controls.

Who is RLX Federation best for?

Community builds that need RLX Federation without forcing it into every install.

Can RLX Federation run by itself?

RLX Federation can run as its own Community 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 Federation 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 Activity, RLX Notifications, RLX Defender, and RLX Compliance, RLX Federation 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 Federation?

RLX Federation commonly pairs with RLX People, RLX Activity, RLX Notifications, RLX Defender, RLX Compliance. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Federation?

RLX Federation should be launched with its real data model and public routes in mind. Optional integrations: rlx-people, rlx-activity, rlx-notifications, rlx-defender, rlx-compliance.

How much does RLX Federation cost?

RLX Federation 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 Federation?

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 Federation for deployment?

Foundation module: intended as a building block and may require project-specific configuration before customer launch.

How does RLX Federation fit into a real LifeRaft OS build?

pending, approved, quarantined, blocked, delivered, failed, archived.

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.

Coming soon

Want RLX Federation in your LifeRaft OS build?

RLX Federation 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.