What's up with the paywalling?

Hey,

I just upgraded my self hosted instance and noticed that record revision history is now limited to 30 days without upgrading. I do understand and respect that you have to make certain decisions to make this great project profitable and ensure long-term maintainability. But I need to express my disappointment over the way this is going down. Introducing more and more features and UI elements that cannot be used without a license is one thing. And I personally don’t have an issue with that whatsoever. But locking existing features behind a paywall - essentially beginning to starve the free version of features - is a different story altogether. Because I don’t know what will be missing next. Or what already is that I just didn’t notice yet. Makes me feel rather insecure about using this software anymore except for demo purposes - or is that the intention?

Hey @lagun, welcome to the community! :waving_hand:

Thanks for flagging this, and I want to put your mind at ease right away: this is a UI bug, not a policy change. We never take OSS features and gate them. Its not our policy. Record revision history on self-hosted will stay exactly as it was — nothing is being silently moved behind a paywall, and your existing history is untouched.

We’re tracking this in #13341 and a fix will be provided with upcoming OSS releases.

Really appreciate your trust in the project, and apologies for the scare the misleading display caused. We are streamlining the various versions (cloud, OSS, on-premise).

Oh I see, apologies for jumping to conclusions then. I didn’t personally tie the issue you mentioned to what I was seeing - I actually experienced the history missing bug myself, but at the time with 0.301.5 I wasn’t prompted to upgrade yet. That just came with the latest release.

Anyways, thanks for the super quick reply and for clearing things up!

1 Like