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.

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.

Drag an AI agent onto a canvas beside a Gmail trigger, a condition, and a Google Sheets step, and ByteChef runs the whole thing as one durable workflow that resumes where it stopped. Runs that fail or wait for a human pick up from the step they reached. The visual editor maps values between steps with data pills, and its 250+ connectors double as agent tools and MCP tools. An agent combines a model from twelve LLM providers, including OpenAI, Anthropic, Mistral, and Ollama, with chat memory, knowledge-base retrieval, and tools. It streams structured answers. Flow controls cover conditions, branches, loops, parallel and fork-join paths, subflows, error handling, and approval steps that pause for a person. Workflows start from webhooks, polling, schedules, forms, or app events, and code steps run JavaScript, Python, or Ruby. Workflows can be exposed through an MCP server for Claude Desktop, Cursor, or Windsurf, and ByteChef consumes external MCP servers too. Data Tables add typed relational tables with a spreadsheet-like grid and CSV import and export. The Agent Playbook opens a chat with the agent as you build it. Every run is listed with per-step input, output, and errors. 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 + EE 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.

Open Agent Builder delivers a visual canvas for orchestrating AI agent workflows without writing Python scripts or managing complex codebases. The React Flow-powered drag-and-drop interface supports seven node types — Agent, Scraper, Transform, If/Else, Loop, User Approval, and MCP Tool — each configurable with provider-specific settings for Anthropic Claude (Haiku 4.5 and Sonnet 4.5), OpenAI GPT-5, Groq, or any OpenAI-compatible endpoint. The LangGraph orchestration engine handles state management, conditional routing, and human-in-the-loop approval gates while Firecrawl integration converts any website into structured, LLM-ready data through scrape, crawl, and map operations. E2B sandboxed code execution powers Transform nodes for secure data manipulation without risking host system integrity. Real-time streaming updates show execution progress node-by-node as workflows run, with Convex providing reactive database synchronization for workflow state and execution history. The TypeScript-first architecture (96.8% TypeScript) built on Next.js 16 App Router with Tailwind CSS delivers a responsive interface across devices. Clerk handles multi-user authentication with JWT integration for secure workspace isolation. Deploy via npm install and environment configuration with Firecrawl, Convex, and Clerk API keys. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Huginn has established itself as the definitive open-source automation engine for developers who refuse to hand their workflow data to third-party cloud services. The platform lets you build agents that scrape websites, monitor RSS feeds, track weather via APIs, watch Twitter streams, aggregate news, detect price changes, and trigger notifications through email, SMS via Twilio, Slack webhooks, or social media posts to Twitter and Tumblr. Each agent creates and consumes JSON events, propagating them along a directed graph where complex multi-step workflows emerge from simple single-purpose components. The web interface provides visual agent management with drag-and-drop scenario building, real-time event logs, scheduling controls, and a built-in agent library covering dozens of use cases out of the box. Huginn supports Liquid templating for dynamic event transformation, regex-based content extraction, JavaScript-based data manipulation, and HumanTaskAgent for crowd-sourced workflow steps. Custom agents can be packaged as Ruby gems and loaded via the ADDITIONAL_GEMS environment variable without modifying core code. Deployment options include Docker with the official huginn/huginn all-in-one image or huginn/huginn-single-process for production multi-container setups with PostgreSQL or MySQL backends, plus native support for Heroku and OpenShift PaaS platforms. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

A clean alternative to n8n and Zapier that puts AI-native workflows front and center, Fynt is the MIT-licensed workflow automation platform where you drag nodes onto a React Flow canvas, wire them together with typed connections, and let a distributed BullMQ engine execute them — with every step streamed live to your browser over WebSockets so you never wonder what happened inside a run. The node library spans triggers (manual, webhook, cron scheduling), AI providers (OpenAI, Anthropic, and Gemini with structured output parsing), service integrations (GitHub webhooks, Notion databases, Slack channels, Discord bots, arbitrary HTTP endpoints), logic gates (conditional branching, filtering, data transformation), and utility nodes (delay, logging, payload mapping). The execution architecture separates concerns across three services: a Next.js 16 web application serving the React 19 workflow builder and tRPC API, a BullMQ worker processing jobs with node-level retries and checkpointing for crash-safe execution, and a dedicated WebSocket relay server broadcasting real-time run events via Redis Pub/Sub. All stored credentials are encrypted at rest using AES-256-GCM with per-credential initialization vectors. The full-stack deploys as a single Docker Compose stack (web, worker, realtime, PostgreSQL, Redis) or individually via pnpm workspaces in a Turborepo monorepo. Authentication is handled through better-auth with configurable OAuth providers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Automatisch runs your Zapier workflows on your own hardware - an open-source, self-hosted automation platform built as a direct alternative. Flows are chains of steps: one trigger (a polling or webhook event such as a new GitHub issue, a Stripe payment, or a form submission) followed by action steps that pass data downstream (post to Slack, append a Google Sheets row, update Notion). The visual builder deliberately mirrors Zapier's trigger-action model, so migrating existing Zaps requires no retraining and no programming knowledge. Roughly 60 integrations cover common business services - Slack, GitHub, Google Sheets, Notion, Stripe, Discord - and connections store credentials per service, with multiple accounts per app supported. Every execution runs on your own server: execution history, logs, and payload data never touch a third-party processor, which matters for GDPR, healthcare, and finance workloads. Error handling with retry logic, a REST API for programmatic flow management, and Docker Compose deployment round out the platform. The AGPL-3.0 Community Edition has no feature limits or per-task billing; an Enterprise Edition adds SSO, roles, and audit logs.

