Community

Build the conversation around the work.

The Rise community is being designed around two complementary spaces: durable forums for knowledge and discussion, and Discord for faster real-time connection.

  • Rise Forums
  • Official Discord
  • Product communities
Community direction

Two spaces. Different strengths.

Forums and Discord solve different communication problems. Rise intends to use both rather than forcing every conversation into a single format.

01DURABLE
Rise Forums

Knowledge that stays useful.

Structured discussions, questions, accepted solutions, guides, product ideas, searchable troubleshooting, and conversations designed to remain useful over time.

Searchable · Structured · Persistent
02REAL TIME
Official Discord

Conversation at community speed.

Faster discussion, announcements, community interaction, and live conversation can complement the deeper knowledge captured in the forums.

Immediate · Social · Connected
Product communities

Give each product room to develop its own conversation.

Rise products remain independent. Community spaces should preserve those boundaries while making it easy to move across the wider ecosystem.

01Rise Command Center

Operations & platform

Discuss RCC concepts, workflows, integrations, operational patterns, ideas, and the systems surrounding the Rise platform.

02Rise Launcher

Software ecosystem

A future space for releases, installation and update discussions, product discovery, troubleshooting, and Launcher workflows.

03Rise Creator Toolbox

Creator workflows

Discuss Creator Toolbox, Creator Vault, protection workflows, recovery concepts, professional workflows, and creator-focused ideas.

Forum direction

Organize discussion around what people actually need.

The detailed forum architecture will be designed before the community platform is implemented. These areas establish the public direction without prematurely locking the final forum structure.

01NEWS

Announcements

Official Rise announcements, product updates, release information, maintenance notices, and important community communications.

02HELP

Questions & troubleshooting

Searchable product discussions where community members can ask questions, share context, and help surface useful solutions.

03IDEAS

Ideas & feature requests

Structured conversations around product ideas and feature proposals, with clear status language that avoids turning discussion into an accidental promise.

04GUIDES

Guides & knowledge

Durable tutorials, workflows, explanations, accepted solutions, and community knowledge that remain useful beyond a real-time conversation.

05SHOW

Projects & showcases

A place for community members to share useful setups, workflows, projects, discoveries, and ways they are working with Rise products.

06GENERAL

General community

Broader Rise conversations that do not belong to one product or technical category while still following community standards.

Community operations

One operating picture for Rise staff.

As the community platform develops, Rise intends to centralize appropriate community supervision and support operations through Rise Command Center rather than creating disconnected internal control systems for every channel.

Permissions should remain explicit. Community moderators, support staff, product staff, and owners can have different responsibilities without receiving unrelated privileged access.

Explore Rise Command Center
Community principles

Make participation useful and manageable.

Community systems work best when communication, moderation, support, and product boundaries are designed deliberately rather than added after problems appear.

01

Keep useful knowledge durable

Important answers, guides, and discussions should remain discoverable instead of disappearing into an endless real-time feed.

02

Make real-time conversation easy

Discord can complement the forums with faster discussion, community interaction, announcements, and other live experiences.

03

Moderate with accountability

Community operations should support clear permissions, reporting, appropriate staff intervention, and auditable moderation.

04

Separate community from private support

Public discussion can solve many problems, but account-specific or sensitive issues need a controlled path into official support.

Community availability

Build the foundation before opening the doors.

Rise will publish verified forum access, the permanent official Discord invitation, community standards, moderation guidance, and participation details as those services become ready for public use.

COMMUNITY STANDARDPublic community links should point to real, supported spaces. Until then, Rise will not manufacture activity or publish temporary destinations as if they were permanent.