Sapeans

Turn an idea into a community people can enter.

Move from a clear community idea to access, discovery, tools, identity, setup guidance, and launch review.

A community needs more than a name and an empty feed.

The choices made before launch shape how people find the community, what they understand, how they enter, and what they can do once inside. Sapeans keeps those decisions in a guided sequence: articulate the purpose, establish access and discovery, select relevant tools, shape the identity, and review the result before launch.

What it makes possible

Begin with purpose and audience

Describe the community, its category, interests, location context, and intended audience. The creation workspace keeps those answers visible so later choices remain connected to the original idea.

Choose how people enter

Configure discoverability and an applicable joining model, including open entry or reviewed requests with questions. Paid entry is managed through the membership system when it is enabled and configured.

Select the right Community Tools

Choose Circles, Tasks, Courses, Games, Marketplace, and Gigs according to the community’s purpose and plan. Recommendation logic can suggest tools, but the builder remains in control of the final selection.

Give the community an identity

Add the initial logo, imagery, colors, and supporting presentation used across discovery and the community shell. More detailed branding, navigation, and domain settings remain available after creation according to plan.

Review before launch

The final stage brings the community brief, access decisions, selected tools, and administrative identity together. Builders can return to earlier stages, and eligible signed-in accounts can launch without recreating account details.

How it works

Brief

Clarify the community name, purpose, category, interests, audience, and location context.

Entry

Choose visibility, joining behavior, questions, and discovery rules.

Tools and setup

Select Community Tools and review setup suggestions that fit the stated purpose.

Identity and launch

Shape the first visual presentation, review the choices, and create the community.

Controls for community builders

Editable foundations

Core information, appearance, Community Tools, profiles, policies, access, and other settings can continue to evolve after creation.

Plan-aware choices

Circles, Tasks, Courses, Marketplace, and Gigs are free community tools. Charging for courses, offers, memberships, or event tickets requires Pro.

One administrative identity

The first administrator is established as part of the flow, using an existing Sapeans account when available.

Plans, permissions, and availability

New standard communities currently receive the plan and trial language shown in the live creation flow. Enterprise creation uses the separate white-label setup path. Tool availability and ongoing limits follow the active plan.

Frequently asked questions

Do I need technical knowledge to create a community?

No coding is required. The creation flow asks for community and operating choices, then uses the existing Sapeans controls to create the workspace.

Can I change the settings later?

Yes. The creation flow establishes a starting point; eligible administrators can later update community details, tools, access, profiles, policies, branding, payments, and other supported settings.

Do all Community Tools come with every plan?

Yes. Circles, Tasks, Courses, Marketplace, Gigs, and games are free. Community owners decide which tools are enabled; charging requires Pro.

Can I use a custom domain?

Custom-domain behavior depends on plan. Sapeans retains visible Sapeans identity, while the current Enterprise description includes advanced identity and white-label controls.