For the team that owns the community roadmap
Community platforms charge per member.Your server does not.
Hosted community platforms price the thing you are trying to grow. Meith runs on infrastructure your team already knows: sign-in federates against GitHub, Google or your own identity server, the theme carries your brand, and the bill follows the machine rather than the member count.
“The platform bill scales with sign-ups.”
The bill here follows the server. Two hundred thousand members cost what two hundred do, and growth stops being a pricing event.
“Customers need yet another password.”
Federated sign-in meets them where they already are — GitHub, Google, or your own identity server — with passkeys and two-factor for the accounts that want them.
“The community looks like the platform, not like us.”
A theme fills documented slots with your brand, and changes how the board looks and nothing else — so a redesign can never cost you the board.
“Custom integrations mean a professional-services quote.”
A plugin is a typed TypeScript package your own team writes against documented hooks. One that misbehaves fails alone, and the board carries on without it.
Sign-in
Your customers, your identity provider, your data.
Members sign in the way the rest of your product signs in: passwords with two-factor, passkeys, or federated against the provider you already run. Every thread, member and message sits in your PostgreSQL — searchable through the API, answerable to your retention policy, and never a data-processing addendum away.
Coming from somewhere else?
There is no clean way out of a Facebook group, a Discord server or a Slack. Most communities start fresh, run both for a season, and move what was worth keeping. A MyBB or phpBB board imports whole — working passwords included.
Not quite you?
The same board, argued four other ways.
One piece of software. What changes is which of its problems you recognise.
Open-source projects
A support forum your project owns: answers with URLs worth pinning, pages that render without JavaScript, and an archive no platform can sunset.
Meith for open-source projects →
MyBB & phpBB boards
The way out of a PHP forum nobody wants to maintain: members, posts and working passwords, imported whole.
Meith for MyBB and phpBB boards →
Agencies & dev shops
One engine, a board per client: each a small config repo you can theme, deploy, upgrade — and hand over whole.
Meith for agencies and dev shops →
Clubs & communities
The volunteer-run version: clubs, associations, clans and groups that need one place everybody can reach.
Meith for clubs and communities →
Own the community you are building.
Scaffold a board, put your theme on it, and point staging at your identity provider — the whole evaluation runs on one machine.
- A repository
- npx create-meith, pushed to your GitHub
- A server
- Rented in the community's name, from a few euro a month
- An evening
- Once — an upgrade is a version bump