
Plug.Dev
10 posts




This month, Plug.Dev turns two 🎉 What started as a simple idea has grown into the default creator partner platform for Devtools like Clerk, Browserbase, Neon, and Snyk. ✨ 2025 has been an inflection point: - More than doubled revenue vs 2024 - Doubled again between Jan–Aug - On track to more than double before year’s end New customers are adding recurring revenue and profit margins are rising. Clear validation that our model of platform + community + expert + AI is scaling. We’re now a core team of six. Added a Head of Ops, refining business & program ops. Invested more in our AI ops. Brought on a Senior Engineer for scaling the platform & building the next category of GTM features. Two years in, the lesson is clear: coders adopt tools through creators, communities & trusted content, not just traditional marketing motions. Plug exists to make that shift scalable, helping devtools turn creator partnerships into long-term programs rather than one-off experiments. Plug was built with and for the creator community and our growth has been a byproduct of their trust. Without outbound sales, referral programs, or traditional marketing, most of our momentum has come through word of mouth in the creator ecosystem. Today, Plug is home to the largest community of Creators That Code, with hundreds of dev influencers across YouTube, X, and beyond. They’ve shaped how we work, fueled our customer growth, and continue to be at the heart of everything we do. That’s why we published the Creators That Code blog (plug.dev/creatorblog), to put a name and framework around the movement they’ve driven. We were, are, and will continue to be creator-led. I’m proud of what we’ve built in just two years, grateful for the team behind it, appreciative for the support from the creator community and even more excited for what’s ahead @plugdotdev 🚀 Learn more about the Plug.Dev team: plug.dev/aboutus 🤗


The adoption of developer tools has changed, a lot. It hasn't been led by ads, or private forums. It’s been led by creators that code, the ones teaching, sharing, and influencing what tools developers choose to adopt and why. I wrote a deep dive on Creator-Led Growth for Devtools. What it is, why it matters, and how to put it into practice. Including some examples of CLG by Devtools like @clerk @neondatabase and @snyksec Here’s our @plugdotdev playbook for CLG: plug.dev/companyblog




