Choosing The Right Starting Point
Most LifeRaft OS projects should not begin by turning on every add-on. The best launch usually starts with the smallest package that supports the real customer workflow, then grows as the community proves what it needs.
Core Launch
Choose Core Launch when the immediate need is an owned member community with forums, profiles, pages, permissions, moderation, and admin control.
This fits early product communities, private groups, support communities, founder-led communities, and projects moving away from scattered social channels. It gives the project a stable home without forcing commerce, media, or advanced operations into the first release.
Business Community
Choose Business Community when the site needs a professional customer-facing layer: docs, support, forms, roadmaps, announcements, analytics, and protected resources.
This is a strong fit for software products, agencies, client portals, course operators, productized services, and companies that want customer conversations and support history on their own platform.
Creator Commerce
Choose Creator Commerce when the community also needs media, downloads, memberships, galleries, product pages, coupons, affiliate paths, or digital content workflows.
This path is useful for creators, artists, model agencies, resource sellers, marketplace operators, educators, and small media businesses that want community and commerce connected instead of separated.
Gaming Or Studio Community
Choose Gaming or Studio Community when a project needs forums, updates, support, entitlements, analytics, creator news, or bridge add-ons around a game, virtual world, or external client.
The public site explains the positioning and available bridge add-ons. Licensed packages carry the production connector details.
Operations And Private Access
Choose an operations-heavy package when the project needs agreements, approvals, analytics, funnels, forms, roadmaps, kanban boards, timeline records, policy acknowledgements, or private preview gates.
This is where add-ons like RLX NDA, RLX Funnels, RLX Analytics, RLX Forms, RLX Roadmap, RLX Kanban, and RLX Timeline work together. A member can be verified and still need to accept a specific agreement before accessing a private build, client area, beta, or protected resource.
A Practical Rule
If the first launch cannot explain why an add-on is needed, leave it off. LifeRaft OS is built so the project can activate more workflows later without abandoning the core member, content, and admin base.