Core system

The part of the platform every serious build needs first.

The core is not the flashy part. It is the part that saves the build later: accounts, forums, pages, permissions, admin controls, moderation, responsive mobile/touch layouts, device handoff, and the add-on runtime that lets the site grow without turning into a pile of one-off code.

Browse Add-ons Public Docs

What core means

Core means the boring problems are already handled.

Every community, product hub, studio site, or creator platform eventually needs the same operating layer. LifeRaft OS puts that layer in the base so add-ons can focus on the business workflow instead of rebuilding login, permissions, pages, admin screens, and structure again.

Core

Members and identity

Accounts, profiles, roles, permissions, verification, and admin control over who can see, post, manage, and participate.

Core

Forum and content base

Discussion, public pages, navigation, moderation, docs-style content, and the structure a serious community needs to feel owned.

Core

Mobile and touch layer

Responsive public and admin surfaces, touch-friendly controls, and device handoff flows are built into the core instead of treated as a theme afterthought.

Core

Admin operating layer

Settings, add-ons, imports, exports, permissions, backups, logs, and launch controls live in one backend instead of scattered tools.

Core

Add-on runtime

The core loads optional systems cleanly, so a build can become commerce, support, creator media, studio bridges, or virtual-platform operations later.

Why it matters

You can launch small without choosing a small future.

A project may begin as a forum and a few pages. Later it might need paid downloads, subscriptions, support tickets, analytics, game systems, a studio bridge, or virtual-platform vendor tools. The core keeps those futures connected instead of forcing a platform migration when the project starts working.

Public vs licensed

The public site explains the product. Licensed docs explain the machinery.

The landing pages should help someone understand why they need LifeRaft OS and which path fits them. The deeper setup notes, routes, data structure, deployment steps, and operator details belong with the licensed package after someone is working with the system.

Current catalog

254 add-ons across 24 product families

The core keeps the site coherent. Add-ons create the differences that matter to each buyer: creator tools, commerce, media, gaming, operations, studio bridges, virtual-platform packages, and professional community workflows.