Plausible Community Edition
Plausible Analytics is introducing a Community Edition of its privacy-focused, self-hosted web analytics tool, keeping the core under the AGPL while moving some advanced features to a separate, more restrictive license. Commenters debate whether this open-core shift fairly protects Plausible’s business from resellers and large integrators or undermines its open-source credibility, noting tensions around CLAs, feature gaps for self-hosters, and the broader challenge of building a sustainable business on FOSS. The thread also contrasts Plausible with Google Analytics in terms of privacy, legal compliance in the EU, and practical usefulness for small sites.
Reactions to Plausible Community Edition & Feature Gating
- Some see CE as a reasonable “open core” split: enough for small sites/startups, with advanced features reserved for paying/hosted tiers.
- Others view it as holding features “hostage” and moving the goalposts on what “open source” meant for this project, prompting talk of looking for alternatives.
- Concern that CE effectively becomes a self-hosted “free basic plan” whose feature gap vs the hosted service will grow, creating pressure to upgrade.
- Others welcome CE because earlier self-hosting felt like a time‑limited trial; they see this as clarifying what’s sustainably free.
Open Source, Licensing, and Business Sustainability
- Strong debate over whether you can both use FOSS licensing to grow and then constrain commercial use by resellers/hyperscalers.
- Some argue: if it’s truly FOSS, you must accept commercialization by others; otherwise don’t use FOSS branding.
- Others counter: projects need protection from larger companies and resellers who repackage the software, undercut pricing, and damage the brand while not contributing back.
- Discussion on AGPL vs BSL/SSPL; AGPL seen by some as a “magic middle ground” that’s still FOSS but unattractive to big enterprises and cloud providers.
AGPL and Legal/Practical Questions
- Common question: does using Plausible CE force a web app to open its own source?
- Consensus in the thread: no, if Plausible runs as a separate service (e.g., Docker) and you don’t modify it.
- If you modify and redistribute Plausible itself, you must provide source for those modifications.
- Some note that AGPL’s “infectiousness” over network use has never been tested in court, leaving lingering uncertainty.
- Introduction of a Contributor License Agreement raises concern that the project could later relicense contributions under non‑FOSS terms.
Views on “Privacy-Focused” Analytics
- Skeptics see “privacy analytics” as an oxymoron and argue many sites would be fine with no analytics at all.
- Supporters distinguish between:
- First‑party, self‑hosted, cookie‑less, non‑PII, aggregate metrics (like page views and dwell time), versus
- Cross‑site tracking and data hoarding by large ad platforms.
- EU/GDPR compliance and distrust of US‑based analytics vendors are cited as reasons to use tools like Plausible.
Broader OSS Business-Model Debate
- Thread widens into whether viable, fair business models for FOSS exist at all, with suggestions including consulting, support, hosting, nonprofits, and corporate sponsorship.
- Tension highlighted between idealistic definitions of open source and the economic reality of small teams trying to survive.