Data sources
We source plugin data from four official marketplaces. Each platform has a different structure, but all share a common set of fields we extract.
- appsource.microsoft.com — Microsoft 365 plugins (8131 listings)
- appexchange.salesforce.com — Salesforce plugins (5889 listings)
- marketplace.atlassian.com — Atlassian plugins (7068 listings)
- autodesk.com/store — Autodesk plugins (2847 listings)
Data collection and freshness
Listing data is collected from each marketplace when the catalog is refreshed; there is no fixed public refresh schedule. If a vendor updates pricing, deployment, or SSO information on their listing, the catalog will reflect the old state until the next refresh.
The Last verified field on each listing shows when we last confirmed the facts matched the marketplace page. Across the current catalog those dates run from August 2026 to October 2026.
Pricing state
We classify each plugin into one of four pricing states based solely on what appears on the marketplace listing or vendor pricing page.
- Free — The listing explicitly states "Free" with no paid tiers or upsells mentioned.
- Freemium — A free tier exists alongside paid plans.
- Paid — Only paid plans are available; no free tier.
- Unknown — No pricing information is published. The page shows "Contact us" or no pricing section at all.
We never label a plugin "Free" when the vendor publishes no pricing. This was a production bug that incorrectly marked 6,377 enterprise products as free. See How We Verify for the corrected process.
Deploy state
Deployment state reflects where the plugin runs, not how it is sold or marketed.
- Cloud — Hosted entirely by the vendor; no local infrastructure required.
- On-premises — Installed on the customer's own servers or network.
- Hybrid — Both cloud and on-premises options are available.
We extract this from the marketplace's "Deployment" field or the vendor's technical documentation. If the field is missing, we mark it as unpublished (—).
Summary short
The one-line summary on each card is a single sentence extracted verbatim from the marketplace listing's description or tagline. It does not include feature lists, marketing language, or anything beyond the first declarative sentence.
What is included: the first sentence describing what the plugin does.
What is excluded: bullet points, feature lists, testimonials, calls to action, vendor slogans.
Removed and renamed listings
When a plugin is removed from a marketplace, we mark it as removed: true and stop showing it in the catalog. The slug is preserved so any external links return a 404 rather than silently redirecting to a different plugin.
If a vendor renames a plugin but keeps the same marketplace ID, we update the name. If the marketplace ID changes, we treat it as a removal and a new listing.
Known limits
This methodology has three known limits. We document them here so you know where gaps exist.
Marketplace lag
The marketplace page may lag behind the vendor's actual offering. If a vendor updates pricing on their own site but not on AppSource or AppExchange, we will reflect the marketplace version until the next refresh picks up the change.
Pricing outside the listing
If a vendor publishes pricing on a separate page not linked from the marketplace listing, we do not see it. Collection follows only the canonical marketplace URL and the vendor links embedded in that page's metadata.
Certifications from the listing only
Security certifications (SOC 2, ISO 27001, GDPR compliance) are recorded only when explicitly listed in the vendor's marketplace profile or linked documentation. We do not cross-check external certification directories.
For corrections or questions about this process, see Report a Wrong Fact.
Related pages
This page describes how we extract data. For the rest of how the catalog operates:
- How We Verify — the three guarantees we make, which fields we record and with what coverage, and what an em dash means.
- Editorial Policy — who writes the descriptive text, why we add no ratings of our own, and how we handle affiliate links.
- About — what the catalog is and who runs it.