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.

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.

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.

With over 5,000 GitHub stars since its June 2026 launch, OOMOL OpenConnector bridges the gap between AI agents and the real world by handling the authentication nightmare that stops LLMs from calling external APIs safely. The runtime connects to more than 1,000 SaaS providers — GitHub, Gmail, Notion, Slack, Microsoft, HubSpot, Google Workspace, and hundreds more — through 10,000+ prebuilt typed Actions that agents can discover and execute without ever touching raw credentials. OAuth2 flows, API key rotation, custom credentials, and no-auth providers are all managed centrally with AES-encrypted storage, scoped runtime tokens, and configurable action allowlists and blocklists that enforce least-privilege access. Agents interact through five access surfaces: the Model Context Protocol endpoint at /mcp for Claude and other MCP-capable hosts, a full REST API at /v1 for programmatic control, an auto-generated OpenAPI specification for code generation, a TypeScript SDK for application integration, and the oo CLI for local agent relay. The built-in Web Console provides browser-based administration for configuring OAuth apps, managing connections, inspecting action schemas, and reviewing execution logs with redacted inputs. Deploy via Docker Compose with SQLite for single-server setups, run from source on Node.js 22+, or push to Cloudflare Workers with D1 and R2 for edge deployment. 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.

The integrations your SaaS product offers its own users - that is what Nango, an open-source product-integrations platform, exists to build. It solves the repetitive infrastructure work behind every third-party API connection: OAuth flows, API key handling, token refresh, encrypted credential storage, rate-limit backoff, retries, and multi-tenant connection management. It ships pre-built auth configurations for 800+ APIs. Your users connect their accounts through an embeddable, white-label Connect UI, and your backend then reads or writes data through Nango's proxy, SDKs, or REST API without ever touching raw credentials. Integration logic is written as TypeScript functions covering actions, scheduled data syncs, and webhook processing - all running on one runtime with retries, checkpointing, and per-connection logs built in. Syncs pull records incrementally on a schedule, one-way or two-way, which suits RAG pipelines, search indexing, and keeping local copies of external data current. Selected actions can also be exposed as tool schemas or through a built-in MCP server, so AI agents operate on user-connected accounts without ever handling provider credentials. Auth support spans OAuth 2.0, OAuth 1.0a, API keys, basic auth, and JWT, and observability - logs, metrics, failure detection, and a reconnect flow for expired credentials - is scoped per customer connection for easier support debugging. Works with any backend language. Self-hosting on RepoCloud keeps all customer credentials and synced data on infrastructure you control, which matters for data residency and compliance requirements.

One endpoint for every MCP server you run: MCPHub gathers local and remote Model Context Protocol servers behind stable URLs, so AI clients connect once and see what you allow. Claude Code, Cursor, and Cherry Studio can use four routes: everything at /mcp, a named group at /mcp/{group}, one server at /mcp/{server}, or semantic tool search at /mcp/$smart. Smart routing runs vector search on PostgreSQL with pgvector and an OpenAI-compatible key, so the model gets a shorter tool list. Servers attach over stdio, SSE, or streamable HTTP, OpenAPI services can be wrapped as MCP tools, and changes apply without downtime. In the other direction, MCP tools can be exported as an OpenAPI 3.0.3 spec for OpenWebUI and other OpenAPI clients. Bearer keys, OAuth 2.0 (client and server modes), and GitHub or Google sign-in in database mode control access, with per-user visibility for servers and groups. Encrypted per-user credentials let one shared server use each person's own key. Logs show tool-call activity, request status, and latency, health checks track each connection, and the dashboard controls which tools, prompts, and resources each server exposes. Large text tool results can be compressed, interactive MCP Apps are proxied through MCPHub routes, and a built-in market lets you browse a server catalog. Typical uses include a team-wide gateway, per-project groups, and direct single-server routes for debugging. 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 team wiring its own MCP servers by hand ends up with credentials scattered across dotfiles and no list of what exists; MCP Gateway and Registry replaces that with one governed front door. Register an MCP server, an A2A agent, a reusable skill, or a custom entity type once, and the Discover page lists it with tags, ratings, and search by natural language. Coding assistants and agents connect to a single authenticated gateway backed by Keycloak, Entra ID, Okta, Auth0, or Cognito, with scopes that decide who may call which tool. Virtual servers bundle tools from several backends behind one endpoint. Connected Accounts brokers third-party logins for Slack, Atlassian, and GitHub so tokens stay off laptops. Every registration is security scanned, and an admission gate holds unsafe items for review. The settings area offers audit log filtering with JSONL and CSV export, federation with outside registries, per-group rate limits, and a searchable configuration viewer. OpenTelemetry metrics and health checks are built in. 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.

