Final audit • March 8, 2026 • Event infrastructure

Final Ranking of FOSS Event Infrastructure Through a Bitcoin, Privacy, and Sovereign-Stack Lens

This page consolidates the full scoring model, the weighted ranking, the tier map, and the detailed rationale for ten event and organizing tools: Gancio, Mobilizon, Gathio, Flockstr, Meetstr, Plektos, Agorakit, pretix, LAUTI, and Openki.

The emphasis is not generic convenience. The emphasis is self-hosting, free software integrity, surveillance resistance, anti-lock-in design, decentralization, Bitcoin compatibility, and long-run resistance to platform capture. The result is not a popularity list. It is a structural audit of stack suitability.

10 projects
8 weighted criteria
Official docs and repos linked inline
Fediverse + Nostr + ticketing + groupware compared directly

Executive Overview

The final ordering places Gancio, Mobilizon, and Gathio at the top because they combine real self-hostability, strong free software posture, meaningful interoperability, and better default privacy semantics than most of the field. The next cluster — Flockstr, Meetstr, and Plektos — forms the Nostr-native event layer. These tools are structurally interesting, especially where NIP-52 calendar events and Lightning-native flows matter, but they remain more dependent on relay practices, key hygiene, and ecosystem maturity. Agorakit and pretix occupy the organization and commerce layers rather than the lean event-kernel layer. LAUTI and Openki remain useful but narrower or weaker under a hard-maximalist FOSS/privacy/Bitcoin filter.

ActivityPub reference: W3C Nostr calendar spec: NIP-52 BTCPay ticketing reference: pretix + BTCPay Openki note: ranked as Openki; the earlier “Openkic” label is treated as a typo

Scoring Methodology

Every tool was scored from 0–100 on eight criteria and then combined using fixed weights. The framework was repeatedly revised to reduce double-counting, account for governance and maturity, and correct overly generous treatment of “Nostr by default” or “source-available but non-commercial” projects.

SSA — Sovereign Stack Alignment

16%
Self-hosting, infra independence, small-node friendliness, and freedom from mandatory corporate cloud dependencies.

FLC — FOSS License & Code Openness

12%
License clarity, freedom level, public code availability, and absence of closed or proprietary core behavior.

PSD — Privacy & Data Lifecycle

18%
Required PII, retention defaults, graph visibility, tracking, and how much user data the software structurally demands.

BNA — Bitcoin / Lightning Alignment

16%
Native Bitcoin or Lightning support, BTCPay compatibility, and explicit fit with a hard-money event economy.

DFI — Decentralization, Federation & Interop

10%
ActivityPub or Nostr, plus RSS, ICS, WebCal, APIs, and the ability to bridge out of a single silo.

GCR — Governance & Capture Risk

12%
Bus factor, stewardship structure, maintenance continuity, institutional or corporate capture risk, and project direction.

SPR — Security, Robustness & Complexity

10%
Operational maturity, release activity, real-world usage, and blast radius created by monolithic complexity or plugin sprawl.

PUX — Practical UX & Adoption

6%
Time-to-value for non-expert organizers, admin ergonomics, deployment paths, and general operational smoothness.
Important correction baked into the final model: Nostr alone does not automatically grant a near-maximal Bitcoin score. Native Lightning or Bitcoin payment flows matter more than mere adjacency. Likewise, Openki was penalized because its TNU ATPG license is non-commercial and therefore not equivalent to standard OSI-style FLOSS under a hard maximalist filter.

Final Ranking

Differences smaller than roughly one point should be treated as close. The larger pattern matters more than the decimal precision: the field breaks into a Fediverse-first event core, a Nostr-native event layer, a groupware/ticketing layer, and a narrower final tier.

#1

Gancio

87.8
Best overall local sovereign event kernel
#2

Mobilizon

86.3
Most mature full-stack federated hub
#3

Gathio

85.8
Strongest ephemeral and no-account profile
#4

Flockstr

81.7
Top Nostr + Lightning event client
#5

Meetstr

79.9
Nostr calendar browser/manager
#6

Plektos

78.5
Promising but early Nostr calendar stack
#7

Agorakit

76.9
Strong local groupware, weaker federation
#8

pretix

76.8
Serious ticketing with Bitcoin payment paths
#9

LAUTI

73.5
Classic community calendar with feed/API bridges
#10

Openki

