Ethical and transparent thread about Public API / SSO features

I am the owner of Postiz, an open-source social media scheduling tool (not a half-baked software but a fully featured one that, compared to all the big players)

I want to build Postiz to bring people as much value as possible.

So far: 6.44k downloads for the docker 🤯

Pretty insane.

Postiz is a self-funded social media scheduling tool and my main job (currently generating $388 per month from the hosted cloud.)

Of course, this is not enough money to run a sustainable business that allows me to maintain and work on it 24/7.

I have invested more than $10k until today (for the dashboard design and main website design)

I was approached by some companies for support and social features like the Public API and SSO.

That's a good place for monetization and a feature many self-hosters want.

So many people asked it in open discussions.

And now I am kind of conflicted and not sure where to take this.

I don't mind self-hosters having it for free for ever, but I do want commercial companies to pay for it.

Those are the options I thought about:

• Give it to everybody, and suffer the cost until I can't maintain the project anymore.
• Have a double license and add it to the main repository.
• Create a "Plugins" style option that only paid Enterprises can clone.
• Do a partial API for the community and partial for enterprise (but not sure how really to do it as there is one main endpoint everybody needs)

As I want Postiz to be always loved by the community and never get backlashed.

So, the best feedback I can get is from the community.

Let me know what you think!