Since you're looking for feedback...
The "New Way" section would benefit from simplifying into a single flow chart with just two steps. Then move the existing 4 blocks to a features section.
Also would be great to have simple use cases on the landing page and link to the current Use Cases page for details. On the Use Cases page, I would get rid of the graphics. They don't convey much info and distract from the screenshots.
Maybe add a page for product comparisons. Without playing with the product first, it's a bit unclear to me how my no-code teams would prefer Fleak over their current tools (Make.com, n8n, Pabbly, Zapier, etc.).
The pricing page is somewhat of a deal breaker for my team to even spend time testing the product. The only option (free tier) seems to have really limits like 1 request / sec. And there's not enough info to understand how max events and other rate limits play together. I would keep the 1 user, 5 pipeline, token limits, and 500 requests (pipeline executions?) per month. Then remove the other limits. Alternatively, offer a Pro tier with a free month trial with higher limits.
Also on the pricing page, it would be great to list out a few use cases as examples of what's possible within the limits of each tier.
Hope this helps! And best of luck. It looks like a promising product.
If a manufacturer could provide a one-stop service, including easy-to-understand documentation, tutorials or demo videos aimed at beginners, at a reasonable price, while ensuring the reliability of the service, I would be very willing to pay for their products. I hope Fleak could consider the needs of users like us, to further optimize the product and services, making it easier for more individual developers to get started with Fleak.
Looking forward to future improvements and updates from Fleak, and continuing my support for you guys!
Ideally I'd love to be able to run arbitrary Python code in a node together with custom pip scripts to install the libraries I care about. We do some image processing steps and looks like this is not something you support.
The bias here is clearly towards text processing but I think more and more companies like this one should start thinking about multimodal pipelines.
One last point, I did not get far enough in my tests to see if I can publish a public API point secured by an API key. That's absolutely a must as having to mess around with a gateway myself to access this would nullify most of the benefits of this platform.
Who is your target user?
I full-on laughed out loud reading your landing page for the "old way"/"new way" comparison.
It reads, to me, like "old way: easy to follow, if cumbersome, flowchart", "new way: 4 separate abstract drawings that are actually impossible to follow and do not imply any specific process is occurring."
Obviously, I'm probably in the minority here. Just some food for thought, if you're interested in that kind of thing.