Operations
RLX Integration Registry
Canonical shared-service ownership, cross-entity links, provider health, and integration contracts that prevent duplicate subsystem implementations.
What it does
Features at a glance
- Canonical shared-service ownership, cross-entity links, provider health, and integration contracts that prevent duplicate subsystem implementations
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
- Activate RLX Integration Registry and review its add-on settings
- Canonical shared-service ownership, cross-entity links, provider health, and integration contracts that prevent duplicate subsystem
- Add the records, content, media, or rules this module manages
Before you choose
Common questions
What does RLX Integration Registry do?
Canonical shared-service ownership, cross-entity links, provider health, and integration contracts that prevent duplicate subsystem implementations.
What does RLX Integration Registry need to run?
RLX Integration Registry 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 Integration Registry 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 Integration Registry part of your build.
Discuss the fit, requirements, and next steps for your project.