Starting today, the Obsidian Commercial license is optional. Anyone can use Obsidian for work, for free. Explore organizations that support Obsidian on our new Enterprise page.
I don’t necessarily like a few takes in the comments here.
Vibes wise the Obsidian team seems to be great and they don’t seem to have shown any reason why I should distrust them. I love FOSS but gifting others my work doesn’t put food on my table, so in that sense they need to have a lucrative business model which they seem to have established.
I could use SyncThing, Git or other solutions to do synchronisation between my devices but I choose to buy their Sync offer, since I want to support them (they also have EU servers, which need to be GDPR compliant by law afaik).
The closest comparison I could make is NextCloud. NextCloud open sources their software, but they sell convenience. Sure, you could self host it, but paying them to do so for you may be more attractive. In comparison Obsidian is not really complicated to set up or maintain. It’s literally just a MD-editor. So the only convenient thing to sell is synchronisation if you don’t want to put a price tag on the software.
If they open source all their code, some tech wizard will implement a self hosted obsidian sync server with the same convenience as theirs in a day, and the company will lose their revenue stream.
We’ve all been burned by tech bros in one way or another, but I think it’s ok for people to profit off of their IP. And they seem to be doing so with a positive vision. Feel free to let me eat my words if they ever go rogue, but that’s my 2 cents.
Thanks for the rare, rational comment regarding Obsidian. Many people here seem to think releasing software as closed source automatically means you have something to hide; seemingly forgetting we live in a capitalist system in which you must constantly sell your services to survive. (I am saying this as someone who adores FOSS and donates to most of my homelab software on a regular basis).
I think a more productive way to look at is: is the closed source dev friendly (or at least non-hostile) to the open source community? In the case of Obsidian, they haven’t done anything egregious, and regularly contribute to open source plugins. Furthermore, the notes are stored as markdown files. This gives the user strong resistance against potential enshittification, so even if they did go rogue you can just move to some other text editor lol. Granted, you would miss out on plugins but otherwise that’s a good reason to keep your plugin usage light and plan your Obsidian vault accordingly.
If they open source all their code, some tech wizard will implement a self hosted obsidian sync server with the same convenience as theirs in a day, and the company will lose their revenue stream
Obsidian is storing everything as plaintext files. Those convenient selfhosted sync solutions have been out there for years.
It’s not just about syncing files. It’s also the fact I can edit stuff on my tablet and see the changes in almost real time on my laptop with Obsidian Sync. I believe most other solutions wouldn’t play nice with such a workflow.
I don’t necessarily like a few takes in the comments here.
Vibes wise the Obsidian team seems to be great and they don’t seem to have shown any reason why I should distrust them. I love FOSS but gifting others my work doesn’t put food on my table, so in that sense they need to have a lucrative business model which they seem to have established.
I could use SyncThing, Git or other solutions to do synchronisation between my devices but I choose to buy their Sync offer, since I want to support them (they also have EU servers, which need to be GDPR compliant by law afaik).
The closest comparison I could make is NextCloud. NextCloud open sources their software, but they sell convenience. Sure, you could self host it, but paying them to do so for you may be more attractive. In comparison Obsidian is not really complicated to set up or maintain. It’s literally just a MD-editor. So the only convenient thing to sell is synchronisation if you don’t want to put a price tag on the software.
If they open source all their code, some tech wizard will implement a self hosted obsidian sync server with the same convenience as theirs in a day, and the company will lose their revenue stream.
We’ve all been burned by tech bros in one way or another, but I think it’s ok for people to profit off of their IP. And they seem to be doing so with a positive vision. Feel free to let me eat my words if they ever go rogue, but that’s my 2 cents.
Someone develops logseq which is completely foss and like obsidian. Now I can choose to donate to FOSS or buy closed source. How do you decide?
We just need to establish paying for open source software more.
https://github.com/logseq/logseq/
Thanks for the rare, rational comment regarding Obsidian. Many people here seem to think releasing software as closed source automatically means you have something to hide; seemingly forgetting we live in a capitalist system in which you must constantly sell your services to survive. (I am saying this as someone who adores FOSS and donates to most of my homelab software on a regular basis).
I think a more productive way to look at is: is the closed source dev friendly (or at least non-hostile) to the open source community? In the case of Obsidian, they haven’t done anything egregious, and regularly contribute to open source plugins. Furthermore, the notes are stored as markdown files. This gives the user strong resistance against potential enshittification, so even if they did go rogue you can just move to some other text editor lol. Granted, you would miss out on plugins but otherwise that’s a good reason to keep your plugin usage light and plan your Obsidian vault accordingly.
Obsidian is storing everything as plaintext files. Those convenient selfhosted sync solutions have been out there for years.
It’s not just about syncing files. It’s also the fact I can edit stuff on my tablet and see the changes in almost real time on my laptop with Obsidian Sync. I believe most other solutions wouldn’t play nice with such a workflow.
https://github.com/remotely-save/remotely-save