---
type: "article"
title: "Big question: Should Commune go Open Source?"
newsletter: "The Weekly Shift"
newsletter_handle: "franmendez"
newsletter_url: "https://usecommune.com/n/franmendez"
author: "Fran Mendez (@fmvilas)"
published: "2026-02-13T11:30:00.000Z"
canonical_url: "https://usecommune.com/n/franmendez/a/big-question-should-commune-go-open-source"
markdown_url: "https://usecommune.com/n/franmendez/a/big-question-should-commune-go-open-source.md"
chat_url: "https://usecommune.com/n/franmendez/a/big-question-should-commune-go-open-source/chat"
source_url: "https://newsletter.fmvilas.me/posts/big-question-should-commune-go-open-source"
body_source: "imported"
likes: 10
replies: 17
body_words: 180
---

# Big question: Should Commune go Open Source?

![The Weekly Shift](https://embed.filekitcdn.com/e/tppsnKSSV6RtcQVLeDZHT8/5nEuhXaXN7FANZ4f1qdrrM?auto=)

Usually, I use this newsletter to share what I’m reading or thinking. Today, I’m flipping the script. I need your brain on one specific thing I’m wrestling with.

**Should we make Commune fully open-source?**

[![](https://embed.filekitcdn.com/e/tppsnKSSV6RtcQVLeDZHT8/wS6akGKJ7qvSAPuMdS3vE7/email)](https://usecommune.com/n/franmendez?article_timestamp=1770982215)

I’ve been building Commune as a headless, creator-first alternative to Substack. The goal is total independence. But lately, I’ve been asking myself if we need to take that a step further.

You know my track record here. I built the AsyncAPI Initiative on the premise that specifications should belong to the community, not a single corporation. I literally turned down a million-dollar offer to acquire AsyncAPI because I knew it had to remain neutral.

I don’t compromise on digital liberty.

So, the question is: Should we do the same for Commune? Should we build the alternative that guarantees you’re never locked in and never beholden to a platform’s algorithm or roadmap?

**I need to know what you think.**

Hit the button below and let me know what you think.

[![](https://embed.filekitcdn.com/e/tppsnKSSV6RtcQVLeDZHT8/wS6akGKJ7qvSAPuMdS3vE7/email)](https://usecommune.com/n/franmendez?article_timestamp=1770982215)

*​*

[![linkedin](https://functions-js.kit.com/icons?icon=linkedin&foreground=ffffff&background=153461&shape=square&v=3)​](https://linkedin.com/in/fmvilas)[![youtube](https://functions-js.kit.com/icons?icon=youtube&foreground=ffffff&background=153461&shape=square&v=3)​](https://youtube.com/@fmvilas)[![github](https://functions-js.kit.com/icons?icon=github&foreground=ffffff&background=153461&shape=square&v=3)​](https://github.com/fmvilas)

Av. Joaquín Costa, 16, Badajoz, Badajoz 06001
​[Unsubscribe](https://preview.convertkit-mail2.com/unsubscribe) · [Preferences](https://preview.convertkit-mail2.com/preferences)​

***

## Discussion (17 replies)

Numbering shows the reply tree: `2.1` is a reply to `2`. Message text is reproduced verbatim as posted.

### 1. Fran Mendez (@fmvilas) - 2026-02-13T12:33:31.324Z

Curious to know what you think 🙂 Don't be shy!

### 2. Aleix Morgadas (@aleixmorgadas) - 2026-02-13T14:14:56.894Z

A reply that needs more thought and it might be too vague 👇

> So, the question is: Should we do the same for Commune? Should we build the alternative that guarantees you’re never locked in and never beholden to a platform’s algorithm or roadmap?

That's a bold statement, and harder to accomplish due to the nature of having to run a service that stores the data for the different users. Another approach would be to make Commune to use a distributed social protocol to achieve the vision. Yet, we know how hard it is using the examples of Mastodon and Bluesky.

Another approach would be about Communte to be contributed and have a group of developers that help the development to be followed under a certain rules.

I think OSS makes sense if it comes along with OpenData (I think this is the right term), so users can move their information to another platform if they want to.

Happy to join this effort Fran 😄

#### 2.1. Fran Mendez (@fmvilas) - 2026-02-13T20:19:58.544Z

Yeah, the idea in my head is to make it an atproto client so instances deployed on different machines could federate. I don't even think we'd have to invent anything different than what Bluesky already provides so we could even use their PDS. Or create one that's compatible with Bluesky's one. Exactly what you said: "so users can move their information to another platform if they want to".

I know it's not easy but that doesn't worry me 😄 It would be a good and fun engineering exercise!

### 3. Ivan García Sainz Aja (@ivangsa) - 2026-02-13T15:40:27.277Z

I'm an opensource practiotioner because something deep inside tells me that's what I want to be, also because I have a passion for learning how rhings work and third because coming from a different field, I learn everything computers/programming from opensource software.. That being said I do not feel the urge to learn how a service such as Commune works neither I am planning to build upon that learning.. therefor I have zero interest on Commune to be opensourced. I wouldnt worry too much about opensource it. My favorite subscription is not opensource and I love listening to music there, for years, and years to come.

#### 3.1. Fran Mendez (@fmvilas) - 2026-02-13T20:23:35.184Z

Yeah, in your case it's very different. You don't even own a newsletter yet so you don't feel the urge for that. Also, making it open source means you **could** deploy it yourself if you wanted to but there would always be an instance running on usecommune.com that you could use as well if you're not in the mood. What would make it powerful is that you could leave if you wanted to. Say, for instance, that I sell it and the new owners decide to make it expensive. You would have that choice unlike with closed networks like Substack. Even another person could start offering the same service at cheaper prices or free!

### 4. Ronald _ (@flake) - 2026-02-13T15:43:15.429Z

quick thought: yes

### 5. Ismael Gutiérrez (@ismael) - 2026-02-13T17:20:24.348Z

Dada tu situación vital, tal y como comentas en tus mensajes, mi respuesta sería que depende de lo que te pueda dar paz y tranquilidad. Es decir, si abres el código a todo el mundo, supondrá que todos podamos ayudar y, por contra, que sientas la necesidad de respondernos/atendernos.  
Por otro lado, si lo mantienes tal y como está, seguirás “solo” en el camino, y eso puede ser complicado, pero seguirías “a tu ritmo”. 

Lo mío es solo una opinión, por supuesto jejej igualmente, tengo la sospecha de que dentro de ti ya sabes la respuesta 😜

#### 5.1. Fran Mendez (@fmvilas) - 2026-02-13T20:27:36.347Z

Hehe! En eso tengo experiencia. No me importa crear comunidad. Es más, para eso lancé Commune, para convertir esta newsletter en una comunidad. Y parece que funciona! 🎉

Obviamente tengo una ligera inclinación hacia la opción de hacerlo open source sino no hubiera preguntado siquiera haha! Creo que puede ser algo muy chulo y útil. Soy consciente que me metería en otro jardín pero tengo fama de ser buen jardinero haha!

#### 5.2. Ismael Gutiérrez (@ismael) - 2026-02-15T12:10:26.128Z

> Quoting Fran Mendez (@fmvilas): Hehe! En eso tengo experiencia. No me importa crear comunidad. Es más, para eso lancé Commune, para convertir esta newsletter en una comunidad. Y parece que funciona! 🎉 Obviamente tengo una ligera in…

¡Claro que funciona! Jejej
A eso me refería, que ya se intuía lo que harías 😜
Pues ya sabes, hagas lo que hagas, estaré “pisteando” 🌻🌷🪴👨‍🌾😅

### 6. Fran Mendez (@fmvilas) - 2026-02-13T20:30:33.676Z

To clarify for everyone reading. In my mind, this would require two things:
1. Make it distributed. Use something like atproto to make different instances federate their content.
2. Offer a paid version at usecommune.com so I can make this project sustainable. Perhaps it can have a free tier but the idea is that if you want great features for free, you should deploy it yourself. Otherwise, you have to pay. I think it's a fair model.

### 7. Kin Lane (@kinlane) - 2026-02-13T20:47:45.926Z

I'm going to go against the grain. No, I don't think you should. I think you should be a strong commercially sustainable platform that grows at a reasonable rate and doesn't take on all that comes with being open-source or venture-backed. Build a real business. Charge fair price that will sustain the business long into the future. There might be open opportunities down the road, but in today's hostile online environment I do not recommend it.

### 8. Thulisile Sibanda (@thulieblack) - 2026-02-15T14:19:14.796Z

Well, it would be good to have a paid subscription for maintenance long-term. You could have an open source/free tier, but it's safe to have a paid version as well to maintain the platform. Just thoughts

### 9. Steven Willmott (@njyx) - 2026-02-15T20:43:11.285Z

Great question Fran... I think it's a complicated one - with lots of beliefs (and yes emotions) attached to it + some realities. Definitely not going to claim to have the definitive answer but I think while open-source can be part of making something succeed (and achieve a specific type of goal) it's rarely the "answer" or most of the answer. Partly because as well as benefits, it also has significant costs, not only that you might be able to monestise less (which you have to do to survive) but also because the maintenance has it's own cost. In my view the opportunity for something like Commune (and ... I think?! ... a bit part of your goal) is to enable conversation and network effects between newsletters in a way that current newsletter silo providers don't support. So the real question is - how can you make that happen and grow the base of both connected newsletters and readers? I think when looking at that it probably involves three pillars: 1) super easy to use onboarding and user experience (ideally with a free tier) that just works... (tick in the box so far!) ... but that will also need some revenue to keep evolving and working, 2) open standards and integration ... trying to make it easier and easier for more news letters and readers to connect. In the ultimate state of this part: making it possible to build a commune client or publisher app that just connects to the commune network... 3) open-source -- enabling people to do 2 without writing their own software. My suspicion is, though, that #1 and #2 are more important in the short and mid-term than #3. Having been at Red Hat for four years, I've seen the pros and cons of an open-source business model, and I think for a single product team, you really need a way to grow revenue and support before you go there. That might not be universally true, but I think it often is. I'm also a Venture Partner at an investment fund that only invests in network effects and from that experience ... I do think in something like Commune the big challenge is finding the ways to make it as universal and open as possible for people to just use and join the conversation. Open Source can help but most likely open standards and connectivity might be more important. Great conversation! Also ... give @kinlane  an API and problem solved ;-)

### 10. Fran Mendez (@fmvilas) - 2026-02-16T12:08:39.333Z

Wow! I'm still processing all your responses ❤️

One thing is clear: I built Commune to create a community around your newsletter. I was wondering if that would ever work. Well, it works! Let's appreciate the fact that we all are connecting here.

I know I know, it's a bit tangential to the topic 😅 I'll get back to it 🙂

### 11. Pascal Heus (@plgah) - 2026-02-16T17:30:11.716Z

Here is a though: don't open source now, but announce that it will all become open source in 5 years, or whenever you feel you'll need your freedom again. ... In the meantime, grow the platform, get some income out of it, build a team of young developers you can pass the platform to down the road, have fun, be yourself, live your passion. Oh, and yes, a free tier feels like a must have.

### 12. Er Galvão Abbott (@galvao) - 2026-02-16T23:30:19.641Z

I believe so, yes. In my opinion open source is the abosultely best way to develop software. Everyone benefits from it: the product, the community, the consumer. I know open sourcing a project comes with it's challenges, but I think it will be totally worth it.

### 13. Ronald _ (@flake) - 2026-02-20T14:34:36.347Z

Reading the email "You all told me I was wrong. You were right" and still without heaving read everything in this thread I wonder if everybody is talking about the same thing. For me making something open source doesn't mean you _develop_ it open source. You can make it source-available and allow forks and contributions without opening yourself up to steering commitees and AI slop issue floods. You can very much have a discord, for example, where real people can utter real issues and wishes, etc.