Friendly Clarification About Per-Seat Pricing #1914
Unanswered
altrsadmin
asked this question in
Q&A
Replies: 2 comments
-
|
👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@tea-artist Hello, friend! Please help us understand the pricing — we're eager to move the project forward! |
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.
-
Hello, this doesn’t quite make sense—please see:
I’ve installed the free self-hosted plan and I’m currently able to add multiple users, including assigning creator roles (in my case, just two). The rest are all our clients (a common use case), meaning they don’t access the system directly—they only interact via forms or submit data, without creating anything.
This setup is already more than sufficient. I’d be happy to pay for a self-hosted license for my instance, as a way to support the project and continue testing its features. However, a model where I end up paying significantly more than the cloud version per user on self-hosted doesn’t make much sense.
Did I understand correctly? Would I need to pay per seat even for viewers and editors?
Wouldn’t it make more sense to offer a one-time fee—say, $20—for a license tied to my self-hosted instance? That way, I could continue using the system with my current setup while supporting the project financially. It feels like a fair and sustainable model, especially for small teams or use cases where most users are passive participants.
Beta Was this translation helpful? Give feedback.
All reactions