White-Label Community Platform: No "Powered By" Badge.

Why it matters

Most platforms charge extra to remove their badge. Mobieus ships without one.

You have seen the pattern. A SaaS platform injects a "Powered by X" badge on free and lower tiers, then charges $50 to $200 per month to remove it. Your community becomes an advertisement for someone else's product. Your members see a brand that is not yours on every page load.

Mobieus does not do this on any tier. Not on Starter. Not on Pro. Not on Creator Plus. Not on Sovereign. Your community is your brand from the first day you launch it.

What "white-label" actually means here

White-label at Mobieus is not a premium add-on or an enterprise checkbox. It is the default state of every tenant.

Your members never see the word "Mobieus" anywhere in the tenant UI. There are no footer links back to mobieus.io. There are no login screen watermarks. There are no email signatures that mention our name. The entire experience presents as your product.

The login system (mobieusID) is configured per-tenant with your logo, your colors, and your community name. When a member signs in, they see your brand on the authentication screen.

Even email notifications come from your domain. The SMTP relay sends through your configured sender address. Recipients see your community name in their inbox, not ours.

What you control

Custom domain

Point community.yoursite.com at your Mobieus tenant. We handle TLS certificates automatically. No manual SSL configuration required. Available on Pro, Creator Plus, and Sovereign.

On Starter, your community runs at slug.mobieus.io. That is the only place the mobieus.io domain appears to your members.

Logo and favicon

Upload your logo once. It appears in the site header, the login screen, email templates, and the mobile bookmark icon. No manual placement across different surfaces. One upload, every touchpoint.

Color palette

Set your primary, secondary, accent, and background colors. The entire UI adapts: buttons, links, cards, navigation bars, hover states, and focus rings. CSS custom properties make the color system consistent across every page without manual per-element styling.

Community name and tagline

Your community name appears in the header, the browser tab title, meta tags, and Open Graph previews. Your tagline sits in the header and the site description. Both are editable at any time from the admin panel.

Email branding

Email templates carry your logo and community name. The dark-theme email layout uses your color palette. The canonical footer shows your community information. Not ours.

Configure your sender name and reply-to address from the admin panel. Members reply to your address, not a mobieus.io address.

Suite product theming

mobieusHelp (help desk) and mobieusLearn (LMS) inherit your theme at provision time. Same palette, same logo, same typography. When a member moves from your community forums to the help desk or a course, the visual experience stays consistent. No jarring brand switches between products.

SEO metadata

Set custom meta descriptions, Open Graph images, and structured data for your tenant. Search engines and social previews show your brand, your description, and your imagery.

Where the tenant admin configures all of this

Everything lives in three tabs inside your admin panel.

Admin > Configuration > Branding. Upload your logo, set your color palette, enter your community name and tagline. Changes apply immediately across all pages.

Admin > Configuration > Domain. Enter your custom domain and follow the DNS verification steps. Mobieus provisions the TLS certificate automatically after verification passes.

Admin > Configuration > Email. Set your sender name and reply-to address. Preview the email template with your branding before going live.

Suite products (help desk, LMS) inherit branding automatically at provision time. No separate configuration needed per product.

How it works under the hood

Each tenant is fully isolated. Own database, own PHP-FPM process, own configuration files. No shared UI elements between tenants. No shared stylesheets. No shared templates.

Theme settings are stored in the tenant's configuration and applied at render time. CSS custom properties propagate your color choices to every component. When you change your primary color, every button, link, and accent in the UI updates in a single pass.

Suite products receive the same branding during provisioning. The provisioner reads your tenant config, generates product-specific theme files, and applies them before the product goes live. This is not a runtime overlay. The theme is baked into each product's configuration so it loads fast and works offline.

The "no badge" policy

This deserves its own section because it is a deliberate product decision, not an oversight.

Many SaaS platforms use the "Powered by" badge as a growth hack. Free users become walking advertisements. Removing the badge becomes a paid feature. Some platforms charge more for badge removal than for core functionality.

Mobieus takes the opposite position. Your community exists to serve your members, not to advertise our platform. Badge removal is not a feature because there is no badge to remove. This applies to every tier, including Starter.

Who this is for

Pricing and availability