70.3
Useful learning layer, weaker as a general event kernel

Full Weighted Matrix

Tool Composite SSA FLC PSD BNA DFI GCR SPR PUX
Gancio87.89595936595908785
Mobilizon86.39095886095968888
Gathio85.89095986590858080
Flockstr81.78595809585706070
Meetstr79.98295808085726575
Plektos78.58495808585605870
Agorakit76.99095825550857580
pretix76.88590688045758885
LAUTI73.58588755565757075
Openki70.38070755560807070

Tier Structure and Architectural Roles

Tier 1 — Sovereign Event Kernels

Gancio, Mobilizon, and Gathio are the strongest core candidates for a federated event layer. They are all self-hostable and free software, but they differ in shape. Gancio is the clearest expression of a local, small-node, anti-platform agenda. Mobilizon is the most mature community-and-events platform, with rich ActivityPub support and official RSS/ICS/WebCal export. Gathio is the leanest of the three, maximizing ephemeral no-account event hosting with configurable deletion semantics.

Tier 2 — Nostr Event Layer

Flockstr, Meetstr, and Plektos form the Nostr-native event cluster. They gain from protocol-level decentralization and NIP-52 calendar events, but their real privacy depends heavily on relay choice, key reuse discipline, and the broader Nostr operational environment. Flockstr leads this group because it has the clearest Lightning-native event and ticketing direction, documented by OpenSats and noted by Lightning Labs.

Tier 3 — Groupware and Ticketing

Agorakit and pretix are not weak tools. They simply occupy different layers. Agorakit is local group infrastructure — discussions, files, calendar, email notifications — and therefore carries more metadata surfaces than the lean event kernels. pretix is a serious ticketing engine, with documented BTCPay integration, but it also structurally invites more PII and more operational complexity than a minimal rendezvous layer.

Tier 4 — Narrower Calendar and Learning Layers

LAUTI and Openki remain relevant, but for narrower roles. LAUTI is a community calendar with RSS, ICAL, REST API, and WordPress bridge support, while Openki is fundamentally a peer-to-peer learning platform. Openki ranks last not because it is useless, but because its non-commercial TNU ATPG licensing and education-centric role weaken its standing as a sovereign event kernel.

Detailed Project Analysis

Each section below includes: a role statement, score profile, reasons for strength, reasons for restraint, and live links to the project’s site, repository, and the most relevant documentation or ecosystem references.

1. Gancio

Tier 1 Composite 87.8
Best overall local sovereign event kernel
SSA
95
FLC
95
PSD
93
BNA
65
DFI
95
GCR
90
SPR
87
PUX
85

Gancio describes itself as “a shared agenda for local communities.” That framing matters. This is not social media disguised as events. It is a community calendar built around events themselves, not personal timelines. The official site explicitly explains that anonymous event submission is enabled by default and that the absence of user-centric views is intentional. The project also documents broad ActivityPub interoperability, while third-party deployment material and project notes confirm export paths through RSS, ICS, widgets, and other open formats.

Why it scores so high

  • Local-node architecture: structurally aligned with many small, community-run instances rather than one central platform.
  • Minimal social graph: no identity-first design, no personal feed emphasis, and a strong event-first posture.
  • Interoperability: ActivityPub plus RSS and ICS make it easy to bridge into personal calendars, other websites, and Fediverse workflows.
  • Capture resistance: rooted in hacklab culture rather than venture-backed growth incentives.
  • Operational scope: narrower than Mobilizon and pretix, which reduces blast radius and keeps the tool focused.

What holds it back from a perfect score

  • Bitcoin neutrality rather than Bitcoin-native design: no first-class Lightning or BTCPay layer built into the core product.
  • Smaller governance footprint than Mobilizon: active, but not backed by an equally large and visible stewardship apparatus.
  • Still requires competent instance operation: privacy posture improves when deployers minimize logs, harden infrastructure, and avoid external map or mail dependencies.
Primary role: public or semi-public local event kernel for communities that want federation, open formats, and much weaker identity exposure than mainstream platforms.

2. Mobilizon

Tier 1 Composite 86.3
Most mature full-stack federated hub
SSA
90
FLC
95
PSD
88
BNA
60
DFI
95
GCR
96
SPR
88
PUX
88

