Platform Operations add-on
RLX Uptime
Privacy-aware HTTP monitors with response timing, manual verification, public status cards, expiry, and incident-ready integration points.
About this add-on
RLX Uptime for LifeRaft OS
RLX Uptime monitors public HTTP and HTTPS endpoints without exposing private infrastructure. Each monitor supports Public, Logged in, Private staff, or Only me visibility, along with pausing and expiry. Manual checks record the HTTP response and elapsed time.
Privacy-aware HTTP monitors with response timing, manual verification, public status cards, expiry, and incident-ready integration points. 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 Uptime 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 Uptime can be packaged as an optional upgrade, bundle component, or project-specific module
Platform Operations builds that need RLX Uptime without forcing it into every install
Add-on-specific scope
Know what is online before your users do
Fast, privacy-aware service monitoring with response timing and clean public or private status views.
This module manages monitors as its primary customer-facing records.
Standalone value
What it does by itself
RLX Uptime can run as its own Platform 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 Staging, RLX Subdomains, and RLX Transfer, RLX Uptime 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
- Platform Operations builds that need RLX Uptime without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Uptime 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 Uptime becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Staging, RLX Subdomains, RLX Transfer, 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 Uptime
What does RLX Uptime do?
Privacy-aware HTTP monitors with response timing, manual verification, public status cards, expiry, and incident-ready integration points.
Who is RLX Uptime best for?
Platform Operations builds that need RLX Uptime without forcing it into every install.
Can RLX Uptime run by itself?
RLX Uptime can run as its own Platform 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 Uptime 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 Staging, RLX Subdomains, and RLX Transfer, RLX Uptime 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 Uptime?
RLX Uptime commonly pairs with RLX Staging, RLX Subdomains, RLX Transfer. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Uptime?
RLX Uptime should be launched with its real data model and public routes in mind. Use the admin settings, permissions, upload rules, and QA checklist to confirm the module is ready for production.
How much does RLX Uptime cost?
RLX Uptime has a Access required 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 Uptime?
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 Uptime for deployment?
Preview module: available for evaluation and scoped deployments while runtime evidence and product polish continue to mature.
How does RLX Uptime fit into a real LifeRaft OS build?
Activate RLX Uptime 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 Uptime in your LifeRaft OS build?
RLX Uptime 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.