Comparison
Flowise vs sre
Verdict
Pick Flowise if flowise is a visual tool for building AI agents, supporting low-code and no-code development. It enables users to create complex workflows and multi-agent systems through a user-friendly interface; pick sre if smythOS Runtime Environment (SRE) is a TypeScript-based open-source runtime framework designed for developing, managing and running intelligent agents in various environments.
Markdown twin · Flowise alternatives · sre alternatives
GraphCanon updated Sep 20, 2026
17views this month
Trust & integrity
| Signal | Flowise | sre |
|---|---|---|
| Maintenance | Archived (35d since push) As of Sep 18, 2026 · github_public_v1 | Slowing (170d since push) As of Sep 20, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 18, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Sep 18, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- Flowise
- Build AI Agents, Visually
- sre
- Cloud-native runtime for building, running, and managing intelligent agents
Stars
- Flowise
- 55k
- sre
- 1.3k
Forks
- Flowise
- 25k
- sre
- 202
Open issues
- Flowise
- 1.0k
- sre
- 35
Language
- Flowise
- TypeScript
- sre
- TypeScript
Adopt for
- Flowise
- Flowise is a visual tool for building AI agents, supporting low-code and no-code development. It enables users to create complex workflows and multi-agent systems through a user-friendly interface.
- sre
- SmythOS Runtime Environment (SRE) is a TypeScript-based open-source runtime framework designed for developing, managing and running intelligent agents in various environments.
Persona
- Flowise
- -
- sre
- -
Runtime
- Flowise
- -
- sre
- -
License
- Flowise
- Other
- sre
- MIT
Last pushed
- Flowise
- Aug 13, 2026
- sre
- Apr 3, 2026
Categories
- Flowise
- AI Agents, Developer Tools
- sre
- AI Agents
Trust and health
Maintenance
- Flowise
- Archived (8%)
- sre
- Slowing (36%)
Days since push
- Flowise
- 35d
- sre
- 170d
Archived on GitHub
- Flowise
- Yes
- sre
- No
Open issues (now)
- Flowise
- 1.0k
- sre
- 35
Stars delta
- Flowise
- +219 (30d)
- sre
- +2 (30d)
Open issues delta
- Flowise
- -5 (30d)
- sre
- +1 (30d)
Full report
- Flowise
- Trust report
- sre
- Trust report
Typed relationship
Flowise sre
Shared compatibility
- Node.js · Flowise: Node.js runtime · sre: Node.js runtime
Choose Flowise if…
- License: Flowise is Other, sre is MIT.
- Graph edge: Flowise is a typed related of sre - see the relationship row above.
- Tags unique to Flowise: agentic-ai, agentic-workflow, agents, artificial-intelligence.
- Also covers Developer Tools.
- Flowise ships Docker support for self-hosted deployment.
- When you need a tool that supports both low-code and no-code development for AI agents.
When NOT to use Flowise
- If you prefer a tool that does not require NodeJS >= 20.0.0 for installation and operation.
- When you need a solution that does not rely on Docker for deployment, as Flowise requires Docker for certain deployment methods.
- If you are working in an environment where the Apache License Version 2.0 is not compatible with your project's licensing requirements.
Choose sre if…
- License: sre is MIT, Flowise is Other.
- Graph edge: sre is a typed related of Flowise - see the relationship row above.
- Tags unique to sre: agent-framework, agi, autonomous-agents, multi-agent-systems.
- Use SRE if you are working with agentic AI projects that need to be deployed across multiple environments such as local, cloud, or edge locations.
When NOT to use sre
- Avoid SRE if the project requirements are focused on languages other than TypeScript as it is specifically built with TypeScript in mind.
- If your use case prioritizes immediate access to a mature and widely supported SDK over an open-source framework, another tool might offer more comprehensive support out of the box.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (FlowiseAI/Flowise) · observed Sep 20, 2026
- GitHub forks (FlowiseAI/Flowise) · observed Sep 20, 2026
- Last push (FlowiseAI/Flowise) · observed Aug 13, 2026
- License file (Other) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Sep 18, 2026
- Trust scan (lockfile / OSV) · observed Sep 18, 2026
- GitHub stars (SmythOS/sre) · observed Sep 20, 2026
- GitHub forks (SmythOS/sre) · observed Sep 20, 2026
- Last push (SmythOS/sre) · observed Apr 3, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: Flowise 55k · sre 1.3k (synced Sep 20, 2026).
Common questions
- What is the difference between Flowise and sre?
- Flowise: Build AI Agents, Visually. sre: Cloud-native runtime for building, running, and managing intelligent agents. See the comparison table for live GitHub stats and shared categories.
- When should I choose Flowise over sre?
- Choose Flowise over sre when License: Flowise is Other, sre is MIT; Graph edge: Flowise is a typed related of sre - see the relationship row above; Tags unique to Flowise: agentic-ai, agentic-workflow, agents, artificial-intelligence; Also covers Developer Tools; Flowise ships Docker support for self-hosted deployment; When you need a tool that supports both low-code and no-code development for AI agents.
- When should I choose sre over Flowise?
- Choose sre over Flowise when License: sre is MIT, Flowise is Other; Graph edge: sre is a typed related of Flowise - see the relationship row above; Tags unique to sre: agent-framework, agi, autonomous-agents, multi-agent-systems; Use SRE if you are working with agentic AI projects that need to be deployed across multiple environments such as local, cloud, or edge locations.
- When should I avoid Flowise?
- If you prefer a tool that does not require NodeJS >= 20.0.0 for installation and operation. When you need a solution that does not rely on Docker for deployment, as Flowise requires Docker for certain deployment methods. If you are working in an environment where the Apache License Version 2.0 is not compatible with your project's licensing requirements.
- When should I avoid sre?
- Avoid SRE if the project requirements are focused on languages other than TypeScript as it is specifically built with TypeScript in mind. If your use case prioritizes immediate access to a mature and widely supported SDK over an open-source framework, another tool might offer more comprehensive support out of the box.
- Is Flowise or sre more popular on GitHub?
- Flowise has more GitHub stars (55,465 vs 1,293). Stars measure visibility, not whether either tool fits your constraints.
- Are Flowise and sre open source?
- Yes - both are open-source projects on GitHub (Flowise: Other, sre: MIT).
- Where can I find alternatives to Flowise or sre?
- GraphCanon lists graph-backed alternatives at Flowise alternatives and sre alternatives (Flowise markdown twin, sre markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, Flowise or sre?
- Flowise: Archived. sre: Slowing. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for Flowise and sre?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: Flowise trust report; sre trust report.