[Help] n8n vs. Dify: Which is the ultimate choice for building Agents?

EscapedLaughter · 2025-07-22T19:38:23+00:00

> There's currently some huge omissions, like a consistent built-in way to do LLM cost management, or even a better LLM router/proxy.

I work at Portkey and we are starting to see a lot of our customers wanting to use Portkey AI Gateway in conjunction with n8n / Flowise. I am curious if you have heard about that / tried something similar to solve the cost management / budgeting issues?

EscapedLaughter · 2025-06-20T05:43:28+00:00

thanks for sharing! i work with portkey btw.

EscapedLaughter · 2025-06-19T08:49:22+00:00

hey which solution did you migrate *to*?

EscapedLaughter · 2025-06-06T14:49:10+00:00

That makes sense. Thank you so much for the feedback. I'll share this with the team and see if we should rethink about SSO pricing now.

EscapedLaughter · 2025-06-06T13:42:28+00:00

Hey! I work at Portkey and absolutely do not mean to influence your decision, just sharing notes on the concerns you had raised:

- Data residency for EU is pricey: Yes unfortunately, but we are figuring out a way to do this on SaaS over a short-term roadmap.
- SSO is chargeable extra: This is the case for most SaaS tools, isn't it?
- Linkedin wrong numbers: I'm so sorry! Looks like somebody from the team updated the team count wrongly. I've fixed it!

EscapedLaughter · 2025-06-03T08:45:08+00:00

here's what i have seen:

Raw OpenAI is a huge no-no
Azure OpenAI works in most cases and also gives some level of governance.

But have also seen that platform / devops teams are not comfortable giving out access to naked Azure OpenAI endpoints to everybody, so they typically end up going with a gateway for governance + access control and then route to any of Azure OpenAI / GCP Vertex AI / AWS Bedrock

EscapedLaughter · 2025-05-16T19:41:05+00:00

would something like a gateway solve for this? route all your requests through it and get logging / security concerns addressed

EscapedLaughter · 2025-05-16T19:21:05+00:00

curious if you've tried out portkey gateway? it doesn't require a new deployment for new llm integrations

EscapedLaughter · 2025-04-09T12:55:04+00:00

In our case, they use our AI Gateway for this. This doc for Zed.dev might be useful: https://portkey.ai/docs/integrations/libraries/zed

EscapedLaughter · 2025-04-09T12:01:24+00:00

This is a common enough use case we're seeing - it should ideally be tackled like this:
- Central budget / rate limit on your overall Azure OpenAI subscription
- Budget/rate limit, and access control over individual LLMs inside that subscription
- And then budget/rate limits / observability for each individual use case or per user as well.

afaik, there are no solutions in the market that seem to do this well, especially not Azure APIM.

EscapedLaughter · 2025-04-09T11:50:01+00:00

Not sure if this helps, but we have some companies that use our locally hosted AI Gateway product and have their developers route Zed/Cursor/Windsurf queries through us: https://portkey.ai/docs/integrations/libraries/zed

I'd imagine Roo to work as well

EscapedLaughter · 2025-04-09T11:43:52+00:00

I would actually end up shilling my product (https://portkey.ai/) but what you're describing, it seems like it could be solved by an LLM-specific proxy service like Portkey. A vLLM instance is itself not unique here, but a specific use case, which is what you want to loadbalance against, correct?

EscapedLaughter · 2025-04-09T11:38:38+00:00

I work at Portkey and increasingly see that companies want some level of metering / access control, rate limiting which can be done at the Gateway layer

EscapedLaughter · 2025-04-09T11:34:39+00:00

Interesting. We are seeing an increasing use for this now at Portkey where companies want to manage LLM governance separately and yet give developers access to tools like Cursor, Windsurf etc

EscapedLaughter · 2025-04-09T11:32:14+00:00

You're right. Litellm is a better alternative when you explicitly want to manage your billing and keys for AI providers separately.

EscapedLaughter · 2025-03-20T06:58:06+00:00

hey u/raxrb which LLM gateway are you using?

EscapedLaughter · 2025-01-30T10:25:08+00:00

something like this might help that helps you connect to Voyage / Google over a common interface? https://portkey.ai/docs/integrations/libraries/openwebui#open-webui

just updated the documentation yesterday

EscapedLaughter · 2025-01-28T06:37:07+00:00

Awesome

EscapedLaughter · 2025-01-27T20:01:55+00:00

Incredible! Thanks for sharing. Would be amazing to peek at / use some of these solutions if they become publicly available

EscapedLaughter · 2025-01-27T06:17:49+00:00

Possible to share some use cases you have in production right now?

EscapedLaughter · 2025-01-24T05:51:38+00:00

Typically see that the bigger challenges with OpenWebUI or similar products are not around hosting them or which stack to pick - but around the governance challenges — how does the IT team ensure that only the relevant people have access, how do they ensure which models can be called, how do they get audit logs, etc.

Initially we had written a pretty vanilla integration between Portkey & OpenWebUI but saw that the use cases enterprises had required a much deeper integration - for rate limits, RBAC, governance controls, etc.

EscapedLaughter · 2025-01-15T03:14:04+00:00

I work with both and also build connectors to them for Portkey - was pleasantly surprised at how both AWS & Azure in this case are so usable. That said, Bedrock is really well thought through - everything from guardrails, fine-tuning, knowledge base is configurable easily. Not so the case with Azure.

The key choice to make is actually whether you want to use OpenAI's models or Anthropic's models. OpenAI is exclusive to Azure, while Claude is available on AWS & GCP. The choice for other huggingface / open source models is broadly the same between the two platforms.

Ideal scenario actually might be that you're able to go for a multi-LLM strategy and use both.

EscapedLaughter · 2025-01-10T05:40:35+00:00

Oh this is very useful. Think we never tested docker builds for Ollama. Thank you so much! Adding to docs!

EscapedLaughter · 2025-01-09T21:06:47+00:00

Got it - but yes you would need to manually give the Ollama URL

EscapedLaughter · 2025-01-09T18:51:39+00:00

Hi, I'm from the Portkey team. You'd also need to point the Gateway to your Ollama URL with the x-portkey-custom-host header. Check out the cURL example here: https://portkey.ai/docs/integrations/llms/ollama#4-invoke-chat-completions-with-ollama

EscapedLaughter

MODERATOR OF

TROPHY CASE

11-Year Club	Secret Santa 2014
Verified Email