waleedlatif1

7 ms·

1.
SIM (YC X25) Is Hiring the Best Engineers in San Francisco(ycombinator.com)
1 points by waleedlatif1 7mo ago
2.
by waleedlatif1 10mo ago
1) functionally, not that I'm aware of. the only thing right now is running from a specific block onwards, something that we are rolling out this week. you'll be able to run the workflow in debug mode and get really granular infor
3.
by waleedlatif1 10mo ago
we built an execution engine ourselves https://github.com/simstudioai/sim/tree/main/apps/sim/execut... and for the infra for background jobs, we use https://trigger.dev/
4.
by waleedlatif1 10mo ago
thank you! hope you enjoy
5.
by waleedlatif1 10mo ago
the prebuilt images are in compose.prod file only, not in compose.local. 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.
6.
by waleedlatif1 10mo ago
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
7.
by waleedlatif1 10mo ago
coming soon
8.
by waleedlatif1 10mo ago
We actually wrote our own serializer & execution engine and for long-running jobs, we defer to trigger.dev
9.
by waleedlatif1 10mo ago
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
10.
by waleedlatif1 10mo ago
Everything that’s available today in our repo will be Apache 2.0 forever, so you don’t have to worry about that :)
11.
by waleedlatif1 10mo ago
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 existin
12.
by waleedlatif1 10mo ago
hope you enjoy :)
13.
by waleedlatif1 10mo ago
sounds super cool! let me know how it goes
14.
by waleedlatif1 10mo ago
Copilot and a few modules are sim.ai-only, but self-hosters can access them with an API key. The core—execution engine, all integrations, deployment—is fully Apache 2.0. We aimed for feature parity with n8n and improved much of the workflow
15.
by waleedlatif1 10mo ago
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.
16.
by waleedlatif1 10mo ago
1. we wanted to have full control over the agent orchestration and the execution since we didn't like the abstractions that many of the existing frameworks had built, and didn't want to have dependencies in places we didn't n
17.
by waleedlatif1 10mo ago
the agents would be great in the instructions where we need to `do something`, but asides from that is sounds like a pure orchestration task. now, handling an integration to something like google sheets myself for a task this small is a nig
18.
by waleedlatif1 10mo ago
this is actually a perfect use case, mostly deterministic workflows that need LLMs to fill in the gaps or do the knowledge work. As you mentioned, you can either add it as a row in a CSV file (sheets), use the baked-in memory block and trea
19.
by waleedlatif1 10mo ago
its a conservative estimate, but primarily because there's a socket server that runs alongside the main container, so you never have to manually save because changes are debounced, broadcasted to any other users on the canvas, and sent
20.
by waleedlatif1 10mo ago
n8n uses a "Sustainable Use License"—source available, but not OSI-approved open source. This means you can only use it for internal business purposes or non-commercial use. Sim is Apache 2.0.
21.
by waleedlatif1 10mo ago
thanks for the feedback, I was actually thinking this the other day. we'll slow them down.
22.
by waleedlatif1 10mo ago
at the moment, we don't support 'loops in loops' on the client-side, but not for any other reason asides from it becoming confusing for users. since we don't actually make copies for each loop, it wouldn't be a perf
23.
by waleedlatif1 10mo ago
for loops we use two sentinel nodes with a backwards edge, and before each iteration, we check the condition and update loop variables. sentinel -> body -> sentinel (condition with backwards edge to first sentinel) in the UI, t
24.
by waleedlatif1 10mo ago
i believe it stands for “nodemation”
25.
Show HN: Sim – Apache-2.0 n8n alternative(github.com)
240 points by waleedlatif1 10mo ago|61 comments
26.
by waleedlatif1 1y ago
imo, model regression might actually stem from more aggressive use of toolformer-style prompting, or even RLHF tuning optimizing for obedience over initiative. i bet if you ran comparable tasks across 3-5, 3-7, and 4-0 with consistent promp
27.
by waleedlatif1 1y ago
I really hope sonnet 4 is not obsessed with tool calls the way 3-7 is. 3-5 was sort of this magical experience where, for the first time, I felt the sense that models were going to master programming. It’s kind of been downhill from there.
28.
by waleedlatif1 1y ago
thank you! appreciate the kind words
29.
by waleedlatif1 1y ago
adding some examples and templates this week, and in our discord we are gonna maintain a showcase where ppl can post the cool workflows they've built.
30.
by waleedlatif1 1y ago
appreciate it! 1) we are completely open source and you can self-host it if you so please. for the hosted platform, we have a free tier to let you tinker and get some free inference credits, and then we have a pro plan with is $20 worth of

More ›