Describe the task in plain words, pick the sources and model it may use, and an agent plans the workflow before running it. That is the core loop: agents build editable visual workflows from a task description, execute them on demand or on a schedule, and keep everything traceable. Prefer building by hand and the canvas offers 17 preconfigured steps, branching, undo and redo, JSON import and export, plus eight starter templates. Feed it real work by importing PDF, DOCX, XLSX, CSV, JSON, and text files, or by connecting folders, HTTP endpoints, and approved local programs. Upload a screen recording and it identifies the actions with timestamps, turning a demonstrated process into an editable workflow you can refine. Model calls go to the endpoint you choose: Ollama, LM Studio, vLLM, or any OpenAI-compatible service, local or cloud with your own credentials. Every run can be inspected step by step, cancelled mid-flight, and exported as JSON, CSV, or Markdown reports. Observations from completed runs land in a knowledge and learnings store, where you review them and promote the useful ones into reusable skills for the next task. The Docker release bundles the application with FFmpeg and local Whisper support, and your documents stay on your own machine. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 licensed.

With over 3,700 GitHub stars and growing adoption among teams tired of managing complex orchestration platforms, Dagu delivers a complete workflow engine as a single Go binary that requires no external database, message broker, or framework installation. Define directed acyclic graphs in declarative YAML — specifying dependencies, schedules, retries, timeouts, approvals, and notifications — while keeping existing shell scripts, containers, and tools completely unchanged. The built-in Web UI provides live pipeline visualization, per-step log streaming, run history browsing, artifact previewing, manual retry controls, and workflow YAML editing without SSHing into servers. Execute steps as shell commands, Docker containers, Kubernetes Jobs, SSH remote commands, SQL queries, or HTTP requests, with conditional branching and parallel execution handled natively. The integrated Model Context Protocol server exposes dagu_read, dagu_change, and dagu_execute tools, enabling AI agents like Claude, Codex, and Cursor to inspect workflow state, preview YAML modifications, and control runs through authenticated endpoints. The harness.run executor lets external coding-agent CLIs operate inside DAG steps with full scheduling and approval gate support. Scale beyond a single machine with the distributed worker mode, which dispatches tasks to remote nodes via gRPC with automatic label-based routing and worker selection. Deploy with Docker, the official Helm chart for Kubernetes, or a simple binary download requiring only a Linux, macOS, or Windows host. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3 licensed.

With over 27,000 GitHub stars and an ecosystem of 1,900+ plugins covering every major cloud provider, database, and SaaS platform, Kestra is the orchestration engine that brings Infrastructure as Code principles to workflow automation — defining complex multi-step pipelines in readable YAML that execute across any language, runtime, or infrastructure boundary. The built-in VS Code-style editor provides syntax highlighting, auto-completion, real-time validation, and an AI Copilot that generates workflow YAML from natural language descriptions. Tasks execute in Python, Node.js, Go, R, Shell, SQL, or any Docker container, with event-driven triggers listening for file arrivals on SFTP and cloud storage, messages from Kafka, Redis, Pulsar, AMQP, MQTT, NATS, AWS SQS, Google Pub/Sub, and Azure Event Hubs in real time. The topology view visualizes workflow DAGs with execution state, duration, and output artifacts for each task node. Namespaces organize workflows into isolated environments with configurable secrets, while subflows enable modular composition with inputs, outputs, and conditional branching. Retry policies, timeouts, error handlers, and automatic backfills for missed schedules ensure reliability across production workloads. Git integration pushes workflows directly to branches from the UI with CI/CD pipeline support for automated deployment. The REST API enables programmatic workflow management, execution triggering, and resource provisioning. 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.

