Yes, I understand the risk, but I really care about trying something new and risky and getting more users rather than running a slow-growing business. If Amazon steals it from me tomorrow, I think I will celebrate for a week :-)
Thank you so much! I got it written down, and we will check account links separately. I understand about the updates. I heard that regular updates are important for GitHub also, to know which projects are alive and which are dead. Interesting, thanks!
That's all true, but why not put it out there for all to see? This project is useful. People are using it. There are customers with hundreds of users and tens of millions of rows in the database. But the product is not growing fast. What's the point of hiding this code and not putting it out into the open source?
It's simpler — we're not growing as fast as we want. So, for us, the value of the code is not great. I am interested in putting it out in the open and seeing what happens. It would be great if I could gather a community around it and make more people use it. If not, we lose nothing crucial because only fast-growing products interest us.
I agree, but I don't see any point in selling it. I'd instead post the code and use it in all my other businesses without depending on the buyer. Besides, there is still a market for Odoo and Zoho integrators, and I think we can try to gather some of these people around our product.
> I would consider what kind of licensing you want to do, I would also consider goals in doing this. One huge benefit of an open source SaaS offering is the freedom to take control of what you're getting out of it in-house, or going straight to the vendor.
We plan to put both back and front under Apache-2.0. It seems like a good enough way to show that the user won't depend on us.
> Will you be offering migration to and from your SaaS service?
Yes, we plan to continue offering the cloud for those who don't want to deploy their own solution.
> As for building a community, definitely make a Discord and a forum where people can come together and get help publicly, figure out how to get a stackoverflow space for it as well.
We're thinking about Discord right now, even started one. That is an interesting idea about Stackoverflow, thank you we'll think about it!
> it's starting to sound more like a grieving process
Why? No grieving. Many products in the world are not growing as fast as their creators would like – it is OK. We just try new things and see what happens. Like what if you put all the code on the net :-)
> Your other comments sound dispassionate about your product.
I really like what we've been able to create. I want more people to use it.
> You said you arent interested in slowly growing a business
I want more users. If the price is that many of them won't pay because it's open source, then that's the price.
> Im sure your integration partners say they would like your project to be open source but they arent going to be doing ANY of the work.
We have a very well-isolated back end (F#) and front end. I don't think integrators will be able to write in F#, but hopefully, they will be happy to refine the front end in Vue.
You can deploy it to Heroku with just one click.
The bot handles text, voice, and photo messages, converting them to text for processing via OpenAI's ChatGPT.
It also uses PostgreSQL for data storage and optionally integrates with Pinecone for long-term memory.
The repository includes Docker and Docker Compose support for easy deployment.
Feel free to check it out, and let me know your thoughts!