lobehub vs sim
LobeChat's 80k-star pivot: from chat UI to 'Chief Agent Operator' — hire, schedule and supervise a team of agents running 7×24, self-hosted via Docker or Vercel, plugin ecosystem carried over. — versus — Visual workspace to build, deploy and orchestrate AI agents — 1,000+ integrations, knowledge bases, built-in tables and files, schedules and run monitoring. Self-host via npx simstudio or Docker.
Both are visual workspaces for running agent operations: Sim leans on workflow building — 1,000+ integrations and knowledge bases; LobeHub leans on the team metaphor — agents as staff you hire, schedule and get reports from.
| lobehub | sim | |
|---|---|---|
| Stars | 81k | 29k |
| Forks | 16k | 3.7k |
| Language | TypeScript | TypeScript |
| License | NOASSERTION | Apache-2.0 |
| Last activity | today | yesterday |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 2 | 3 |
lobehub — the curator's take
One of the biggest chat-UI codebases reinventing itself as an agent-team operator — hire, schedule, report, stay in charge without staying online. Read the star count correctly: 80k stars measure the LobeChat era, not the operator bet, which is weeks old and under active rebuild — evaluate those features on their own merits. What carries over is real: mature self-hosting (Docker/Vercel/Zeabur), a large plugin ecosystem, and an unusually strong design culture. GitHub reports no standard license (custom terms) — read them before commercial deployment; this is not plain MIT anymore. When NOT: if you need a proven production agent runtime today, the harness layer is further along than the operator layer.
sim — the curator's take
The n8n-for-agents play at real scale (29k stars): build agents visually, conversationally, or in code, wire them to Slack/Notion/Salesforce-class integrations, and keep tables, files, knowledge bases and scheduled runs in the same workspace — it's a platform, not a library. Self-hosting is honest but heavy: Docker with 12GB+ RAM recommended, Postgres + pgvector, and note that the Chat/copilot feature remains a Sim-managed service even self-hosted (you fetch a COPILOT_API_KEY from sim.ai). Ollama/vLLM local models supported. Pick it when non-engineers need to build and operate agents; pick a code-first control plane (agentfield) when engineers do, and skip the platform entirely for a single agent.