MCPProxy puts one safe endpoint in front of every MCP server your AI agents use, and it holds each new server in quarantine until a person approves it. Add stdio or HTTP servers on the Servers page, then review the captured tool definitions and scanner findings in the Review queue before any agent can call them. The Tools page lists every tool with a Read, Write, or Destructive tier, an approval state, and a usage count, plus switches to hide whatever you do not want exposed. Agents see a short set of discovery and call tools instead of the full catalog, and the Home dashboard estimates how much context that saves per request. The Activity Log records each call with its server, intent, status, and duration, and exports for audits. The Usage page charts calls per tool, response sizes, errors, latency, and activity over time, filtered by profile, client, or token. Profiles and agent tokens scope what each client may reach, a Secrets page keeps credentials out of config files, and a setup wizard connects Claude Code, Claude Desktop, Cursor, Windsurf, and VS Code. Platform teams and solo builders get one place to see and control everything their agents can touch. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Unla puts a friendly front door on every API you already run, so AI clients can call it as an MCP server without anyone writing a line of glue code. Describe an endpoint in YAML or the form editor, name its arguments, choose where each one goes in the request, and the gateway exposes it as a tool over SSE or streamable HTTP. Import an OpenAPI file to generate a whole server at once, or proxy a third-party MCP server and route it under a prefix of your choice. The Gateway Manager shows every server as a card or table row with its routes, enabled tools, and tool counts. Every save creates a numbered config version with its author and timestamp, so changes are easy to audit and roll back. Tenants keep teams separate, user accounts carry roles, and CORS settings sit next to each route. Configuration hot reloads, syncs across replicas, and persists to disk, SQLite, PostgreSQL, or MySQL. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

DopplerTask is the control layer where AI agents build your automations and you decide what goes live. You describe the outcome in plain language, and your agent assembles a task from a library of eighty-one ready-made steps spanning messaging, ticketing, sales, operations, documents, databases, queues, and AI models. The proposal lands in a visual editor that people and agents share, with new and changed steps marked and the old value of each field beside the new one. Nothing goes live until you approve it, and the previously approved version keeps running untouched in the meantime. Once a task is live it can start from a webhook, a schedule, a message queue, a manual click, or the agent itself, and every run is recorded with the output of each step, the person who started it, and the person who approved the version. Failed runs resume from the step that failed, with retries and continue-on-failure where you want them. Agents reference your credentials by name only; the values stay encrypted on your server, beyond the agent's reach, and separate tokens for people and agents plus single sign-on keep access tidy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT 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.

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.

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.

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.

Eliminate scattered configuration files and leaked credentials across development teams with Shelve, an open-source secrets management platform that secures environment variables across development, staging, and production tiers. Engineering teams can organize sensitive database passwords and third-party API credentials within a centralized vault protected by AES-256 encryption and SHA-256 integrity verification. The platform synchronizes configurations directly to GitHub Actions and repository secret stores through an official GitHub App integration. Developers can inject encrypted variables directly into local processes using the dedicated CLI without saving plain-text secrets to disk. The built-in sharing vault creates self-destructing, password-protected links to exchange sensitive credentials securely with external contractors. Administrators can define custom workspace teams with granular role-based access controls, track change audit logs across configuration histories, and navigate management views using a keyboard-driven command palette. Automated schema validation engines detect missing parameters and enforce uniform uppercase naming standards across application tiers. 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.