Replies: 2 comments 1 reply
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@mwa85 where are you seeing that price increase i thought it was 19/mnth still on the site? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
This comment made me think:
#509 (comment)
I completely understand @rustdesk position on the new take, but I don't agree 100% this is the correct way, let me explain.
First of all, I am one of the potential (paying) user base of rustdesk. I do remote assistance everyday and TeamViewer is my solution now. I'm not an happy customer, for many reasons:
Notice I haven't included the price in this list, because this is a tool for my job and I think 20-30€ /month/seat is a reasonable price for this tool and its features.
I can't switch to Rustdesk right now because I need:
I'm writing this because Rustdesk is gaining momentum at the time (beiing the only viable open-source alternative to TeamViewer/Anydesk), a lot of "lower tier" users of other solutions are open to change and looking for an alternative, and we (more or less) think in the same way.
As I said, I understand your idea to reserve some features for paying customers only, but please, consider the simplicity of a dual-licensing: if I use Rustdesk to make money, I need a paying license (with support and all the bells and whistles), otherwise I'm OK with the "free model". No feature or code difference. Only one community, no need to differentiate paying and free users.
My fear is that if you start removing features now (in a moment where I can't buy this product because it misses some features I need), it'll be hard in the future to focus on reliability of such features. If a feature is "behind a paywall" this means less userbase, less testing, less community focus...
I saw some issues in the past because @rustdesk didn't have a raspberrypi on hand to do some test; this happens and the role of the community is helping a developer with these issues. Less users involed means a lower possibility to get help. This time is a raspberrypi, next time maybe you need a hand with a strange kubernetes setup, or worse.
If you start to offer "normal" and "premium" features, it means you have "normal" and "premium" users, "normal" and "premium" products. Are you sure you want to make this distinction?
If I think at other open-source projects I use everyday, like Zabbix and Grafana (we can name a lot of them), their "community edition" is not a "castrated enterprise edition", but a full product.
Hope I didn't offend anyone, I just wanted to share my 2 cents.
Beta Was this translation helpful? Give feedback.
All reactions