Libre WebUI is a self-hosted AI workspace that keeps chat, notes, personas, and agent tasks in one place you control. Local models run through Ollama, and hosted ones come from OpenAI, Anthropic, Gemini, Groq, Mistral, OpenRouter, or any OpenAI-compatible endpoint added on the provider settings page. Pick a model per conversation. Replies stream, prompts queue, chats fork into branches, and several models can answer side by side. Notes keep Markdown documents with revision history. Personas bundle a system prompt, a model, and memory into a reusable assistant, and prompt templates with typed variables appear when you type a slash in the composer. Knowledge collections ground answers in uploaded documents and cite their sources. The Work area gives each task its own workspace with files, a terminal, diffs, and a live preview, and automations run scheduled prompts that arrive as normal chats. Administrators create users and groups, hand out roles, issue scoped API tokens, and share chats, notes, and personas through one grant model. A private team assistant, a research desk, or a sandbox where agents build small apps all fit here. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Every major model provider behind one ChatGPT-style interface: LibreChat spans OpenAI, Anthropic, Google, Azure, AWS Bedrock, Vertex AI, Groq, Mistral, OpenRouter, DeepSeek, and any OpenAI-compatible endpoint including local Ollama. You can switch models mid-conversation and compare providers without changing tools. Its Agents framework builds no-code custom assistants with tool access via Model Context Protocol servers, file search over uploaded documents through an optional pgvector-backed RAG service, and a sandboxed Code Interpreter that executes Python, JavaScript, Go, C++, Java, PHP, and Rust. Artifacts render React components, HTML, and Mermaid diagrams directly in chat, and image generation works through DALL-E and other configured providers. Multi-user support is enterprise-grade, with OAuth, SAML, LDAP, and two-factor authentication, per-user conversation history in MongoDB, and Meilisearch-powered search across all messages and files, plus reusable presets, forkable threads, and persistent memory across conversations. The economics favor teams: instead of a ChatGPT Plus seat per person, everyone shares one instance billed per API token, with access to every provider rather than one - and providers see individual API calls, not your accumulated organizational knowledge. Deployment is Docker Compose; API keys and endpoints are configured through .env and librechat.yaml.

Large language models get a polished front end that can run fully offline: Open WebUI is the self-hosted front end of choice. It talks to local model runners, primarily Ollama, and to any OpenAI-compatible API, so LM Studio, vLLM, Groq, Mistral, OpenRouter, and cloud providers all plug into the same chat interface and can be mixed per conversation. RAG is built in: upload files to knowledge bases or reference them in chat with the # command, backed by a choice of nine vector databases (ChromaDB and PGVector officially maintained) and multiple extraction engines including Tika and Docling, with hybrid BM25-plus-vector search and cross-encoder reranking. Web search results from providers like SearXNG, Brave, and Tavily inject directly into conversations. Extensibility comes from Python tools and functions that run inside the chat, a Pipelines plugin framework, and native MCP support. Multi-user features include RBAC, SSO, and group permissions, and the instance itself exposes an OpenAI-compatible API your own apps can call.

A private ChatGPT built with Next.js: Lobe Chat is the open-source AI chat interface teams self-host instead. Its main advantage is provider breadth: one interface connects to 40+ model providers, including OpenAI, Anthropic Claude, Google Gemini, Mistral, Groq, AWS Bedrock, Azure, and local models served through Ollama, so you can switch models per conversation and compare outputs. It handles multi-modal work: image recognition, image generation, text-to-speech, and speech-to-text. A plugin system based on function calling and the Model Context Protocol (MCP) adds external tools like web search and code execution. Run it in standalone mode as a single container with settings in browser storage, or in database mode with PostgreSQL and S3-compatible storage for persistent history, multi-user auth, and RAG knowledge bases built from uploaded documents with pgvector retrieval. Because tools arrive through function calling and MCP rather than a proprietary plugin format, custom internal tools can be exposed to the assistant with a standard server over STDIO or HTTP. Hundreds of pre-configured assistant roles import from the community marketplace. For teams the cost model matters: provider API keys billed per token typically undercut a ChatGPT Plus seat per person, and self-hosting keeps API keys, uploaded files, embeddings, and conversation history entirely on your own server.

