Introducing the Jupiter DevRel Working Group (DRWG)
We’re excited to propose the Jup DevRel Working Group (DRWG) to support and grow the developer community in the Jupiverse, which has been booming over the past two years. Back in Cat Year 0, the Jupiter team focused heavily on building top-notch products—not just for everyday users, but also for developers, with things like APIs and other tools. They’ve been busy creating and polishing these internally, and it’s paid off: more and more developers have started jumping in, building cool stuff in and around the Jupiter ecosystem. But with the Jupiter team so focused on product development, there’s been little room to guide these developers, help them settle in, or keep them engaged.
That’s where the DRWG comes in. We want to be the bridge for this growing technical crowd—helping them solve problems, feel supported, and truly feel at home in the Jupiverse.
Purpose / Problem
The Jupiverse is growing fast, but its developer community is hitting roadblocks on both sides of the ecosystem. The Jupiter Team is laser-focused on building and rolling out new features non-stop, leaving little time to engage with the technical community. In the past, this meant official documentation and Git repositories fell behind, outdated by the rapid pace of development. Developer support has been shouldered by just two team members—one of them the CTO, who’s sent over 50,000 messages in two years to keep things afloat. That’s a Herculean effort, but it’s not sustainable, and it leaves developers without the guidance they need to fully leverage Jupiter’s tools.
Meanwhile, on the DAO side, the Core Working Group (CWG) is swamped with tasks and lacks the bandwidth or technical know-how to act as a proper entry point for the technical community. Community developers—those eager to build, get feedback, and dive deeper into the Jupiverse—have struggled to find their footing. In its first year, the DAO prioritized grantees and social outreach over technical projects, which made life tougher for devs trying to contribute or get involved. The result? A gap between the Jupiter Team’s output and the DAO’s community, with developers caught in the middle—unsupported, disconnected, and without a clear path to thrive. The DRWG exists to fix this, bridging the divide and giving the technical community the attention it deserves.
Solution / Deliverables
Supporting the Jupiter Team
-
Developer support
As mentioned before the core team spends many hours in the developer support channel in discord. Our goal in the short/mid term is to overtake this channel as fast as possible so that the team can focus on their core tasks. (@Dann and @Fiji are putting great efforts into this with @Fiji bringing an enormous effort of over 1.000 messages in the dev support channel in the past 30 days. These are not regular “JM” messages but technical answers / solutions to the community.) -
Documentation support
The Jupiter team is working non stop on new features and the documentation stays behind.
The DevRel team finds missing / incomplete topics in the API Usage, communicates these with the team and the problems get fixed. -
DevRel code repository with examples / SDKs
We have already created a GitHub organisation with Typescript and Python examples on how to use the existing Jupiter APIs. A python SDK is in the makings. -
Public existing code repositories / libraries maintenance
Unified wallet and terminal repositories start getting maintained by the DevRel team.
Referral Dashboard is also a potential application for maintenance. -
Provide data to the Jupiter Team where needed.
In the past weeks we have created a DevRel Flipside account where we provide Governance data from public sources. Data is the same as Catalytics provides but from different sources and this is the proof that both projects provide valid data.
Supporting the DAO
Our goal here is to be the first contact for technical community members and projects. As developers who have already built in the Jupiverse we know that it is not easy to get heard and to get feedback from other technical community members. We see ourselves as the “Core Working Group” for Developers. We proposed the following change in the Jupiter discord channel:
Our idea is that the Discord needs an area for Developers to feel at home.
- dev-notifications
Here we want to be able to announce new releases of APIs, versions, dev community calls, bounties, etc. - dev-links
In this channel our idea is that we want to provide to developers a channel with all the official links that exist, including community projects. - dev-support
This channel stays the same as today and people can come and ask for help and guidance based on their projects and needs. - dev-chat
This channel is a very crucial one. At the moment all developers gather either in the global general chat or in the dev-support to talk about their ideas and projects. Our vision is that this channel will gather developers from different communities and that it will become a place where developers can chat and exchange ideas. - dev-vc
This voice channel should be used by developers who want to showcase their products, exchange ideas but also for developer community calls that the DevRel is going to organize
For this to happen we propose to introduce a discord role for the DevRel members.
This role will be responsible for the organisation of this Developer Section in discord.
Our goal is to make developers feel welcome to our community and try to push them to their limits by providing them the best possible support and channels to interact.
As DevRel we will pick the most interested and talented developers and showcase their projects. Additionally, we will look for community members who want to be part of our initiative and integrate them if we find the right people.
Public face of the Jupiter DevRel WG
Of course all the points we touched until now are hard work and very time consuming. Nonetheless it is extremely important to maintain a professional public face to the outer world.
We plan to launch our X Account soon. (We have already done that but we are facing issues with X, our accounts get suspended all the time. We are working on it with the Team and the DAO). Our X account will be the public face of the DevRel and some of our plans are the following:
- Getting in contact with other developer communities from Solana and not only.
- Creating X-Spaces where we talk about future releases or we highlight existing community projects
- Launching the “Jupiter DevRel Educational Series”. This is something we are already working on. In this series we are going to touch technical FAQs and “How to” on 3 different Difficulties:.
- “Easy” for everyone
- “Medium” for technical and non technical users
- “Hard” only for advanced technical users
This will contain infographics, examples and tips.
Example: Draft by Konstantinos | Typefully
More far-fetched ideas for the future
- Professional social media content / Youtube
- Contribute to core Jupiter products
- Help other community members create community projects like (Jupiverse Kit, Catalytics) to bring under the umbrella of DevRel
- Being able to grant bigger community projects as DevRel
- Expand examples to Rust and GoLang
- AI Agent for developer support channel
- Live coding sessions showcasing Jupiter products
The Team (DRWG)
https://x.com/solatropos
Konstantinos - Lead, Software Engineer, Passionate communicator/problem solver
Grew up in Greece. At 18 years of age moved to Germany to explore new things and a couple of years later started studying applied computer sciences. Since then worked in several technical projects in the sports and insurance sector and meanwhile living in Switzerland and working in the banking sector as a Fullstack engineer focused on frontend development and leading a team of developers.
Additional to that co-Founder of @catalyticspro
https://x.com/dannweeeee
Dann - Builder, Technical Content Lead, Software Engineer, Open source contributor
Born and raised in Singapore. Actively contributing and building open source projects. Previously contributed as a Full Stack Developer and Blockchain Developer at Web3 Gaming and Infrastructure projects. Passionate about building products and sharing my experience. Serial hackathon winner.
Additionally, creator of @jupiversekit
https://x.com/fiji_solutions
Fiji - Software Engineer, Technical Lead, Focused on Getting Things Done
Greek, living in Switzerland for the past year. Software engineer with over seven years of experience. Passionate about building tools that simplify people’s lives. Have worked across various technologies, built production-ready infrastructures from scratch, and got involved in different sectors like Telecommunications, Banking, Travel, and Retail.
Also co-Founder of @catalyticspro
Proof of work
Catalytics
Product: https://catalytics.pro
X Account: https://x.com/catalyticspro
Catalytics is a platform where users can get statistics and metrics about the Jupiter Governance, Solana LSTs and some other small features.
This initiative was founded by @Konstantinos and @Fiji in August 2024 and received a grant from the Jupiter DAO in December 2024.
Since then the X-Account has grown organically to almost 2.200 followers at the time writing this proposal and has almost 30.000 unique addresses that have used the “Jupiter Governance Profile”. A unique feature that provides detailed analytics about a users governance activity in the Jupiverse. The platform is averaging between 2.000 and 3.000 visits per day.
Jupiverse Kit
Product: https://www.jupiversekit.xyz
X Account: https://x.com/jupiversekit
Jupiverse Kit is a full stack React components library that makes building onchain products as easy as possible with the help of Jupiter’s APIs.
This initiative was founded by @Dann in November 2024 and it is built purely as an open source passion project allowing builders who build on Solana to easily leverage Jupiter’s products.
Since then, Jupiverse Kit has significantly expanded the adoption of Jupiter’s products, reaching a peak of over 280+ weekly downloads for the NPM SDK. It has also contributed to multiple live projects, with a notable example being bonk.fun.
Community and ecosystem Projects
We believe supporting community and ecosystem projects is a big deal for Jupiverse builders. Our goal is to help these developers by covering costs like hosting, subscriptions, and deployments—basically, the practical stuff that keeps technical projects running. More and more people are building tools on Jupiter’s products, and we want to be there for them with advice, tech support, and funding to make their lives easier.
We have already been hands-on with projects like reviewing and auditing the Jupiter Appreciation extension (v1.0.1) the CaWG created. Now, we want to take Catalytics and Jupiverse Kit to the next level by bringing them under the DRWG umbrella. They’ll stay standalone but get our full attention for updates and growth, driven by what the community tells us they need. Building and maintaining these projects takes time and costs money, but with the buzz they have already got, we are all in. As our workgroup grows, new members will pitch in, and together we will keep shaping these tools to fit the Jupiverse. This is about lifting up every builder, not promoting our own work.
By the time this proposal goes live we officially start accepting requests by community developers who are willing to join our initiative by evolving with us and shaping the future of Developer Relations in the Jupiverse. An official post from our X Account (when problems resolve) will be released.
Budget
For what we have described until now in this proposal we are proposing a 3-month Budget with the following breakdown.
| Salaries core members (3) | 5.500 USDC / member / month | 49.500 USDC |
|---|---|---|
| Technical community grants** | 5.000 USDC | |
| Trial members compensation*** | 4.500 USDC | |
| Total for 3 months | 59.000 USDC |
** We want to be able to identify community projects in this first phase of the DRWG and grant them with some USDC
** We want to trial some community members. Does not have to be full time. Can be several people
Risks / Challenges
From our point of view, we do not see any risks for our WG. We know each other well and have worked on several tasks together in the past. Nevertheless no plan is bulletproof and we have identified some challenges that might come on our way.
Coordination with the Jupiter Team / DAO
Until now we have not faced any problems but since the Team and the DAO are very busy with organising several things around the community there might be limited time to help us achieve our goals.
For example the Team delivers several new features and there is no time to communicate these with us. Another example is that the Discord suggestion we propose will not be implemented.
X Limitations
We are facing problems with the creation of our X account for over a month right now. Every account we create gets suspended and we have tried this already 3 times. X is unfortunately not responsive enough to help us solve this problem.
Keeping up with the demand and community
Since we are integrating Catalytics and Jupiverse Kit under the umbrella of DRWG and we are asking from the community to give us active feedback and requirements, there is a possibility that these tasks overlap with the other DevRel tasks and then we will have to prioritize features. This is not a problem, just pointing that there might be delays with delivering new features of these products.
Long term vision
Our vision is to grow the DRWG into a standalone crew that sits right between the Jupiter Team and the DAO, working smoothly with both. Down the road, we want to do more than just support devs—we want to team up with the community to build products and features together. Picture this: organizing events, running reviews, and even hosting real-life meetups (yep, IRL and offline stuff is on our radar). We see ourselves as the bridge not just within Jupiter, but also to other communities in the Solana ecosystem, pulling them in to build with us and shape the Jupiverse future.