Wire nodes together in a browser, deploy in one click, and real-time data flows from sources through transformations to outputs: Node-RED is the OpenJS Foundation's flow-based programming tool for event-driven applications. Born at IBM as a proof-of-concept for manipulating MQTT topic mappings, it has become the lingua franca of IoT and automation glue - home automation, industrial control, edge data collection - with a community library of over 5,000 contributed nodes and flows covering protocols, devices, and services. Where visual wiring runs out, JavaScript function nodes written in a rich in-editor code editor take over, and every flow serializes to importable, exportable JSON that shares cleanly and version-controls sensibly. Version 5.0 (2026) delivered the largest editor overhaul in the project's history: a rethought layout with Explorer and Information panels in a split sidebar, a native dark theme with theme variants, improved accessibility, and refreshed node appearance. The runtime is lightweight Node.js, exploiting the event-driven non-blocking model so the same flows run on a Raspberry Pi at the network edge or a cloud VM. Apache-2.0 licensed with 240+ contributors, it pairs naturally with dashboard nodes for live charts and controls.

Bridging local hardware and cloud intelligence, OwnPilot orchestrates autonomous multi-channel agent swarms and visual workflow pipelines while keeping sensitive personal records strictly on private infrastructure. Users can trigger autonomous task runs that browse websites using headless browser automation, extract data tables, and summarize research directly into encrypted markdown notebooks. The built-in workflow canvas allows individuals to construct branching automation sequences combining large language models, conditional logic gates, iterative data loops, and human-in-the-loop approvals. Users delegate calendar scheduling, task tracking, expense budgeting, and contact lookups through conversational chats conducted over web portals, Telegram bots, or WhatsApp numbers. Operators can dispatch coding agents to inspect local repositories, execute shell commands in sandboxed environments, and stream live terminal logs as automated patches develop. The platform also enables home automation enthusiasts to monitor MQTT telemetric feeds from microcontrollers, queue device commands, and receive instant alert notifications when sensor thresholds trigger. Advanced security layers inspect all incoming prompts for personal data patterns, enforce strict permission boundaries across file directories, and generate tamper-evident audit logs for every autonomous tool call. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Recurring chores should get cheaper every time you run them, and Umpteenth is a self-hosted agent service built on that idea: describe a job once in plain language, and each run teaches it to need less help. A job starts on a schedule, a webhook call, the API, or the Run now button, and each run gets a fresh disposable container destroyed afterwards. The first run is an Explore run where the agent works out the steps; afterwards a reflection step reads the transcript and writes short learnings plus reusable toolkit scripts into a numbered playbook version. Later runs are Assisted, starting from those learnings, and after three successful assisted runs that take the same steps, the job graduates: reflection writes a main script, and scripted runs execute it alone, spending no model tokens unless a check asks for a judgment call. If a scripted check fails, the agent takes over in the same sandbox, finishes the job, and repairs the script. The job page charts cost per run dropping toward zero. Connect HTTP MCP servers such as GitHub or Slack; model keys and MCP credentials stay on the host and never enter the sandbox. Each job sets its own schedule, model, reach, and per run spending limit. Deploy with Docker Compose, or on Kubernetes with the Helm chart, where every sandbox is a pod. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Originally built at Netflix to orchestrate microservices powering 230 million subscribers and now trusted in production at Tesla, LinkedIn, and J.P. Morgan, Conductor is the most battle-tested open-source workflow engine available — with 32,000 GitHub stars and horizontal scalability to billions of executions. The architecture cleanly separates orchestration from business logic: workflows are defined in declarative JSON while workers execute tasks in any of seven supported languages (Java, Python, Go, JavaScript, C#, Ruby, Rust) with zero framework constraints. Durable execution persists every state transition, enabling automatic retries, configurable timeouts, crash recovery, and instant replay from any failure point without re-executing completed tasks. Native AI agent orchestration supports 14+ LLM providers (Anthropic, OpenAI, Google Gemini, AWS Bedrock, Mistral, Cohere, HuggingFace, Ollama), MCP tool calling, function calling, human-in-the-loop approval gates, and vector database integration (Pinecone, pgvector, MongoDB Atlas) for RAG pipelines. Deploy with your choice of five persistence backends (PostgreSQL, Redis, MySQL, Cassandra, SQLite), six message brokers, and Elasticsearch or OpenSearch for workflow indexing — all configurable via Docker Compose files included in the repository. The built-in web UI provides workflow visualization, execution monitoring, task queue inspection, and manual intervention controls. 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.

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.