Wulfheart

This would be really beneficial for my use case to be honest: Building a hobby community.

It is a Laravel application. So you can write code that does this for you and can let it be called by webhooks or whatever Stripe uses. You might also want to use Laravel Cashier.

Another idea I had would be dual licensing. Let's say I would like to help develop e.g. a tighter integration for the auth system (like stated here . I have no incentive to work on this as it wouldn't benefit my project (because I would have to pay some $$$).
However you could opt to release this under a dual license. Let's say one license requires everything to be open source (I mean everything, even all other packages for example) and if you would like to have a tighter integration or have some proprietary packages (which I think has been be quite important for the companies I worked for) then you got to pay.
What do you think about it?

Limit the number of user accounts: You could restrict the number of user accounts that can be created on the free tier. This limitation can help ensure that the free tier is suitable for smaller communities or personal projects while encouraging larger communities to upgrade to a paid plan.

Tbh I am not a huge fan of user accounts limit as I have some users but most of them are not active.

Limit forum activity: You could set limits on the frequency or volume of forum activity for the free tier. For example, you could restrict the number of posts, comments, or topics that can be created within a certain time frame. This limitation would allow smaller communities or hobbyists to engage in discussions while still encouraging more active or professional communities to consider a paid plan.

This is the idea I like the most. But it would depend on the limits itself if it is viable.

Nerf the groups functionality: If your forum software offers advanced features like user groups or permissions, you could limit the functionality of these features on the free tier. For instance, you could restrict the number of user groups that can be created or limit the permissions available to free tier users. This limitation would ensure that more complex or enterprise-level community setups require a paid plan.

Also quite a nice idea but then I think it would still scare users away.

Restrict access to advanced features: Consider offering a stripped-down version of the software for free, with access to only the essential features. This can help differentiate between hobbyist communities and more serious ones that require advanced functionality such as custom themes, advanced moderation tools, or integrations with external services. The free tier can act as a gateway, enticing users to upgrade to a paid plan for access to these premium features.

What are advanced features in your opinion?

Limited customization options: Restrict the level of customization available on the free tier. For example, you could provide a set of pre-defined themes or templates, limiting the ability to customize the forum's appearance, colors, or branding. Advanced customization options could be reserved for paid plans, appealing to businesses or communities that require a unique and branded forum experience.

Phew, that would make me unhappy. :D I like the design but I think there are some things I would like to change.

Reduced support options: Differentiate the support provided based on the tier. For the free tier, you could limit the support to community forums or documentation, while offering more personalized support options like email or live chat exclusively for paid plans. This would ensure that users who require dedicated support or faster response times are encouraged to upgrade.

I think this is good but I don't think people getting the free version should expect personal support.

Another ideas I had:

• Sell hosting for communities. I don't know if Flarum offered this and how it went. @Toby might have more insight on this.
• I recently saw a project (can't remember which) which offered custom feature development which could also be contributed back to the original project.

Note that these last two ideas might not be what you envisioned. :D