One workspace holds agents, data, and run history
Sim combines a visual workflow builder with chat, code blocks, integrations, files, tables, and searchable knowledge. A team can connect model calls to business systems, deploy the workflow, then inspect its runs and logs without building a separate control panel. The current README claims more than 1,000 integrations, but each useful provider still needs credentials and an acceptance test against the actions the workflow will take.
The scale is closer to an application suite than a canvas component. Our commit f1a3456 checkout contained 18,392 files and about 3,044,743 lines of source in 294.9 MB. The monorepo includes the main web app, desktop work, realtime services, shared packages, setup tooling, and documentation. Next.js, Bun, PostgreSQL, Drizzle, Socket.io, and Trigger.dev are among the named pieces.
The setup wizard creates a multi-service installation
For normal self-hosting, the README recommends npx sim-setup rather than cloning the repository. The wizard creates a deployment directory, generates secrets, provisions the database, writes environment settings, connects a Chat API key, and starts published images with Docker Compose. It also has commands for status, logs, diagnosis, updates, restart, and removing containers while retaining data. That is a useful operational surface for a large stack.
Requirements start with Node.js 20 and Docker. The README's setup link warns that insufficient memory means less than 12 GB of RAM. PostgreSQL is part of the documented stack, and the setup tool can add email, object storage, sandboxing, jobs, cache, knowledge, LLM, or an integration such as Slack. Each addition changes the secrets, network access, backup plan, and failure modes an operator owns.
What happened when we ran it
Our unprivileged Node 22 sandbox installed the repository in 117 seconds. Bun added 2,519 packages, leaving 2,560 MB on disk. The build failed after 8 seconds. Its final lines point to apps/desktop/scripts/ensure-pty-prebuilds.ts, where fetchPrebuild raised the error; the desktop build then exited 1. Four of 7 tasks had succeeded at that point.
The log tail does not say why the prebuild fetch failed, so blaming network policy, a missing artifact, or application code would be guesswork. The repository scan found 15 CI workflow files, no Dockerfile at the scanned location, no top-level tests directory, and monorepo workspaces. The 8-second result applies to commit f1a3456 in our stated container, not the published Compose images.
Our test command also exited 1 after 203 seconds. The harness summary says Vitest ran 116 tests with 116 passed and 0 failed, while the wider monorepo log tail reports 3 failures in an app compiler file and 1 timed-out desktop browser-import test. The desktop package's summary showed 1 failed file and 60 passed files. These outputs describe different slices of the same command, so the defensible overall result is failure.
The desktop timeout was set to 10,000 ms and occurred in chromium-site-names.test.ts. The supplied log does not establish whether the test is flaky, the sandbox is slow, or the code has a defect. The 3 app failures also need their full assertion messages before diagnosis. A maintainer evaluating this commit should rerun the exact failing package tests and preserve the complete logs.
Chat remains a Sim-managed service when self-hosted
Self-hosting does not make every feature local. The README says Chat is managed by Sim and requires a Chat API key connected during setup. Keys can later be viewed, created, or revoked on sim.ai. Local models are supported through Ollama and vLLM, but the presence of those inference routes does not remove the Chat account boundary described by the project. Air-gapped buyers should map each required feature before installing.
The setup tool reports configured, missing, or invalid capabilities without printing credential values. That distinction is useful once an installation has several optional services. A 2,519-package codebase can fail far from the workflow canvas, so health checks should cover PostgreSQL, realtime connections, scheduled work, storage, model endpoints, and each OAuth callback rather than only loading port 3000.
Release v0.8.11 is active and still pre-1.0
Release v0.8.11 was published on August 25, 2026, and the repository was pushed again on August 26. GitHub showed 29,471 stars and 289 combined issues and pull requests when fetched. The release included changes to setup, secrets, tables, OAuth credentials, webhooks, vLLM endpoints, file handling, and CI audits. That breadth shows current maintenance and also a wide regression surface.
Apache 2.0 covers the repository according to the current README and GitHub license result. The product is still on a 0.x line, so pin a release and rehearse upgrades against representative workflows. Our 117-second install succeeded, but the failed build and test command prevent a clean source recommendation for f1a3456. Published images are the sensible evaluation route for users; contributors need to resolve or reproduce both failures first.
Sim earns its weight only when it replaces several tools
A team using agents, schedules, integrations, shared files, tables, knowledge, and monitoring can justify Sim's 2,560 MB dependency environment and service stack. The setup wizard reduces initial friction, while the management commands give operators a coherent way to inspect the installation. Those benefits matter more as workflow count and contributor count grow.
For a handful of model chains, this is too much machinery. The source tree failed both major gates in our sandbox, Chat keeps a hosted key boundary, and optional capabilities multiply credentials. Pick Sim when someone will own it as an internal platform. Otherwise, n8n, Langflow, Dify, or a small coded service may be easier to audit and keep running.