Plausible · Strategy · Mid · 45 to 60 minutes

Should Plausible change its self-hosted model?

Plausible is a privacy focused web analytics company that sells a hosted service and also offers self-hosted software. Answer this product management case and get it graded line by line against a weighted rubric.

Strategic thinking
Trade-off analysis
Business model judgment
User empathy
Stakeholder communication

The situation

The founders ask you to recommend a strategy for Plausible's self-hosted release. Plausible sells a hosted analytics service, but some users run the software themselves. The company already moved from MIT to AGPL to make it harder for others to take the code private, yet the team now believes the current setup may still leave room for third parties to repackage or resell Plausible in ways that do not support the company. That matters because Plausible is funded by subscribers and does not rely on investors, so mistakes that weaken the hosted business could affect the small team directly. At the same time, the company wants to stay true to its open source values and avoid surprising existing self-hosters or creating confusion for cloud customers. You need to advise whether Plausible should keep the current self-hosted approach or change it, and how to explain the trade-offs clearly. The hard part is balancing openness, user trust, legal clarity, and the need to protect the business model that funds ongoing development.

What to produce

A 1 to 2 page strategy memo.

Your answer must

State a clear recommendation for Plausible's self-hosted licensing or distribution strategy, plus at least two realistic alternatives.
Define the goals of any change in plain language, including which behaviors Plausible is trying to discourage and why they matter to the business.
Separate the impact on self-hosters from the impact on cloud customers, including what would stay the same and what would change.
Evaluate the main trade-offs across openness, user trust, clarity or enforceability, and business sustainability.
Include a short rollout and communication plan for users, and name 2 to 4 signals you would watch after launch.

Constraints

Base your answer only on the summary provided, do not assume facts not in evidence.
Keep the scope on self-hosted licensing or distribution strategy, not changes to the analytics product itself.
Treat legal review as a follow-up step, not the core of your recommendation.
Your plan must preserve trust with existing users and avoid unnecessary disruption for cloud customers.

Format

Use headings for goals, options, recommendation, impacts, and rollout.

How Plausible actually played it

Plausible explains why it changed its self-hosted release into a Community Edition after finding that its AGPL license did not fully protect the business. The post recaps the earlier move from MIT to AGPL, what goals the license serves, and how the funded team is set up (no investors, funded by subscribers). A real example of balancing open source with a hosted business model.

State the goals of a licensing change in plain terms (for example, stop closed copies and unpaid resale).
Separate what changes for self-hosters from what stays the same for cloud customers.
Revisit earlier protections when threats change.
Tie the open source decision back to what sustains the team.

Built from Introducing Plausible Community Edition by Marko Saric, Plausible.