Mobilizon is the strongest “full platform” in the field. The official documentation presents it as a federated organization and mobilization platform designed to help groups leave Facebook events, Meetup, and similar systems. The software supports multiple profiles from one account, explicitly so that different identities can be compartmentalized. The project also documents ActivityPub federation and RSS/ICS/WebCal export flows, making it substantially more interoperable than a closed event silo.

Why it stays at the top

  • Stewardship and continuity: originated with Framasoft, now stewarded by Kaihuri, with public-interest infrastructure and documentation that give it the strongest governance profile in the set.
  • Feature completeness: groups, events, roles, privacy settings, federation, APIs, and export paths all exist in one coherent system.
  • Identity compartmentalization: multiple profiles materially improve privacy relative to one-flat-identity systems.
  • Interoperability depth: Fediverse support plus RSS and ICS make it unusually bridgeable.

Why it does not take first place

  • Richer social graph than Gancio or Gathio: group pages, accounts, and profiles naturally generate more metadata.
  • Higher complexity: broader surface area means more admin effort, more moving parts, and more ways to drift toward a “big instance” model.
  • Bitcoin-native support remains external: it is compatible with Bitcoin-centered communities, but Bitcoin is not a first-class architectural component.
Primary role: the strongest general-purpose federated events-and-groups platform when maturity, governance, and breadth matter more than extreme minimalism.

3. Gathio

Tier 1 Composite 85.8
Strongest ephemeral and no-account profile
SSA
90
FLC
95
PSD
98
BNA
65
DFI
90
GCR
85
SPR
80
PUX
80

Gathio is the sharpest privacy-first design in the list. The official site states plainly that there are no accounts on the flagship instance; creating an event generates an editing password, and providing an email is optional. The flagship instance also states that events are automatically deleted seven days after they end. Meanwhile, the configuration docs show that the deletion window is an instance-level setting (delete_after_days) and that event creation can be open or restricted. The federation docs confirm that RSVP, comments, and updates can flow through ActivityPub-compatible services.

Why it ranks this high

  • Minimal account surface: a radically smaller identity layer than conventional event platforms.
  • Deletion semantics: the flagship’s automatic deletion policy materially reduces long-term retention.
  • Federated access: event interaction through Fediverse accounts lowers friction for attendees.
  • Simple deployment paths: documented self-hosting and Docker support keep the infrastructure approachable.

What keeps it below Gancio and Mobilizon

  • Smaller governance and maintenance footprint: less institutional continuity than Mobilizon and a narrower ecosystem than Gancio.
  • Privacy depends partly on instance policy: deletion can be disabled, public lists can be enabled, and admin choices still matter.
  • Less suited to larger structured communities: strong for hidden or low-friction event pages, weaker as a comprehensive community operating layer.
Primary role: ephemeral, privacy-first event hosting where no-account access and deletion defaults matter more than complex group features.

4. Flockstr

Tier 2 Composite 81.7
Top Nostr + Lightning event client
SSA
85
FLC
95
PSD
80
BNA
95
DFI
85
GCR
70
SPR
60
PUX
70

Flockstr leads the Nostr layer because it is not only adjacent to Bitcoin — it is explicitly moving events, RSVPs, tickets, and payments into the Nostr/Lightning stack. The project site says “Own your Events. Only on Nostr.” The OpenSats grant announcement describes Flockstr as a calendar events app on Nostr where users can create events, post updates, invite users, issue tickets, and collect payments. Lightning Labs also highlighted it specifically as a Nostr alternative to Meetup or Facebook Events with Lightning zaps integration for rewards and ticketing.

Why it ranks highest among Nostr tools

  • Real Bitcoin alignment: explicit Lightning flows matter more than vague ecosystem proximity.
  • Nostr-native ownership model: event data can live on relays instead of a central application database.
  • Open source and forkable: the public MIT-licensed repository keeps experimentation and local adaptation open.

Why it does not rank with the top Fediverse core

  • Relay and key correlation risk: weak relay hygiene or broad key reuse can create a rich public metadata graph.
  • Early-stage maturity: smaller deployment base, less battle-tested operational behavior, and lower governance depth than Mobilizon or Gancio.
  • MIT capture vector: maximal forkability comes with easier proprietary appropriation than strong network copyleft.
Primary role: Bitcoin-native event and ticketing client within a Nostr-centered social and payments stack.

5. Meetstr

Tier 2 Composite 79.9
Nostr calendar browser and manager
SSA
82
FLC
95
PSD
80
BNA
80
DFI
85
GCR
72
SPR
65
PUX
75

