Community and ecosystem
We help companies and associations choose the technical communities that matter to them, take part credibly, and where it makes sense, create and run a community of their own.
Concretely: a community judges you by what you contribute, not by what you announce. We work on the part that earns attention, and we do it from inside the same rooms.
When this is relevant
- The people who choose your technology are developers and engineers, and your current channels do not reach them.
- Your product is open source, or depends on it, and you have no presence where its users gather.
- You already sponsor events but cannot say what the sponsorship returned.
- You want a community around your product and need to know whether that is realistic before committing people to it.
Questions we help you answer
- Which communities hold the people you need to reach, and which are noise?
- Is taking part enough, or does this call for a community of your own?
- What does credible participation cost in people and time, not only in sponsorship?
- How will you tell whether it worked, without counting followers?
What we do
- Map the communities, working groups and events that match your technology and your audience.
- Plan a presence your people can sustain: contributions, talks, working group participation, and which events to skip.
- Prepare whoever represents you, so a talk or a stand holds up to technical questions.
- Where a community of your own is warranted, set it up: scope, governance, code of conduct, moderation, and the routine that keeps it alive after launch.
Typical outputs
- Community and event map, with a recommendation on where to be present and where not to be.
- Participation plan for a defined period, with the effort it requires named.
- Community charter: scope, governance, code of conduct and moderation model.
- Write-ups after each event, published where they are useful rather than filed internally.
What we do not do
- No follower counts or engagement rates presented as outcomes.
- No astroturfing, and no paid advocacy dressed as community.
- No social media management. This is participation in technical communities, not marketing operations.
- No claim that a community can be bought. It needs contribution over time, and if you are not prepared to sustain that, we will say so.
Related evidence
We work in these communities ourselves, which is the only reason to trust advice about them. Radixia is a member of the Eclipse Foundation and takes part in the Eclipse Cloud Interest Group, whose subject is cloud autonomy and portability, and was among the first members to sign up at its kick-off:Radixia and Eclipse Foundation. We attend FOSDEM and SFSCon, spoke at OCX 2026 in Brussels, and take part in meetups in Milan and elsewhere in Europe. Theabout page states our memberships and speaking engagements in full, along with the other roles our founder holds.