Platform add-on
RLX Maps
Geocoded locations, coordinates, privacy-aware maps, nearby discovery, radius filtering, markers, and routes.
About this add-on
RLX Maps for LifeRaft OS
Shared location infrastructure for coordinates, markers, radius discovery, routes, map-provider links, and privacy-aware precision. Verify provider terms, geocoding accuracy, accessibility, and personal-location privacy.
Geocoded locations, coordinates, privacy-aware maps, nearby discovery, radius filtering, markers, and routes. 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 Maps 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.
Structured longitude for a clearer day-to-day workflow
Structured provider/place ID for a clearer day-to-day workflow
Structured marker type for a clearer day-to-day workflow
Structured radius for a clearer day-to-day workflow
Structured directions for a clearer day-to-day workflow
Add-on-specific scope
Map every place that matters
Geocoded locations, coordinates, privacy-aware markers, nearby discovery, radius filtering, routes, and map-provider links.
This module manages map locations as its primary customer-facing records.
Typical workflow states: draft → published → private → archived.
Standalone value
What it does by itself
RLX Maps can run as its own Platform 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 Directory, RLX Destinations, RLX Restaurants, RLX RealEstate, and RLX Events, RLX Maps 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 builds that need RLX Maps without forcing it into every install
Workflow
How it fits into a real build
- Configure settings, navigation, visibility, staff permissions, retention, and related add-ons
Works well with
The strongest builds connect the right modules
RLX Maps becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Directory, RLX Destinations, RLX Restaurants, RLX RealEstate, RLX Events, 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 Maps
What does RLX Maps do?
Geocoded locations, coordinates, privacy-aware maps, nearby discovery, radius filtering, markers, and routes.
Who is RLX Maps best for?
Platform builds that need RLX Maps without forcing it into every install.
Can RLX Maps run by itself?
RLX Maps can run as its own Platform 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 Maps 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 Directory, RLX Destinations, RLX Restaurants, RLX RealEstate, and RLX Events, RLX Maps 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 Maps?
RLX Maps commonly pairs with RLX Directory, RLX Destinations, RLX Restaurants, RLX RealEstate, RLX Events. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Maps?
RLX Maps should be launched with its real data model and public routes in mind. Optional integrations: rlx-directory, rlx-destinations, rlx-restaurants, rlx-realestate, rlx-events, rlx-venues.
How much does RLX Maps cost?
RLX Maps 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 Maps?
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 Maps for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Maps fit into a real LifeRaft OS build?
Configure settings, navigation, visibility, staff permissions, retention, and related add-ons.
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 Maps in your LifeRaft OS build?
RLX Maps 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.