This looks really cool, but not being able to use my own LLM endpoints for the Copilot is an instant turn-off.
Show HN: Sim – Apache-2.0 n8n alternative
41–50 of 63 posts
Re: Show HN: Sim – Apache-2.0 n8n alternative
#42Open Sourced until we get rug pulled..
Re: Show HN: Sim – Apache-2.0 n8n alternative
#43Open Sourced until we get rug pulled..
Everything that’s available today in our repo will be Apache 2.0 forever, so you don’t have to worry about that :)
Re: Show HN: Sim – Apache-2.0 n8n alternative
#44This looks really cool, but not being able to use my own LLM endpoints for the Copilot is an instant turn-off.
You actually can, if you self-host there are environment variables to control what models are available to the copilot but it’s tuned to Azure for the time being. We can work on generalizing it further and documenting it better
Re: Show HN: Sim – Apache-2.0 n8n alternative
#45This looks really cool for DIYing workflows, especially since you seem to have a very useful selection of tools! Did you build your own agent engine? Why not LangGraph? Say I was building a general agentic chat app with LangGraph in the backend (as it seems to provide a lot of infrastructure for highly reliable and interactive agents, all the way up to a protocol usable by UIs, plus a decent ecosystem, making it very…
Their deployment stuff has been turning me off lately; everyone is rushing to monetize - which I understand and support - but I feel like Langsmith is creeping further and further into Langchain|graph and it makes me hesitant to invest. It’s giving AWS-like gentle but firm lock-in vibes, I wonder if they have any PMs from there. I do like the way they’ve been able to leverage Langgraph workflows to build agents - it…
I’m only in the research phase of my hypothetical project so far, so I’m going more off of vibes than personal experience for now.
I’m interested in LangGraph because it seems the closest to an industry standard - every use case seems to be addressed with a tutorial (both first and third party) and there’s an ecosystem of already available graphs/agents. I’m aiming for both high extensibility (new use cases should be easily implementable) and high reliability. The LangGraph docs do a pretty good job at convincing me that they got the latter pretty nailed down. It seems like a hard enough problem to question a new solution on this.
I want to build a (highly reliable & controllable) UI for agents more than I want to build the agents themselves, so my hope is that LangGraph has the biggest ecosystem I can plug into.
They do have some funky lock-in attempts, for instance the LangGraph CLI, which acts as a server for their agent protocol (https://github.com/langchain-ai/agent-protocol), is proprietary. However (and this is what I consider indicative of a strong ecosystem) there’s a free reimplementation named Aegra: https://www.aegra.dev/
Re: Show HN: Sim – Apache-2.0 n8n alternative
#46This looks really cool, but not being able to use my own LLM endpoints for the Copilot is an instant turn-off.
You actually can, if you self-host there are environment variables to control what models are available to the copilot but it’s tuned to Azure for the time being. We can work on generalizing it further and documenting it better
Azure is just fine, as long as it's documented someplace. I'll take a look, although I also couldn't find prebuilt Docker images referenced in the compose.local file (I will look into what is being built into ghcr.io)
Re: Show HN: Sim – Apache-2.0 n8n alternative
#47How does this compare to say, Node Red?
Node-Red is the original.
N8n and its clones are attempts to copy and commercialize it with a closed-source license.
Re: Show HN: Sim – Apache-2.0 n8n alternative
#48Re: Show HN: Sim – Apache-2.0 n8n alternative
#49for the workflow DAG, what type of backend are you guys using? is it like temporal or self-built durable workflows