|
| 1 | +--- |
| 2 | +title: "State of AsyncAPI Initiative: 2025 Annual Review" |
| 3 | +date: 2026-01-10T06:00:00+01:00 |
| 4 | +type: Communication |
| 5 | +tags: |
| 6 | + - Project Status |
| 7 | +cover: /img/posts/2025-blog-banner/banner-annual.webp |
| 8 | +authors: |
| 9 | + - name: Thulisile Sibanda |
| 10 | + photo: /img/avatars/thulieblack.webp |
| 11 | + link: https://www.linkedin.com/in/v-thulisile-sibanda/ |
| 12 | + byline: Community Builder and Open Source Fanatic! |
| 13 | +excerpt: 'AsyncAPI Annual Review for 2025 in Numbers' |
| 14 | +featured: true |
| 15 | +--- |
| 16 | + |
| 17 | +Happy 2026 to the AsyncAPI community! |
| 18 | + |
| 19 | +Starting the new year by looking back at our community’s growth. Let’s review the numbers to see our progress, where we can do better, and how we can improve. These metrics help us understand our impact and guide us in the direction to take when working towards the community goals. |
| 20 | + |
| 21 | +For the past achievements, [please read the previous Project Status updates](https://www.asyncapi.com/blog?tags=Project+Status). |
| 22 | + |
| 23 | +> As a disclaimer, all analytics you’ll read here are collected from the 1st of January 2025 to the 30th of December 2025. |
| 24 | +
|
| 25 | +## Slack |
| 26 | + |
| 27 | +The AsyncAPI Slack workspace is our primary channel for most communications and updates, where contributors and adopters join to collaborate with others, understand how we work as a community, and chat with maintainers of the specifications and tooling. |
| 28 | + |
| 29 | +In 2025, we welcomed **1857** new joiners and have a total of **7964** members. |
| 30 | + |
| 31 | +<Figure |
| 32 | + src="/img/posts/2025-blog-banner/Joiners vs. Year.webp" |
| 33 | + caption="New members on Slack each year." |
| 34 | + className="text-center" |
| 35 | +/> |
| 36 | + |
| 37 | +Our weekly activity reduced by 19% this year, with the intention of reducing noise in channels by disabling some workflow notifications and pausing certain channels. Also, we ran one mentorship program instead of multiple as we did in previous years, and had fewer active working groups. |
| 38 | + |
| 39 | +<Figure |
| 40 | + src="/img/posts/2025-blog-banner/Average and Median.webp" |
| 41 | + caption="Weekly Slack activity over the years." |
| 42 | + className="text-center" |
| 43 | +/> |
| 44 | + |
| 45 | +## Social Media |
| 46 | +Our social media platforms help us to share community news, updates, and announcements. We don’t use any premium or paid marketing, and we only maintain LinkedIn, X/Twitter, Mastodon, and YouTube platforms. We use Buffer to publish and manage content across social media. |
| 47 | + |
| 48 | +### Buffer |
| 49 | +We began using Buffer in July 2024 and switched to paid services in September. This gave us more tools to track and report on our social media management. The analytics below cover LinkedIn and X/Twitter, which Buffer currently supports. |
| 50 | + |
| 51 | +We also have some analytics recorded dating back to 2023. |
| 52 | + |
| 53 | +<Figure |
| 54 | + src="/img/posts/2025-blog-banner/Audience and Engagement.webp" |
| 55 | + caption="Audience and Engagement analytics from Buffer." |
| 56 | + className="text-center" |
| 57 | +/> |
| 58 | + |
| 59 | +### LinkedIn |
| 60 | + |
| 61 | +We gained **945** followers on LinkedIn in 2025, bringing our overall following to **4928**. |
| 62 | + |
| 63 | +<Figure |
| 64 | + src="/img/posts/2025-blog-banner/Followers vs. Year.webp" |
| 65 | + caption="Yearly followers on LinkedIn." |
| 66 | + className="text-center" |
| 67 | +/> |
| 68 | + |
| 69 | +### YouTube |
| 70 | +We had **272** new subscribers to our YouTube channel this year, bringing our total subscribers to **1,983**. While our views and watch time dropped by 29% compared to last year, the community continues to grow and engage. |
| 71 | + |
| 72 | +<Figure |
| 73 | + src="/img/posts/2025-blog-banner/YouTube stats.webp" |
| 74 | + caption="YouTube stats over the last few years." |
| 75 | + className="text-center" |
| 76 | +/> |
| 77 | + |
| 78 | +### Newsletter |
| 79 | +The community summary newsletter continues to grow and still serves the community as a summary of our monthly blogs, events, and important updates. We sent 10 emails this year, and our average open rate was 41%, while clicks averaged 4.7%. Bringing the overall engagement rate to 22.7%. |
| 80 | + |
| 81 | +<Figure |
| 82 | + src="/img/posts/2025-blog-banner/open vs clicks.webp" |
| 83 | + caption="Newsletter Analytics." |
| 84 | + className="text-center" |
| 85 | +/> |
| 86 | + |
| 87 | +The number of new users referred to the AsyncAPI through our monthly newsletter increased, though session time dropped slightly. |
| 88 | + |
| 89 | +<Figure |
| 90 | + src="/img/posts/2025-blog-banner/referred-Newsletter.webp" |
| 91 | + caption="Website visits referred by the Newsletter." |
| 92 | + className="text-center" |
| 93 | +/> |
| 94 | + |
| 95 | +## Google Analytics |
| 96 | +The overall site performance declined this year, with users by 4.4%, sessions by 9.1%, and pageviews by 15.8%. Docs continue to be a great contributor to the performance in sessions. |
| 97 | + |
| 98 | +<Figure |
| 99 | + src="/img/posts/2025-blog-banner/Visits.webp" |
| 100 | + caption="Website visits each year." |
| 101 | + className="text-center" |
| 102 | +/> |
| 103 | + |
| 104 | +The contributing factor leading to the drop in analytics is due to several factors, including users blocking tracking, privacy tools, and browser extensions. This trend affects the traffic recorded, and user behaviour data does not fully reflect the actual audience, as they’re excluded from the analytics reports. |
| 105 | + |
| 106 | +## Google Search Console |
| 107 | + |
| 108 | +We saw a 6.9% increase in impressions in Google Search Console, although we had a decrease in clicks. |
| 109 | + |
| 110 | +<Figure |
| 111 | + src="/img/posts/2025-blog-banner/Search Console.webp" |
| 112 | + caption="Website analytics from Search Console." |
| 113 | + className="text-center" |
| 114 | +/> |
| 115 | + |
| 116 | +## GitHub |
| 117 | +We use LF Insights to get detailed analytics for all our repos across the org on GitHub. The community keeps growing, with **1,131** active contributors. |
| 118 | + |
| 119 | +<Figure |
| 120 | + src="/img/posts/2025-blog-banner/Active contributors.webp" |
| 121 | + caption="Active contributors on GitHub." |
| 122 | + className="text-center" |
| 123 | +/> |
| 124 | + |
| 125 | +We also improved issue resolution across the project, with the average issue now taking just one month to close, a clear sign of our maintainers' responsiveness. |
| 126 | + |
| 127 | +<Figure |
| 128 | + src="/img/posts/2025-blog-banner/Issues resolution.webp" |
| 129 | + caption="Issue resolution stats." |
| 130 | + className="text-center" |
| 131 | +/> |
| 132 | + |
| 133 | +In the past year, a total of **2,770** pull requests were opened, and **2,390** were merged, highlighting the pace of development and community contributions. |
| 134 | + |
| 135 | +<Figure |
| 136 | + src="/img/posts/2025-blog-banner/Pull requests.webp" |
| 137 | + caption="Pull requests resolution stats." |
| 138 | + className="text-center" |
| 139 | +/> |
| 140 | + |
| 141 | +The AsyncAPI community is driven by contributors and maintainers who dedicate their time and expertise outside their regular jobs. Kudos to everyone for your commitment and impact! |
| 142 | + |
| 143 | +<Figure |
| 144 | + src="/img/posts/2025-blog-banner/outside work hours.webp" |
| 145 | + caption="Stats showing contributions made outside work hours." |
| 146 | + className="text-center" |
| 147 | +/> |
| 148 | + |
| 149 | + |
| 150 | +## NPM |
| 151 | +AsyncAPI's top packages are hosted under the Node Package Manager. The package downloads continue to increase, and the `asyncapi/spec` saw **54M** downloads in the past year. |
| 152 | + |
| 153 | +<Figure |
| 154 | + src="/img/posts/2025-blog-banner/NPM.webp" |
| 155 | + caption="Total downloads of AsyncAPI NPM packages." |
| 156 | + className="text-center" |
| 157 | +/> |
| 158 | + |
| 159 | + |
| 160 | +## Community Achievements |
| 161 | + |
| 162 | +We had so many achievements this year, and here are a few highlights: |
| 163 | + |
| 164 | + |
| 165 | +- We transitioned and nominated our first [Governance Board](https://www.asyncapi.com/community/board). |
| 166 | +- We published our [second case study](https://www.asyncapi.com/casestudies/transfergo) by TransferGo. |
| 167 | +- The AsyncAPI Bounty Program turned 2 with over [36 issues resolved](https://github.com/orgs/asyncapi/projects/36/views/4?filterQuery=-no%3Alevel+status%3ACompleted). |
| 168 | +- We had six in-person conferences, an online conference, and over 30 speakers. |
| 169 | +- Welcomed [two ambassadors](https://www.asyncapi.com/community/ambassadors) and introduced monthly meetings. |
| 170 | +- Expanded our [community docs](https://www.asyncapi.com/docs/community) and content. |
| 171 | +- Surpassed [5,000 stars on the Spec repo](https://github.com/asyncapi/spec/stargazers) in GitHub. |
| 172 | + |
| 173 | + |
| 174 | +These are just a few, but we have so much planned for 2026. Be sure [to read the community goals](https://www.asyncapi.com/docs/community/030-project-vision-strategy-goals/2026_Community_Goals) to gain insight into what we will be focusing on. |
| 175 | + |
| 176 | + |
| 177 | +> Image Generated by Nano Banana |
0 commit comments