Huginn screenshot thumbnail

Huginn

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.

Deploy
Open Connector screenshot thumbnail

Open Connector

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.

Deploy
Sim Studio screenshot thumbnail

Sim Studio

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.

Deploy
Executor screenshot thumbnail

Executor

Connect your services once and let every AI agent use them through a single MCP endpoint, without a credential ever reaching the agent. Executor packages each integration as an app: a small TypeScript program that turns saved accounts into tools. Install one from a catalog of more than 1,800 ready-made apps, add a remote MCP server by URL, or have your agent write and deploy a new one. Agents get two tools, skills and execute, so they search for what they need and run a short program across as many apps as a task takes. Each tool decides when to ask first: always, never, or only when the input looks risky, and you approve in your agent, your MCP client, or a browser page. The dashboard shows every app with its tools, skills, workflows, schedules, webhooks, source files, and version history, and every deploy can be rolled back. Connections give each agent its own MCP URL that reaches only the apps you pick, with copy-paste setup steps for Claude, ChatGPT, Codex, and others. Organizations, groups, invitations, shared accounts, and optional single sign-on cover teams. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Fynt screenshot thumbnail

Fynt

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.

Deploy
Apache EventMesh screenshot thumbnail

Apache EventMesh

Applications publish an event once and stop caring who needs it next: Apache EventMesh receives CloudEvents over plain HTTP, stores them durably, and delivers each one to every subscription that matches. Producers call publish, consumers call subscribe or unsubscribe, and the runtime owns the registry, offsets, acknowledgements, and redelivery that messaging clients usually force you to build yourself. Subscribers choose load-balanced delivery for competing workers, broadcast delivery for every listener, or multicast for selected groups, and they receive events by HTTP long polling, Server-Sent Events, or WebSocket push. Filters drop irrelevant events before they leave the mesh, while transformers reshape payloads so a producer and consumer can disagree about format without either one changing code. Kafka and RocketMQ act as pluggable write-ahead storage, with an in-memory backend for development, and stateless runtime instances scale horizontally without consumer-group rebalancing. Twenty-three connectors move events into and out of RabbitMQ, Pulsar, MongoDB, MySQL change data capture, Redis, S3, Prometheus, Slack, DingTalk, Lark, WeChat, and AI services, each checkpointing offsets so failures replay instead of silently losing data. Agent-to-Agent protocol support and MCP connectors let AI agents exchange asynchronous events alongside synchronous tool calls, and event-triggered agents can publish decisions back into the mesh for downstream delivery. 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.

Deploy
ByteChef screenshot thumbnail

ByteChef

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.

Deploy