Meetstr presents itself as an open-source web Nostr client for discovering, viewing, and managing NIP-52 calendars. That description is important because Meetstr is best understood as a calendar layer inside Nostr, not as a full alternative to pretix or Mobilizon. Its AGPL licensing gives it a stronger anti-capture posture than MIT-licensed Nostr peers, and its role as an event browser/manager makes it a useful stack component even when it is not the main publishing engine.

Why it stays in the upper-middle tier

  • Strong free software posture: AGPL rather than permissive licensing.
  • Useful stack role: strong for browsing, discovering, and managing event calendars across Nostr relays.
  • Nostr interoperability: inherits protocol-level decentralization through NIP-52.

What limits it

  • Less explicit Bitcoin commerce support than Flockstr: no equally clear Lightning-first ticketing story.
  • Still inherits Nostr metadata hazards: relay centralization and key reuse remain real concerns.
  • Tool role is narrower: more browser/manager than all-purpose event infrastructure.
Primary role: Nostr event discovery and calendar management layer, especially useful alongside other Nostr publishing or payments tools.

6. Plektos

Tier 2 Composite 78.5
Promising but still early Nostr calendar stack
SSA
84
FLC
95
PSD
80
BNA
85
DFI
85
GCR
60
SPR
58
PUX
70

Plektos is a decentralized meetup, events, and calendar platform built on Nostr. The repository notes a MIT license and identifies the project squarely as a Nostr-native event layer. Unlike Meetstr, which reads more like a calendar manager, Plektos is positioned closer to a decentralized meetup product. The ranking remains restrained because public evidence still points to a relatively young and still-hardening project rather than a widely proven operational backbone.

Strengths

  • Nostr-native event model: good structural fit for decentralized calendars and event discovery.
  • Open development: public code, ongoing activity, clear project framing.
  • Good interop inside the Nostr sphere: aligns naturally with other NIP-52-aware tools.

Weaknesses

  • Early maturity: less evidence of broad adoption or hardened deployments than the top Fediverse tools.
  • No equally explicit Lightning ticketing layer: stronger than generic web apps on Bitcoin adjacency, weaker than Flockstr on direct payments.
  • Same Nostr metadata caveat: privacy depends heavily on disciplined relay and key practices.
Primary role: experimental decentralized meetup/calendar layer inside a Nostr-first social graph.

7. Agorakit

Tier 3 Composite 76.9
Strong local groupware, weaker federation
SSA
90
FLC
95
PSD
82
BNA
55
DFI
50
GCR
85
SPR
75
PUX
80

Agorakit is best treated as a local organizing suite rather than a pure events kernel. The project describes itself as open-source web-based groupware for collectives, with a forum, calendar, file manager, and email notifier. The support material also states that groups can export their data and move elsewhere, which strengthens its sovereignty profile. It ranks below the top event kernels because email notifications, files, and richer group management carry more metadata surface and because there is no deep Fediverse or Nostr federation layer comparable to Gancio, Mobilizon, or the Nostr-native stack.

Why it remains strong

  • Excellent self-hosting posture: a clear local-control model.
  • AGPL licensing: strong network copyleft and strong anti-capture semantics.
  • Real collective utility: not just events, but discussion and coordination infrastructure for groups that actually organize.

Why it sits below the event core

  • Email and file surfaces: metadata and retention risks are higher than in leaner systems.
  • Weak federation score: far less native interop than ActivityPub or Nostr stacks.
  • Bitcoin neutrality: can host Bitcoin-native groups, but Bitcoin is not architecturally central.
Primary role: self-hosted collective operations stack for groups that need more than event pages and are willing to accept heavier communication surfaces.

8. pretix

Tier 3 Composite 76.8
Serious ticketing with Bitcoin payment paths
SSA
85
FLC
90
PSD
68
BNA
80
DFI
45
GCR
75
SPR
88
PUX
85

pretix is not a generic meetup clone. It is a substantial ticketing system for conferences, festivals, exhibitions, workshops, and other structured events. The project’s official materials describe AGPL licensing with additional terms, while the licensing FAQ clarifies the dual-licensing model. Importantly for Bitcoin-centered deployments, BTCPay Server documentation covers pretix integration, and the pretix-bitpay plugin provides a direct path to Bitcoin payment acceptance.

