Hey. Thanks for the awesome tool.
Not exactly a feature request. And I believe you have your reasons for not open sourcing it. But nevertheless I wanted to share a perspective you may not have considered.
There are a ton of other similar solutions out there of various degrees of polish. And the heart of all of them (including Vowen) is those open-weight models anyway. So the fundamental technology you and others use is not a trade secret.
While commitment to do the processing locally and/or with the user-configured providers, and not send user data to the developers sounds great, it's not really easily verifiable. It basically makes Vowen impossible to get a permission to use Vowen in an enterprise environment where information security standards are high. For closed source solutions the matter of trust is often solved through certifications (SOC2, ISO etc). However this is clearly not a viable solution for a side project worked by a team of 2 (both due to overhead to manage processes and cost of such certifications). This effectively narrows down the possible user base.
Now,if you're looking to monetize your app in the future, it may be worth to learn from many AI-powered open source tools out there (OpenCode, Kilo Code etc.). They often have the end user app open source, but provide paid a control plane for enterprises to centrally manage their users and their licenses instead of having to issue and rotate individual tokens to each employee.
So, I hope you'll at least give this idea another thought.
Thanks again for building Vowen.
Alex
Please authenticate to join the conversation.
Rejected
Feature Request
25 days ago

Alexandr Zolotukhin
Get notified by email when there are changes.
Rejected
Feature Request
25 days ago

Alexandr Zolotukhin
Get notified by email when there are changes.