Waleed 0cc290eeb7 feat(comparison): add Microsoft Copilot Studio, OpenClaw, Dust, CrewAI, and LangChain (#5384)
* feat(comparison): add Microsoft Copilot Studio, OpenClaw, Dust, CrewAI, and LangChain

- 5 new "Sim vs Competitor" profiles (now 20 total), each with ~58
  independently sourced facts, standout features, and limitations,
  researched against each vendor's own docs/pricing/GitHub
- New brand icons: MicrosoftCopilotIcon, OpenClawIcon, DustIcon,
  LangChainIcon, CrewAIIcon
- isWorkflowBuilder: false for OpenClaw, CrewAI, and LangChain since
  they're a personal agent runtime and code-first frameworks rather
  than visual workflow builders, so their FAQ asks a
  category-clarifying question instead of a peer feature-gap one
- Independent tone audit (no over-praising competitors, no unflattering
  Sim framing) and a fresh accuracy re-verification pass (50 highest-
  stakes facts across all 5 profiles, all confirmed against live
  sources) both came back clean

* fix(comparison): fix two more FAQ text-mangling bugs found during final audit

- lowercaseFirst only guarded against 2+ CONSECUTIVE leading capitals
  (acronyms like "AI"/"SSO"), so CamelCase brand names with a single
  leading capital (LangChain, OpenClaw, CrewAI) got their first letter
  wrongly lowercased ("langChain provides..."). Now checks for 2+
  uppercase letters anywhere in the leading word, which covers both
  acronyms and CamelCase brand names.
- parseFactValue and summarizeFact's boolean-prefix stripping only
  recognized "Yes:"/"No:" (colon), but "Yes, ..."/"No, ..." (comma) is
  an equally common phrasing already used across ~15 existing facts
  (stackai, pipedream, workato, zapier, etc.), so those facts kept
  their leading comma when stitched into an FAQ answer (e.g. "StackAI:
  , broad support..."). Both now accept either separator.

Found by systematically sweeping every "Sim vs X" FAQ answer across
all 20 competitor pages for garbled/mis-cased text, not just the 5
newly added ones.

* feat(comparison): add sub-workflow composition and loop-block facts

- Two new universal comparison facts across all 20 profiles:
  subWorkflows (calling a saved workflow as a reusable step inside
  another) and loopIteration (a dedicated sequential for-each/while
  loop container, distinct from concurrent Parallel execution)
- Both are real Sim capabilities (Workflow block, Loop block) verified
  directly against the codebase and docs.sim.ai
- Findings are genuinely mixed, not uniformly favorable: n8n, Zapier,
  Make, Workato, Retool, Power Automate, Gumloop, Vellum, Stack AI,
  Tines, Langflow, Flowise, Microsoft Copilot Studio, and LangChain all
  have some form of sub-workflow calling; Zapier and Gumloop's loop
  primitives run concurrently rather than sequentially (marked
  "Partial", not "No"); Pipedream, OpenAI AgentKit, Claude Cowork,
  CrewAI, Dust, and OpenClaw genuinely lack one or both

* feat(comparison): add third-party integration vetting fact

New universal comparison fact across all 20 profiles: thirdPartyVetting,
whether a platform's integrations/tools/skills come from a vetted
first-party catalog vs. an open marketplace where any third party can
publish executable code with lighter or no vendor security review.

Directly relevant given OpenClaw's ClawHub marketplace has documented
incidents (283 skills, ~7.1% of the registry, found leaking credentials;
24 accounts distributing 600+ malicious skills before scanning existed).

Findings are honest and mixed, not uniformly favorable: Gumloop, Retool,
and Tines are first-party-only like Sim (marked "Yes"); n8n, Zapier,
Make, Workato, and OpenAI AgentKit have partial vetting on an open or
semi-open ecosystem; Pipedream and OpenClaw are open marketplaces with
documented security incidents.

* fix(comparison): correct n8n supply-chain attack download count

Independently re-verified the cited Hacker News article: the primary
malicious package had 4,241 downloads listed (not "3,400 weekly" as
previously written, a number not actually supported by the source).

* fix(comparison): fix duplicated competitor name in first FAQ answer

Every competitor's oneLiner is already a complete "{Name} is ..."
sentence, so prepending "${name} is " before it was always redundant.
Before this session's lowercaseFirst fix, the duplication rendered in
mixed case ("Zapier is zapier is a cloud-based...") and was easy to
miss; the CamelCase-name fix made it fully literal and obvious
("CrewAI is CrewAI is..."), which is what Cursor Bugbot caught.

Fixed by using the oneLiner directly (via ensurePeriod) instead of
re-prepending the name. Verified fixed across all 20 pages via live
curl, not just the CrewAI case Cursor flagged.

* improvement(comparison): cite Sim's own docs alongside code for 4 facts

Added docs.sim.ai citations (Roles and Permissions, BYOK, Debugging
retrieval, Function block) as primary sources for rbac, byok,
kbChunkVisibility, and customCodeSteps, which previously cited only
GitHub source code with no user-facing documentation reference.
Verified all 4 doc URLs resolve (200).
2026-07-03 11:29:13 -07:00

Sim.ai Documentation Discord X

Ask DeepWiki Set Up with Cursor

Sim — Integrate, Context, Build, and Monitor AI agents

A workspace to build, deploy and manage AI agents and workflows.

Quickstart

Cloud-hosted: sim.ai

Open sim.ai

Self-hosted

npx simstudio

Open http://localhost:3000

Docker must be installed and running. Use -p, --port <port> to run Sim on a different port, or --no-pull to skip pulling the latest Docker images.

The Sim platform — chat on the left, the visual workflow builder on the right

Capabilities

  • Connect 1,000+ integrations and every major LLM
  • Add Slack, Notion, HubSpot, Salesforce, databases, and more
  • Build agents visually, conversationally, or with code
  • Ingest files, knowledge bases, and structured table data
  • Monitor runs, logs, schedules, and workflow activity

One workspace, every surface

Chat and workflows are just the start — tables, files, knowledge, and scheduled tasks all live in the same workspace.

Tables in Sim — structured data your agents can query

Tables — a database, built in

Files in Sim — documents for your team and every agent

Files — one store for your team and every agent

Knowledge bases in Sim — synced docs your agents can search

Knowledge — your agents' memory

Scheduled tasks in Sim — recurring agent runs on a calendar

Scheduled tasks — runs on your schedule

Self-hosting

Docker Compose

git clone https://github.com/simstudioai/sim.git && cd sim
docker compose -f docker-compose.prod.yml up -d

Open http://localhost:3000

Sim also supports local models via Ollama and vLLM. See the Docker self-hosting docs for setup details.

Manual Setup

Requirements: Bun, Node.js v20+, PostgreSQL 12+ with pgvector

  1. Clone and install:
git clone https://github.com/simstudioai/sim.git
cd sim
bun install
bun run prepare  # Set up pre-commit hooks
  1. Set up PostgreSQL with pgvector:
docker run --name simstudio-db -e POSTGRES_PASSWORD=your_password -e POSTGRES_DB=simstudio -p 5432:5432 -d pgvector/pgvector:pg17

Or install manually via the pgvector guide.

  1. Configure environment:
cp apps/sim/.env.example apps/sim/.env
# Create your secrets
perl -i -pe "s/your_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
perl -i -pe "s/your_internal_api_secret/$(openssl rand -hex 32)/" apps/sim/.env
perl -i -pe "s/your_api_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
# DB configs for migration
cp packages/db/.env.example packages/db/.env
# Edit both .env files to set DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
  1. Run migrations:
cd packages/db && bun run db:migrate
  1. Start development servers:
bun run dev:full  # Starts Next.js app and realtime socket server

Or run separately: bun run dev (Next.js) and cd apps/sim && bun run dev:sockets (realtime).

Chat API Keys

Chat is a Sim-managed service. To use Chat on a self-hosted instance:

  • Go to https://sim.ai → Settings → Chat keys and generate a Chat API key
  • Set COPILOT_API_KEY environment variable in your self-hosted apps/sim/.env file to that value

Environment Variables

See the environment variables reference for the full list, or apps/sim/.env.example for defaults.

Tech Stack

Next.js · Bun · PostgreSQL · Drizzle · Better Auth · Tailwind — and the rest of the stack

Contributing

We welcome contributions! Please see our Contributing Guide for details.

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Built by the Sim team in San Francisco

Languages
TypeScript 77%
MDX 20.8%
JavaScript 1.9%
CSS 0.1%