How is the 60-extension database curated?

Every entry in the database is something I’ve installed, configured, and shipped on a real client store between 2019 and 2026 — no “found-it-on-the-marketplace” entries, no AI-generated brochure summaries.

The shortlist for each of the 12 categories is filtered through five gates:

1. Live install — ran on a paying-client production store for at least 90 days. If I’ve only POC’d it on staging, it doesn’t make the list.
2. Active maintenance — vendor shipped a release in the past 12 months. Silent vendors get cut even if the module is technically excellent.
3. Pricing transparency — vendor publishes a public price (not “contact us for a quote”). Enterprise-only modules get tagged but de-prioritized.
4. Hyvä compatibility known — I’ve either tested it on a Hyvä storefront or read the vendor’s explicit compat statement.
5. No undisclosed conflicts — doesn’t silently break checkout, search, or admin when stacked with the other 3-4 modules in its category.

That filters ~150 candidates I’ve touched down to the 60 entries you see. Re-curated quarterly — if a vendor goes silent, they’re marked deprecated and rotated out at the next refresh.