agentboards.org
Compare/AutoGen vs Flowise

AutoGenvsFlowise

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

AutoGen
Microsoft · Agent framework
OSSMCP
Panel
4.5
6 spec wins
Reliability
4.8
Usefulness
4.3
Cost
6.3
Longevity
2.7

“The docs are CC-BY-4.0, so you may freely redistribute the notice telling you to use something else.”

Flowise
FlowiseAI · Agent framework
OSSMCP
Panel
3.9
0 spec wins
Reliability
4.0
Usefulness
4.5
Cost
5.7
Longevity
1.3

“The global npm install still resolves, which is currently the most reliably maintained thing about it.”

Spec by spec

SpecAutoGenFlowise
Architecture
CategoryAgent frameworkAgent framework
Runslocallocal, cloud
Platformsmacos, linux, windowsmacos, linux, windows, web
Context windownot documentednot documented
Protocols
MCP clientYesYes
MCP serverNoNo
Capabilities
Runs terminal commandsYesNo
Multi-file editsNoNo
Git operationsNoNo
Browser controlYesNo
Sandboxed executionYesNo
Multi-agent orchestrationYesYes
Headless / CI modeYesNo
Models
BackboneOpenAI, Azure OpenAI, any autogen-ext model clientany
Bring your own modelYesYes
Local modelsYesYes
Cost
Pricing modelbyokmixed
Starts at$0/mo$35/mo
Free tierYesYes
Bring your own keyYesYes
Openness
Open sourceYesYes
LicenseMITApache-2.0
GitHub stars61,25355,494

Which one would each critic pick

CriticAutoGenFlowisePick
El Juez——not enough reviews
El Amigo4.53.8AutoGen — Do not adopt AutoGen for new work; Microsoft has put it in maintenance mode and points you elsewhere, so pick LangGraph or smolagents if you are starting an agent today.
El Crítico4.03.3AutoGen — The readme states AutoGen is in maintenance mode, will not receive new features or enhancements, and is community managed going forward; that sentence is the whole risk.
El Profesor5.04.0AutoGen — Four layers, core, agentchat, ext and Studio, over an event-driven runtime with local and distributed modes, and code execution delegated to Docker; the design outlived its maintainers.
La Inversora3.83.8no preference
La Jefa4.03.3AutoGen — As a dependency it has no vendor support, no roadmap and no SLA, which for sixty engineers means a migration project we did not budget; not yet, and plan the exit.
El Hacker6.05.3AutoGen — MIT code, McpWorkbench for MCP, any autogen-ext model client including local ones, and the fork already happened: the original maintainers ship the 0.2 line as AG2 under Apache-2.0.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.