-
Notifications
You must be signed in to change notification settings - Fork 178
So River looks awesome and I would like to test/use it one day. But before I can consider this as a valid option I was wondering if the River Pro features are available while developing.
I think it's fine to pay for something once it's being used in production (or in any remote environment - whatever you call it), but I find it hard to start paying for something while I am not even sure if I am going to need it.
Perhaps I should just start with the opensource only options, but those "Pro" features look really nice as well.
To me, not being able to use the pro features locally (and perhaps CI), makes it hard to choose River as a possible candidate, however wonderful it might be.
(Context: I don't currently have any specific projects where I want to use this, but I am doing some research and came across River).
All reactions
Replies: 1 comment
Fair question. I don't have a fully articulated answer on this (have only thought about it for a few minutes), but a dev option would more or less make all the Pro code open content, and at that point it'd be trivially easy to just keep using with no intention to pay, or to use an LLM to transliterate into a similar shape that's technically a different codebase.
The Pro model today doesn't completely protect us against that either, but I feel a little better about it knowing the majority of the people coming in the door are honest B2B actors who aren't constitutionally against putting a credit card down for the product.