Sim Studio is an open-source platform for building, testing, and optimizing AI agent workflows, targeting developers and researchers who need to rapidly deploy LLMs integrated with various tools. It offers a visual interface for creating these agentic pipelines, simplifying complex AI orchestration.

How It Works

Sim Studio utilizes a Next.js (App Router) framework with PostgreSQL and Drizzle ORM for data management. It employs Better Auth for authentication and Shadcn/Tailwind CSS for its UI, with ReactFlow powering the visual flow editor. This stack provides a modern, robust foundation for building interactive AI applications.

Quick Start & Requirements

• Self-Hosting (Recommended): Clone the repository, create and populate .env from .env.example (requires BETTER_AUTH_SECRET), and run docker compose up -d --build. Access at http://localhost:3000/w/.
• Local Models: Use ./sim/scripts/ollama_docker.sh pull <model_name> to pull models. Start with ./start_simstudio_docker.sh --local (CPU) or docker compose up --profile local-gpu -d --build (GPU).
• Existing Ollama: Use docker compose up --profile local-cpu -d --build --network=host or configure host.docker.internal mapping in docker-compose.yml.
• Dev Containers: Open in VS Code with the Remote - Containers extension and select "Reopen in Container".
• Manual Setup: git clone, cd sim/sim, npm install, copy .env.example to .env, set variables, npx drizzle-kit push, npm run dev. Access at http://localhost:3000.
• Prerequisites: Docker, Node.js, PostgreSQL (for manual setup), Ollama (for local models).

Highlighted Details

• Visual agent workflow builder with ReactFlow.
• Support for local LLM integration via Ollama (CPU/GPU).
• Next.js App Router architecture.
• PostgreSQL database with Drizzle ORM.

Maintenance & Community

The project is maintained by the Sim Studio Team. Contribution guidelines are available.

Licensing & Compatibility

Licensed under the Apache License 2.0. This license is permissive and generally compatible with commercial use and closed-source linking.

Limitations & Caveats

Email verification codes are logged to the console if RESEND_API_KEY is not set, requiring manual intervention or a configured email provider for production authentication flows.