Product Thumbnail

Sim

Open-source workspace for AI agents and workflows

Open Source
Developer Tools
Artificial Intelligence
Visit WebsiteSee on Product HuntGithubTwitter

Hunted byGarry TanGarry Tan

Sim is an open-source workspace to build agentic workflows. Connect your AI agents and workflows to 1,000+ integrations and LLMs.

Top comment

👋 Hey Product Hunt! I'm Emir, co-founder and CEO of Sim. Today Sim is open to everyone, and I couldn't be more excited to share it ❤️ Sim started with a mess of our own making. Waleed (my best friend and co-founder) and I were prompting Claude to build sophisticated automations in n8n, storing data in Supabase, and standing up infra for our APIs and MCPs, and we realized the stack we'd assembled just to build agents that automated our own work was a complete mess. Not to mention our token spend... So we set out to build the one platform we wished we had. The problem: building AI agents today means stitching together frameworks, one-off scripts, and brittle automations that break the moment anything changes. We wanted one place to build an agent, give it access to our data across 1,000+ integrations, build a brain for memory, deploy it, and actually manage it over time. So we built one. Sim is the open-source AI workspace for agents. Here's what makes it different: 🗣️ Build by chatting — describe what you want and Sim builds the agent and workflow for you. Or design it visually on a canvas. Or drop into code. Whatever fits the job. 🔌 1,000+ integrations + every major LLM — Slack, Notion, HubSpot, Salesforce, Gmail, and more, connected out of the box. Your agent says "message me on Slack when a deal closes" and it just works. 🧠 One workspace, shared context — Workflows, Tables, Knowledge Bases, and Files all live together, so your agents share memory and data instead of living in disconnected tools. 💸 Cost-efficient by design — Sim swaps token-hungry tool calls for deterministic steps and real code wherever it counts, so you're not burning tokens (and money) on work that never needed an LLM in the first place. 🚀 Built for real work — Slack bots, compliance agents, data pipelines, research assistants. Not demos, actual production agents. 🔓 Open source (Apache 2.0), SOC2, and already trusted by 100,000+ builders. Who it's for: teams who want to put AI agents to work (IT, ops, and technical teams who need governance and control), and individual builders who care about speed and open source. We're shipping fast and want to build this with you. Tell us what's missing, what's broken, and what would make Sim 10x more useful for you. Try it -> sim.ai I'll be here all day and will read and reply to every single comment 🙌

Comment highlights

the "deterministic steps wherever it counts" line caught me because that's the exact thing I ended up hand-coding after my n8n token bill got stupid. how does Sim decide what becomes real code vs an LLM call, is that automatic when you build by chatting or do I have to go mark steps myself? because if the chat builder defaults everything to LLM calls the cost problem just comes back quietly

Emir, congrats on the launch. That live integrations counter ticking past 1000 is such a nice touch, makes the scale feel real. Upvoted!

As workflows grow over time, keeping everything organized usually become hard than building the first version. Wht helped your team keep large workflows easy to understand and maintain as more agents, integrations and triggers were added?

Kind of interesting that 90%+ of usage moved to chat when the product started out canvas-only. Usually builder tools go the other way, people start with prompts then graduate to manual/visual control once they need precision. Makes me think their user base skews more solo-builder/ops than engineer.

With 1,000+ integrations wired in, how predictable is token spend once an agent starts chaining calls across three or four of them in one workflow?

This is really amazing. So do you have templates for the workflows?
How is it different to N8N or Zapier?

The shared context/workspace part is what I'd stress-test first. In agent workflows I've seen the brittle bit is less the prompt and more schema or credential drift across Slack/Notion/Supabase. Curious how you debug/version a workflow when one of the 1,000+ integrations changes?

@emirkarabeg The per-node flexibility between chat, canvas, and code is what other tools get wrong. Curious, which mode do most of your users end up living in?

The shared memory across agents in the same workspace is cool 👍 can you also set boundaries so certain agents only access certain data, or is it all-or-nothing?

For someone who's already deep into LangGraph or CrewAI, is there an import path, or would they basically be starting from scratch rebuilding their agents in Sim?

What's on the roadmap that you're most excited about but can't talk about yet? 👀

@emirkarabeg The per-node flexibility between chat, canvas, and code is what other tools get wrong. Curious, which mode do most of your users end up living in?

1,000+ integrations is a lot to keep working. Are those maintained in house or community contributed?

Congrats Emir! Your origin story is literally my job description. I prompt Claude to build automations for a 40-person company and the stack sprawl is real, so one workspace with shared context is the right pitch. My question: since 90% of usage is now chat-built, what happens when an agent needs to do something risky like sending a Slack message or an email? Can I set approval gates on specific nodes so a human signs off before it fires? That’s the line between a demo and something I’d let loose on production.

Congrats Emir!
Most agent builders just throw LLM calls at everything and the bill quietly becomes a problem at scale. How does Sim decide which steps get deterministic code versus an LLM call, is that the builder's call or does Sim suggest it

Apache 2.0 and soc2 out of the gate is a wild combination for a new open source agent project. usually security teams block this stuff instantly. congrats for launch @emirkarabeg 🙌 qq can i run the entire stack locally via docker-compose and still keep the visual canvas working?

About Sim on Product Hunt

Open-source workspace for AI agents and workflows

Sim launched on Product Hunt on July 10th, 2026 and earned 637 upvotes and 109 comments, earning #2 Product of the Day. Sim is an open-source workspace to build agentic workflows. Connect your AI agents and workflows to 1,000+ integrations and LLMs.

Sim was featured in Open Source (68.6k followers), Developer Tools (515.9k followers) and Artificial Intelligence (473.7k followers) on Product Hunt. Together, these topics include over 196.6k products, making this a competitive space to launch in.

Who hunted Sim?

Sim was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

Reviews

Sim has received 4 reviews on Product Hunt with an average rating of 4.75/5. Read all reviews on Product Hunt.

Want to see how Sim stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.