Self-hosting a language model is only half the job; people still need somewhere pleasant to talk to it, and Chat UI is that window, the same interface that powers HuggingChat. Point it at any OpenAI-compatible endpoint, your own Ollama or llama.cpp server, the Hugging Face router, or a hosted gateway like OpenRouter, and the models it serves appear in the picker automatically, with no per-model configuration. Conversations are saved to your database and stay browsable in the sidebar, so a thread from last week can be reopened, continued, and compared against a fresh answer from another model. Multimodal models accept image uploads right in the composer, and models that support it can call MCP tools mid-conversation to fetch data or run actions. For a shared team deployment, OpenID Connect sign-in keeps individual histories and settings separate, and per-user defaults travel with each account. Everything a consumer chatbot would keep on someone else's servers, prompts, uploaded files, and usage history, stays in the MongoDB you control on the same machine. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Bring your own API keys and work with OpenAI GPT models, Anthropic Claude, Google Gemini, Mistral, DeepSeek, Grok, Azure endpoints, and local models in one organized workspace: TypingMind is a unified chat frontend for large language models, replacing a browser tab per provider. Parallel chat sends the same prompt to multiple models and compares answers side by side, and models can be switched mid-conversation. A prompt library stores reusable, tagged prompts with variables, and the AI Agents system builds specialized assistants that bundle a base model, custom instructions, assigned plugins, and uploaded knowledge files for RAG. Plugins extend every connected model with web search, image generation (DALL-E, Stable Diffusion), Deep Research, URL reading via Firecrawl, and Zapier automation - plus MCP server integrations for Notion, Atlassian, and other external tools, and a JavaScript extension API for custom behavior. Chats store locally by default with optional sync. Self-hosting puts the interface on your own domain and, for teams, adds branding, member access limits, and shared prompt and agent libraries.

Chat, research, and everyday chores all run through OpenAgent, a private AI assistant hosted on a server you control. Pick from more than thirty model providers, including OpenAI, Anthropic, Gemini, DeepSeek, and local Ollama models, and switch models inside a conversation. Agents can drive a real browser, search the web, run shell commands, read and write Word, Excel, and PowerPoint files, and call any MCP server. Every tool call shows its arguments and result. Upload PDFs and spreadsheets to build isolated knowledge bases with semantic search, then attach them to a chat. A drag and drop workflow builder chains steps with branches, parallel tasks, and schedules. The admin console tracks token use and cost per user and model with charts and a message heatmap, lists every tool, records audit logs, and shows live CPU, memory, and API latency. Single sign-on through OIDC, OAuth2, LDAP, or SAML and separate workspaces keep teams apart, and a REST API with Swagger docs exposes every feature. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Dify turns the notoriously complex process of building production-grade AI applications into a visual drag-and-drop experience that teams can actually ship and maintain. With over 87,000 GitHub stars and backing from prominent investors, the platform has become the go-to open-source LLMOps solution for organizations that refuse to be locked into proprietary AI stacks. The visual workflow canvas lets developers wire together LLM calls, conditional logic, iteration loops, tool invocations, and human-in-the-loop checkpoints without writing boilerplate integration code. Its RAG pipeline engine handles the full document lifecycle from ingestion of PDFs, Word documents, and HTML through configurable chunking strategies, embedding with models from OpenAI or open-source alternatives, vector storage in Weaviate, Qdrant, Pinecone, or pgvector, and hybrid semantic-plus-keyword retrieval with citation tracking. Dify integrates with hundreds of model providers including OpenAI GPT-4o, Anthropic Claude, Google Gemini, Mistral, Llama, and any OpenAI-compatible endpoint like Ollama for fully local inference. The agent framework supports both ReAct and function-calling strategies with 50-plus built-in tools spanning Google Search, DALL-E, Stable Diffusion, WolframAlpha, and custom API definitions. Published apps can be deployed as hosted web interfaces, embedded chat widgets, REST API endpoints, or MCP-compatible tools. Enterprise features include role-based access control, SSO integration, and audit logging. A built-in marketplace enables teams to share and reuse model providers, tools, and workflow templates across projects. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed with an open-source community edition.

