Categories
Self-Hosted AI Agents MCP RAG Workflow Automation Low-Code Integration Platform Workflow EngineStars
Forks
Watchers
Developer links
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.
Benefits
- Agents That Resume After Failures
- Each task execution is persisted in PostgreSQL by the Atlas runtime, so a run that fails, stops, or waits for approval resumes from the task it reached instead of restarting.
- Connectors That Double As Tools
- Every connector is also an agent tool and an MCP tool, so the same Gmail, HubSpot, or Slack step serves a fixed workflow and an agent deciding at runtime.
- Deterministic Logic Beside AI Decisions
- Conditions, loops, parallel branches, subflows, and approval pauses share one graph with the model, so predictable logic and AI judgment stay in a single reviewable workflow.
- Self-Host With One Docker Command
- A single Docker container starts ByteChef on port 8080 with an embedded database for evaluation, and the Docker Compose file adds PostgreSQL for installations you plan to keep.
Features
- Visual Workflow Editor
- A drag-and-drop canvas with data pills for mapping values between steps, a properties panel for every step, and the workflow kept as JSON underneath.
- AI Agent Component
- One workflow node combines a chat model from OpenAI, Anthropic, Mistral, or Ollama with chat memory, knowledge-base retrieval, and tools, and streams structured output.
- MCP In Both Directions
- Consumes external MCP servers as tool sources and exposes your workflows as an MCP server behind API-key authentication for Claude Desktop, Cursor, and Windsurf.
- Durable Execution Engine
- The Atlas runtime persists each task in PostgreSQL, resumes stopped or approval-paused runs, and scales out with queue modes for Redis, RabbitMQ, Kafka, JMS, AMQP, or SQS.
- Knowledge Bases and RAG
- Native document ingestion and chunking feed vector stores such as pgvector, Pinecone, Qdrant, Weaviate, and Milvus, with modular and question-answer RAG patterns available as components.
- Built-In Data Tables
- Typed relational tables with string, number, integer, boolean, date, and date-time columns, a spreadsheet-like grid, CSV import and export, and a workflow component for reading and writing records.