Open Source Metering and Usage Based Billing. Contribute to getlago/lago development by creating an account on GitHub.

cross-posted from: https://lemmy.world/post/6355296

I cannot count the number of times I’ve heard, “This product is X, but open source.”

And I’ll admit it—I’ve done the same when describing Lago. When I’m not in the “startup pitch” mood, I default to, “We’re Stripe Billing, but open source”. Or my co-founder might say, “We’re like an open-source Chargebee.” Frankly, it gets the job done.

Of course, if that’s all there was to us, we would have failed by now. What we’ve learned is that open-source tools can’t rely on being an open-source alternative to an already successful business. A developer can’t just imitate a product, tag on an MIT license, and call it a day. As awesome as [commercial] open source is, in a vacuum, it’s not enough to succeed.

  • @[email protected]
    18•8 months ago

    Love it. Trust is also why I’m using Logseq for note taking and “Building a Second Brain”. I’m putting lots of sensitive personal and work information into it, so having plain text files stored locally in a standardized format is critical. My data is completely safe and future-proof.

    Ironically, the lack of vendor lock-in is likely going to lead to me sticking with Logseq for a very long time.

    I also pay/donate $5/mo to get access to their fully-encrypted cloud sync (and to support the project). I really like the idea of nobody having access to the content of my notes, as would be the case if I used Google Drive or OneDrive to sync plaintext files.

    As the article says, in cases where trust is important, open source has a significant advantage.

    • Kaldo
      6•8 months ago

      If there’s one lesson we should have all learned by now, it’s that it really sucks to depend on the whims of some corporation for software you use often. They all go bad inevitably.

      I also switched from obsidian to logseq and I really like it so far, I just wish it had a better smarter search. People recommend queries but they are annoying and clunky to use when you just want to quickly look something up.

    • @[email protected]
      5•8 months ago

      I moved recently to logseq on the same premise.

      However I found that logseq markdown is a kind of a vendor lock in. To be honest I have also tried joplin and obsidian as well.

      While obsidian failed because NoT FOsS duh, joplin was disregarded (at first) because it uses a database and not plain text files.

      I was migrating from tiddlywiki. First to joplin, then to obsidian and then to logseq.

      And although the latter are using all markdown format as their base, they all have their small catches where they differentiate. Sure you do not loose access to bulk of your data. But what would have been the difference to be vendor locked in in years and extract the data from a sql database?