Drag nodes onto a canvas and ship an LLM app: Flowise is an open-source visual builder for AI agents and LLM applications, written in Node.js on LangChain.js and licensed Apache-2.0. You assemble flows by dragging nodes onto a canvas: models, prompts, memory, vector stores, retrievers, and tools, then wire them together and test in the built-in chat panel. Three builder types cover increasing complexity: Assistant for simple RAG chat over uploaded files, Chatflow for single-agent systems with techniques like rerankers and Graph RAG, and Agentflow for multi-agent orchestration with branching, looping, shared flow state, and human-in-the-loop checkpoints. Over 100 integrations connect data sources, vector databases, and both proprietary and open-source models, plus MCP client and server nodes for standard tool interop. Finished flows are exposed as REST APIs, embedded chat widgets, or via JS and Python SDKs - each flow gets an endpoint the moment it is saved, removing the deployment gap between a working prototype and something your application can call. Execution logs, visual step debugging, and external log streaming trace behavior, while input moderation and rate limiting act as guardrails; RBAC, SSO, and workspaces cover team deployments. Self-hosting keeps prompts, encrypted credentials, and conversation data on your own instance, which matters when flows handle internal documents or customer data - and wiring a model, prompt, memory, and vector store on the canvas replaces the boilerplate a hand-coded LangChain project would need.

Langflow turns LLM application development into a visual canvas where every node maps to a real LangChain primitive (chains, agents, retrievers, memory, vector stores, and tools) that teams wire together without writing integration boilerplate. The platform supports 15+ LLM provider components including OpenAI, Anthropic, Google Gemini, Mistral, Groq, Cohere, Azure OpenAI, HuggingFace, and Ollama for fully local inference, with LiteLLM proxying to over 100 additional providers through a single OpenAI-compatible endpoint. Vector database integrations cover Pinecone, Weaviate, Chroma, Qdrant, Astra DB, OpenSearch, FAISS, and Milvus, while built-in Knowledge Bases introduced in version 1.8 allow RAG pipelines without any external vector service. Multi-agent orchestration enables agent-to-agent communication with conversation management, persistent Memory Bases for cross-session context retrieval, and step-by-step reasoning visibility in the interactive Playground. Every flow automatically becomes a callable REST API endpoint via the /run route and an MCP server exposable to Claude Desktop, Cursor, or any MCP-compatible client. Every component is a real Python class that developers can customize, extend, or replace, while Extension Bundles package third-party integrations as independent pip packages for modular installation. Tool integrations include web search, Slack, Gmail, Google Drive, GitHub, and custom REST API calls. Docker deployment with PostgreSQL persistence runs on port 7860. Backed by 153,000+ stars and DataStax. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Sim Studio lets teams build, deploy, and monitor AI agent workflows by dragging blocks onto a visual canvas and wiring them into executable pipelines, backed by over 1,000 integrations. The React Flow editor represents each step as a node: LLM calls, tool invocations, conditional branches, and data transformations form directed acyclic graphs that run as complete agent pipelines. Every major LLM provider works natively, including OpenAI, Anthropic, Google Gemini, Groq, and Cerebras, plus local models through Ollama and vLLM. Integrations span Gmail, Slack, Microsoft Teams, Telegram, WhatsApp, Notion, Google Workspace, Airtable, GitHub, Jira, Linear, Perplexity, Firecrawl, PostgreSQL, Supabase, Pinecone, and Qdrant. Built-in tables provide a database layer, a file store offers shared team storage, and knowledge bases powered by PostgreSQL with pgvector enable retrieval-augmented generation. Finished workflows deploy as REST API endpoints, scheduled jobs, or Slack bots, with block-by-block execution traces for full observability. Real-time collaborative editing via Socket.io supports simultaneous multi-user construction. Alternatively, describe agent behavior in natural language and Sim assembles the workflow automatically. Built on Next.js App Router, Bun runtime, Drizzle ORM, and Tailwind CSS. 29,400+ GitHub stars and 100,000+ builders. Apache-2.0 licensed.

