A BPMN-based Multi-Agent Orchestration Framework for the Enterprise
Process GPT is an open-source platform that combines the 30-year-proven BPMN (Business Process Model and Notation) international standard with the autonomy of modern AI agents. It lets non-technical users design business processes in natural language, lets multiple specialized agents collaborate to execute them, and continuously learns from feedback to make every future run better.
Where classic BPM requires code and specialists, and pure agent frameworks (CrewAI, LangGraph, AutoGen, Swarm/OpenAI SDK) leave you without visual processes, audit trails, or compensation semantics — Process GPT sits at the intersection: visual + code + standards-based, engineered for production.
Online Service 🌐 www.process-gpt.io
-
Flexible and Robust Collaboration via Multi-Agent Systems — Process GPT configures multiple AI agents to collaborate within a single BPMN-based business process, so that multiple agent frameworks can professionally handle complex tasks and share intermediate results. This reliably automates high-complexity work that would be difficult for a single agent. Each agent leverages specialized domain knowledge and tools, and can automatically call upon other specialized agents to delegate tasks when necessary.
-
Automated Business Process Generation — Process GPT is designed to let AI agents automatically define business processes, producing results without constant human instruction or manual execution of every step. This minimizes human intervention, embodying the ambient agent philosophy, and ensures that human involvement does not become a bottleneck.
-
Natural-Language-Based Continuous Process Learning and Optimization — Non-expert users can define business processes using natural language, which automatically generates initial process models. An automatic optimization cycle analyzes user feedback and agent execution logs, continuously improving processes and augmenting training data for workflows that need correction.
-
Deterministic Regularization of AI Decisions — When agents repeatedly make the same kind of judgment, Process GPT automatically converts it into a DMN decision table or Python rule, guaranteeing that "same input = same output" for enterprise-critical paths while keeping AI flexibility for exceptions.
-
Enterprise-Grade Reliability — BPMN Compensation Events provide automatic rollback and compensating transactions on failure. Human-in-the-Loop is a native BPMN pattern, not a workaround. Every step is auditable against an ISO/IEC 19510 process model.
- Framework-agnostic Multi-Agent System — powered by LangChain Deepagents, CrewAI, and more; pick the best runtime per task
- BPMN-based Hybrid Process Execution — deterministic (DMN/code) and stochastic (LLM reasoning) modes in one diagram
- Collaborative Work via the Agent-to-Agent (A2A) Protocol — agents discover and negotiate with each other through Agent Cards
- Isolated Agent/Tool Execution — each MCP and A2A server runs in its own container, orchestrated on Kubernetes with KEDA queue-based autoscaling and a Sidecar isolation pattern
- Skill Self-Learning & Feedback Loops — agents improve their own Skills through a Think → Execute → Reflect cycle driven by user feedback
- Context Engineering — Mem0 + Neo4j knowledge graph + Memento RAG service give agents deep organizational context
- Voice & Realtime Channels — GPT-4 Realtime API + Twilio PSTN integration for voice-driven process triggers
- Process Marketplace — share and reuse verified process templates across teams and organizations
- Integrations — Browser-use, OpenAI Deep Research, Supabase (Postgres, Realtime, Storage, Auth), ERP/CRM via MCP, N8n (coming soon)
| Layer | Role | Key Components |
|---|---|---|
| UI & Gateway | User entry & routing | Vue 3 Frontend, React Voice Agent, Nginx / Spring Cloud Gateway |
| Core Process | BPMN definition, instance lifecycle, polling | Execution Engine (FastAPI), Polling Service |
| Knowledge & RAG | Document parsing, embedding, retrieval | Memento (Supabase vector DB, Google Drive ingestion) |
| AI Agents | Task execution | CrewAI Action, CrewAI Deep Research, OpenAI Deep Research, Browser-Use, BPMN Extractor |
| Infrastructure | State, events, storage, auth | Supabase (Postgres, Realtime, Storage, Auth), Docker Compose / Kubernetes |
Process GPT is the only player in the "BPMN + AI Hybrid" category — purpose-built for enterprises that need the governance of BPM and the autonomy of modern agents at the same time.
| ProcessGPT | CrewAI / LangGraph / AutoGen | Dify.ai / n8n | Google ADK / AWS Bedrock | |
|---|---|---|---|---|
| Orchestration | BPMN visual modeling | Code-based roles/graphs | Visual low-code | Console / blueprint |
| Determinism | DMN + Python auto-conversion | None | Conditional nodes | Guardrails only |
| Agent-to-Agent | A2A + event-driven | Sequential / group chat | N/A | A2A (Google) / internal |
| Self-learning | Skills + feedback loop | Memory only | None | None |
| Compensation | BPMN Compensation Events | None | Basic error branches | None |
| Autoscaling | KEDA + Sidecar | Manual | Manual | Managed (vendor-locked) |
| Non-developer access | High (NL + visual) | Low (code) | High | Medium |
| Deployment | Open source, multi-cloud, on-prem | Library-level | SaaS / self-host | Cloud-locked |
- Enterprises modernizing legacy BPM — keep your BPMN assets, add AI autonomy
- Regulated industries — finance, healthcare, public sector where audit trails and compliance are non-negotiable
- Citizen developers — business users automating their own work in natural language, no coding required
- AI teams building production agents — skip the infrastructure rebuild; get K8s-native isolation, scaling, and observability out of the box
- Website: process-gpt.io
- Documentation: docs.process-gpt.io
- SaaS: try it instantly at process-gpt.io
- Self-host: clone process-gpt-infra-docker and run
docker compose upto deploy the full local-dev stack; Kubernetes manifests included for production
Process GPT creates a new category — "the BPMN of AI agents" — and sets the standard for enterprise multi-agent orchestration.
Maintained by uEngine Solutions · learning@uengine.org
- API gateway: GitHub
- frontend: GitHub
- completion: GitHub
- memento (Document Memory Storage): GitHub
- base-agent-langchain-react: GitHub
- deepagents: GitHub
- deep-research: GitHub
- openai-deep-research (OpenAI-based Deep Research Agent): GitHub
- a2a-orch: GitHub
- react-voice-agent (Voice Interaction Agent): GitHub
- agent-feedback: GitHub
- mcp-validator: GitHub
- bpmn-extractor (ProcessGPT BPMN extractor from PDFs): GitHub
- computer-use: GitHub
- office-mcp: GitHub
- analytic GitHub
- strategy GitHub
- instance-classifier GitHub
- Robo Architect: GitHub
Users should be able to declare and modify processes, rules, system integration mechanisms, etc. in natural language, and the system should automatically improve with minimal feedback provided during use.
All such changes must be logged for tracking and recovery, while users should simultaneously be able to directly control automation results and regulations through a generalized UI at any time.
- All process definitions, rules, system integrations, and business interfaces should be writable in natural language without requiring programming knowledge or complex logical/mathematical thinking.
- Users should be able to design automation with business objective or strategic-level descriptions alone, without undergoing separate training processes.
- The system should be progressively refined and managed through minimal feedback (approval, modification, rejection) provided during actual use.
- Automated agents must provide human interfaces that allow people to substitute and perform tasks at any time.
- Each task should provide necessary context (related data, previous step outputs, similar cases) in a clear and organized manner to facilitate human processing.
- Agents learn from actual performance examples where humans directly handle tasks, correcting and improving their execution knowledge. In other words, human exemplars become the agent's training data.
- When errors or failures occur in automated processes performed by agents, recovery should be automatically implemented through compensating transactions (rollback).
- Operators should not need to track and correct agent details individually; the system itself should take responsibility for failure recovery and processing.
- This liberates users from system imperfections and ensures overall business continuity.
This repo is a meta-project: every microservice listed above lives as a Git
submodule under services/, application code stays locally in the root
project, and the local-install assets (Docker Compose, nginx, env, DB init)
live in the process-gpt-infra-docker submodule.
Local install files live in a separate repo. Docker Compose files and configs for local-dev installation are maintained in process-gpt-infra-docker and vendored here as a submodule at
process-gpt-infra-docker/. See Running the Stack with Docker Compose below, or the standalone Local Installation Guide.
process-gpt/
├── .gitmodules # Submodule definitions (auto-managed)
├── .env.example # Shared env template (reference copy)
│
├── scripts/
│ ├── init-submodules.sh # One-shot service-submodule add (Bash)
│ └── init-submodules.ps1 # One-shot service-submodule add (PowerShell)
│
├── process-gpt-infra-docker/ # Local install assets (submodule — separate repo)
│ ├── docker-compose.yml # Full stack: infra + microservices + gateway
│ ├── nginx/nginx.conf
│ ├── litellm_config.yaml
│ ├── .env.example
│ ├── volumes/ # db / api / functions / email-templates / pooler
│ ├── start-all-services.sh/.ps1 # Interactive launcher (Bash + PowerShell)
│ ├── stop-all-services.sh/.ps1 # Stop / teardown helpers
│ └── services/ # Same microservices, vendored for `build:` targets
│
└── services/ # All subprojects (submodules — external repos)
├── frontend/ # process-gpt-vue3
├── completion/ # process-gpt-completion
├── memento/ # process-gpt-memento
├── base-agent-langchain-react/
├── deepagents/
├── agent-feedback/
├── mcp-validator/
├── a2a-orch/
├── bpmn-extractor/
├── computer-use/
├── deep-research/
├── openai-deep-research/
├── office-mcp/
├── analytic/
├── instance-classifier/
├── strategy/
└── react-voice-agent/
# Fresh clone (one shot) — includes process-gpt-infra-docker and services/*
git clone --recurse-submodules https://github.com/uengine-oss/process-gpt.git
# Already cloned? Fetch the submodules:
cd process-gpt
git submodule update --init --recursiveIf you only want to run the app locally with Docker Compose (no need to touch
process-gptsource at all), you can skip this repo entirely and clone process-gpt-infra-docker directly — see the Local Installation Guide.
Re-run the initializer (idempotent; existing submodules are skipped):
# Linux / macOS / Git Bash
./scripts/init-submodules.sh
# Windows PowerShell
.\scripts\init-submodules.ps1To pull the latest commit of every submodule:
git submodule update --remote --mergeAll Docker Compose assets (compose file, nginx, env template, DB init SQL,
launcher scripts) live in the process-gpt-infra-docker submodule, not in
this repo's root. Initialize it, then run everything from inside it:
git submodule update --init process-gpt-infra-docker
cd process-gpt-infra-docker
cp .env.example .env
# Open .env and fill in: LLM API keys, secrets, host IP, SMTP, etc.
./start-all-services.sh # Linux / macOS / Git Bash
.\start-all-services.ps1 # Windows PowerShellThe launcher prompts you to start all services, infra only, or pick
individual microservices, brings up infra (Supabase, Postgres, Neo4j,
LiteLLM) first with --wait, then the selected services and the nginx
gateway. It also remembers your last selection and supports named presets
(--last, --save-as, --preset).
Default ports once running:
| Service | URL |
|---|---|
| Gateway (Nginx) | http://localhost:8088 |
| Completion | http://localhost:8000 |
| Memento | http://localhost:8005 |
| Supabase Kong | http://localhost:54321 |
| Supabase Studio | http://localhost:`${STUDIO_PORT}` (3001 default) |
| Neo4j Browser | http://localhost:7474 |
Full command reference (start/stop options, profiles, troubleshooting) is in
the Local Installation Guide and in
process-gpt-infra-docker's own README.
Please refer to the Local Installation Guide.