Why it remains valuable

  • High robustness: among the most mature systems in this field, with broad production use and a substantial ecosystem.
  • Bitcoin payment path exists: serious self-hosted ticketing can be paired with BTCPay.
  • Very strong UX for formal events: scanning, orders, products, and operational tooling exceed what the lighter systems attempt.

Why its privacy score is clearly lower

  • PII is intrinsic to the domain: many pretix workflows want names, emails, attendee records, and order histories.
  • Complexity: plugins and broad functionality expand the operational and security surface.
  • Low federation score: this is not an ActivityPub or Nostr-native system.
Primary role: high-capability self-hosted ticketing and admissions engine, especially for events that deliberately accept structured ordering and PII.

9. LAUTI

Tier 4 Composite 73.5
Classic community calendar with feed/API bridges
SSA
85
FLC
88
PSD
75
BNA
55
DFI
65
GCR
75
SPR
70
PUX
75

LAUTI positions itself as an open-source community calendar and is already used in several public instances. The official site documents ICAL and RSS feeds, an open REST API, and a WordPress plugin, which is enough to give it a real interoperability score rather than treating it as a dead-end silo. But its shape is still that of a community calendar with registered entities and public listings, not a privacy-maximal ephemeral system.

Strengths

  • Solid calendar infrastructure: useful for city, regional, and thematic event directories.
  • Open feeds and API: better interop than closed “events website” software.
  • Independent and non-commercial positioning: structurally better than ad-supported commercial calendars.

Limits

  • Weaker privacy posture than Gathio or Gancio: more public-directory oriented and less anonymous by design.
  • No native ActivityPub or Nostr layer: bridges exist, but not protocol-native federation.
  • Smaller field presence: less visible operational evidence than Mobilizon, Gancio, or pretix.
Primary role: independent public community calendar with open feed and API bridges, suitable where directory-style visibility is part of the mission.

10. Openki

Tier 4 Composite 70.3
Useful learning layer, weaker as a general event kernel
SSA
80
FLC
70
PSD
75
BNA
55
DFI
60
GCR
80
SPR
70
PUX
70

Openki is fundamentally a peer-to-peer learning platform for non-commercial education opportunities. The project’s own materials emphasize local, self-organized knowledge exchange rather than generic event scheduling. The main ranking penalty comes from licensing: the project is described in external documentation as open source under the TNU ATPG license, freely available for non-commercial use. Under a strict FOSS maximalist filter, that is materially weaker than AGPL, GPL, or MIT because it constrains downstream commercial or entrepreneurial reuse.

Why it still matters

  • Strong educational use case: course organization, community learning, and self-organized knowledge exchange.
  • Self-hosted, community-oriented posture: closer to a commons model than to a venture product.
  • Fits a learning layer: valuable when the goal is peer-to-peer education rather than generic events.

Why it ranks last here

  • Licensing weakness: non-commercial terms reduce sovereignty for downstream forks and ventures.
  • Narrower domain: better for courses and learning groups than for the general event field.
  • Lower Bitcoin relevance: not structurally oriented toward Bitcoin payments, Lightning, or sovereign event commerce.
Primary role: peer-to-peer educational infrastructure, not a first-choice general event kernel under a hard free-software and Bitcoin-maximalist lens.

Critical Notes and Final Judgments

What changed during the adversarial audit

  • Nostr scores were corrected downward where Bitcoin support was only indirect. Flockstr stayed high because the evidence for Lightning-integrated ticketing is explicit; Meetstr and Plektos were restrained because Nostr adjacency is not identical to built-in Bitcoin rails.
  • Openki’s score was corrected sharply on licensing. The non-commercial TNU ATPG note prevented it from being treated as equivalent to AGPL or MIT.
  • LAUTI gained credit for real interoperability. Its RSS, ICAL, REST API, and WordPress bridge justify a mid-level interop score rather than a silo score.
  • Governance and maturity were weighted more heavily. That helped Mobilizon and modestly restrained the early Nostr tools.

Final architectural reading

  • Best pure event kernel: Gancio
  • Best full federated platform: Mobilizon
  • Best ephemeral and low-account event host: Gathio
  • Best Nostr + Lightning event client: Flockstr
  • Best self-hosted collective groupware: Agorakit
  • Best serious ticketing engine: pretix
  • Best directory-style community calendar: LAUTI
  • Best learning-layer platform: Openki