TankaOpen-source AI

Creators picked by tech stack and community standing, inside the topics developers discuss

Developers don't sit in mass-market audiences, and X's technical communities push back on marketing. Creators were screened by tech stack and community influence, not followers, and joined the conversations developers were already having, so the GitHub project drew real discussion instead of ads.

TankaSpanish-speaking developers
Growth readout
3,000+GitHub stars gained
630K+developer engagements
650technical posts
1 weekfor 400 creators
The data
Tech stack and community influence, not follower count
What the system did
400 tech creators matched and live within a week
What carries forward
A developer creator list organized by tech stack

What was at stake

The audience was developers. They don't show up in mass-market reach, and in X's technical communities they push back on marketing. Within one week, an open-source project had to become something developers actually talked about.

Business results

3,000+
GitHub stars gained
630K+
developer engagements
3B+
impressions on X

Where it standsThe developer creator list, organized by stack, is ready for the next launch.

What the data changed mid-project

The loop doesn't wait for the wrap-up. It turns while the project runs.

  1. Days 1–2

    A first batch of tech creators chosen by stack and community influence, joining the topics developers were already discussing.

  2. Day 2

    Discussion data showed AI agents were the hottest topic.

  3. Days 3–7

    Later creators and content concentrated on that topic, and the GitHub project drew organic discussion.

  4. Day 7

    400 creators and 650 technical posts live; GitHub stars up 3,000+.

The system behind this project

Of the pipeline's six stages, these did the heavy lifting here.

03 · Model

Creators screened by tech stack and community influence, not follower count

05 · Execute

400 tech creators publishing 650 technical posts within a week, inside the topics developers were already discussing

The challenges, and how we solved them

The audience is developers, who aren't found in mass-reach channels

Chose creators by tech stack and community influence, not follower count

Technical communities on X push back against marketing

Matched creators to the conversations developers actually have

Content had to be technically deep and still shareable

Sparked organic discussion of the GitHub project rather than ads

Technical content brought an open-source project into developer communities and got them talking.

In their words
We finally reached real developers, and the discussion on GitHub grew on its own.
Growth Lead, Tanka

Creator posts

Project figures

3B+Impressions on XAcross the campaign

Want a playbookof your own?

Share your product, target markets and budget. Once we agree on the brief, we quote the project.

Panoverse© 2026 Panoverse Inc. · panoverse.comSelf-serve creator search and free tools: Kolect ↗中文