Zapier's job, on your own server: Activepieces is an open-source workflow automation platform built to be exactly that replacement. Flows are built in a visual no-code editor with triggers, actions, loops, conditional branches, auto-retries, raw HTTP steps, and code steps that run JavaScript or TypeScript with full npm package support. Integrations are "pieces" - type-safe TypeScript npm packages with hot reloading for local development - and the catalog spans 600+ services, with the large majority contributed by the community. The platform is AI-first in two directions: native AI pieces call OpenAI, Anthropic, Google, and Azure models inside flows, and every piece automatically doubles as an MCP server, so assistants like Claude Desktop and Cursor can invoke your integrations and workflows through natural language. A built-in MCP server also exposes 30 tools for building flows, managing tables, and running tests agentically. Flows are fully versioned with draft and locked states. The core is MIT-licensed and runs on TypeScript with PostgreSQL and Redis.

Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.

Run a whole fleet of AI agents as managed services, each with its own model, memory, schedules, and sandboxed workspace, from one admin console. Create an agent, point it at OpenAI, Anthropic, OpenRouter, or any OpenAI-compatible endpoint, store its API keys encrypted, and it is ready to chat in the browser. People sign in with a device key and get a session list, streaming replies, and file attachments. The Agents table shows status, last activity, sessions, errors, and token spend for the past 24 hours, and the Stats page tracks users, sessions, events, and total tokens. Cron or one-shot schedules let an agent send a daily brief, and each run is logged. Owner, user, and guest roles control who may talk to an agent or change it, and policy and approval tabs gate risky tool calls. Skills and MCP servers are registered once and enabled for one agent or the whole fleet, and instructions can be pushed to every agent at once. Sessions, memories, and secrets sit in PostgreSQL, so state persists across gateway restarts. Use it for an internal agent platform, a support desk, or one agent per customer. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

MateClaw delivers a multi-agent AI platform where digital employees run as persistent team members with roles, goals, and accumulated skills rather than stateless chat completions. The Spring Boot backend on Spring AI Alibaba provides ReAct iterative reasoning and Plan-and-Execute decomposition on a StateGraph runtime, with parallel delegation between employees and dynamic context pruning for multi-step tasks. Five career templates ship ready (Product Researcher, Customer Support, Knowledge Curator, Data Analyst, Executive Assistant) while custom employees inherit configurable backstories, pixel-art avatars, and dedicated tool bindings. The MCP integration supports stdio, SSE, and Streamable HTTP transports with per-employee tool isolation preventing capability bleed between agents. ACP bridges bring Claude Code, Codex, and other coding agents in as first-class employees. Workflow orchestration composes multiple employees and system actions into publishable linear DSL processes with seven step modes: sequential, fan_out, collect, conditional, await_approval, dispatch_channel, and write_memory. The trigger system wires cron schedules, webhooks, channel messages, employee lifecycle events, content matches, and workflow completions to automated flows. The Admin Runtime Console provides real-time visibility into running employees with token usage tracking and one-click force-recycle. Spring Boot Actuator monitoring, full audit trail, and per-channel error isolation deliver production-grade reliability. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Whirl puts every top AI model in a single conversation and remembers what you were working on last week, so you can switch models mid-thought without losing the thread. Ask for a report, a chart, or a small interactive page and it appears as a living artifact in a side panel, still editable while you keep chatting, and shareable by link when it is ready to leave the conversation. Connect your own tools over MCP, with OAuth sign-in handled for you, or install skills that teach the app new tricks your team relies on. Long-term memory carries your preferences and project context from chat to chat, and live web search with page reading grounds answers in today's pages instead of the model's training data. Sensitive threads can be locked with a password that encrypts them on your device, where the server never sees the key and only zero-retention models may answer. Around those headline pieces sits the everyday kit: incognito mode, a message queue for when you think faster than the model replies, voice input, image generation, file attachments, folders, and sharing controls. An admin console manages the model catalog, integrations, and skills, and the interface itself switches between light and dark with your choice of accent color, installable as a mobile web app. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.