21–30 of 38 posts
This looks useful for no-code team members to create embeddings for LLM. 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…
What is an AI workflow? What does "embed API endpoint" mean? What is a concrete example of something I would use it for? Why would I use it as opposed to other solutions?
I'm having similar issues understanding how I might use this.
The “Docs” link goes back to the homepage. I found it hard to tell what exactly this does - how can serverless reduce overhead (usually it’s the other way around), how does it scale the LLM backend and so on.
Kind of useful but I'd generally point people to AWS StepFunctions which is a strict superset of this product (assuming they are ok with using AWS)
Isn't Langflow the better tool for LLMs?
Earlier quoted context omitted.
I'm having similar issues understanding how I might use this.
you may think of it as a cloud function, we mostly focus on HTTP based data ingestions without a storage layers. e.g. Your app is sending some data, Fleak can be used to create an API to process that data then return back to the app synchronously or save the processed data directly into a storage layer.
What would really help would be a concrete business case for when someone would use this and how it helps vs other options
> Does this sound useful to you? Who is your target user?
Isn't Langflow the better tool for LLMs?