Putting Redis behind a paywall it's a foul behavior, it's essential to a lot of Laravel projects, it's like blocking mysql if you don't pay!!! Also forcing me to update or i can't work on my projects? another one that bites the dust.
Also this release it's sloppy, it made my mac work slower, indigo itself its slower, it takes longer to start and shutdown compared to the beta.
Hi @bsfxav — thanks for sharing your feedback—it’s helpful to hear all perspectives.
Choosing which services to include in Pro was a difficult decision and I understand the Basic edition may not align with everyone’s specific needs. Redis is essential for many, but we expect these users will largely be the professional users for whom Pro is intended. Our Pro version is designed to support the ongoing development of Indigo, especially for users relying on it in a work setting. If you’re using Indigo professionally, Pro ensures access to all the available services to keep your workflows running smoothly.
Regarding forced updates, all the recent release candidates have had a four month expiry built in, since the exact v1.0.0 release date was not yet determined.
As for the performance change you describe, that's very odd! I haven’t noticed any slowdown myself nor received any other reports of slowdown, and no recent code changes have been made that should impact speed. It's quite a mystery. I’d be happy to help troubleshoot with you—please let me know a bit more about your setup, and we’ll work together to find out what might be happening. Also of course, if anyone else has perceived a slowdown in the recent releases, please chime in.
Thank you again for your feedback, and please feel free to reach out with any additional concerns!
What's perhaps more questionable than putting certain services behind a paywall - which I can understand - is the pricing. Indigo is almost €20 more expensive per year than phpStorm (€59/yr).
I had hoped this would be reasonably priced, but there is no world in which $84/yr for something that does little more than allow you to skip the Homebrew commands for installing the services, is a reasonable value.
The only other difference between Indigo and Homebrew-installed Nginx/PHP/MySQL/Redis is that Homebrew services are always running in the background, whereas with Indigo, they shut down when the app shuts down.
But with the M-series chips being as good as they are and the relatively few resources those services take, that's not a huge concern.
Add that to the fact that Indigo doesn't have a framework for us to be able to add custom services, such as Imagick or ElasticSearch, I'm sure you can understand my complete bafflement at the current price.
That being said, I also understand it's better to sell one license at $84 than 10 licenses at $8.40 since one customer requires less support than 10 customers. That one customer is just not going to be me.
Edited to add: To compare Indigo pricing to some of the other tools I use, in order of cost (lowest-highest):
As you can see, Indigo would be the third most expensive tool I pay for, and in my opinion, the value added by literally all of the tools on this list is much greater than the value added by Indigo.
You can't even say that using Indigo to manage your Nginx server is that much easier than using the Homebrew version, because of how much you need to muck about with the template files to get URL rewrites working for new sub-folders of your document root.
Tower, the Git management tool, does not require you to randomly dig into Git config files to manage literally any part of the commit & push experience to any given repository.
I would love to support Indigo and its development going forward, but this pricing is not in line with reality.
Second edit: Randomly when refreshing the pricing page, the price changed from €89 to $84, so I've edited the post to reflect this, as well as reworded certain other parts.
Hi @nullart — drop me a line at support@indigostack.app.
Powered by: FreeFlarum.
(remove this footer)
