https://www.activepieces.com | https://github.com/activepieces/activepieces
Show HN: Sim – Apache-2.0 n8n alternative
51–60 of 63 posts
Re: Show HN: Sim – Apache-2.0 n8n alternative
#52Development seems pretty rapid, how often are breaking changes forcing workflow modifications to keep updated with the latest versions?
We keep all workflows running on Sim cloud backwards compatible always. The idea is that you build, deploy, and never have to make modifications again unless you want to. If we release a breaking change that requires a migration for existing local workflows, we release notice at least a few weeks ahead of time/bake it into the db migrations. Incase there are significant changes made, everything is versioned so you op…
Re: Show HN: Sim – Apache-2.0 n8n alternative
#53Re: Show HN: Sim – Apache-2.0 n8n alternative
#54Earlier quoted context omitted.
We keep all workflows running on Sim cloud backwards compatible always. The idea is that you build, deploy, and never have to make modifications again unless you want to. If we release a breaking change that requires a migration for existing local workflows, we release notice at least a few weeks ahead of time/bake it into the db migrations. Incase there are significant changes made, everything is versioned so you op…
Thanks, and that sounds great. On the backend what are you using for the DAG stuff to make it durable? Temporal?
Re: Show HN: Sim – Apache-2.0 n8n alternative
#55Re: Show HN: Sim – Apache-2.0 n8n alternative
#56Earlier quoted context omitted.
Node-RED is great for IoT/edge/data flows. Sim is built specifically for AI agents—native LLM support, tool-use control, structured outputs, token-level observability, etc.
There is nothing in Node-Red that is specific to IoT.
Re: Show HN: Sim – Apache-2.0 n8n alternative
#57Earlier quoted context omitted.
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)
since the copilot is a managed service, you’d be setting those azure credentials in your .env and the copilot would call into your azure openai deployment.
Re: Show HN: Sim – Apache-2.0 n8n alternative
#58This is amazing! Thank you all for building this!
Re: Show HN: Sim – Apache-2.0 n8n alternative
#59for the workflow DAG, what type of backend are you guys using? is it like temporal or self-built durable workflows
Re: Show HN: Sim – Apache-2.0 n8n alternative
#60Earlier quoted context omitted.
There is nothing in Node-Red that is specific to IoT.
afaik, there are actually a ton of unique IoT integrations that node-red has. a majority of their nodes/flows have accompanying physical devices and sensors
The only weird integration that Node-Red has is MQTT, but that isn't really anything IoT-specific, just a niche message broker.