Dynamiq vs Flowise

Flowise reached end of life on August 31, 2026; its Apache 2.0 source is archived on GitHub. Dynamiq is an actively developed, governed agent platform.

By Pawel Sobczak, Product and partnerships Updated September 29, 2026

Start free Talk to the team

In short

Flowise was an open-source visual builder for chatbots, agents and multi-agent workflows. Its team announced on July 29, 2026 that it was winding down and froze development that day, archived the GitHub repository on August 13, and reached end of life on August 31, 2026; the Apache 2.0 source stays available to self-host or fork, but npm packages and Docker images are marked deprecated. Dynamiq is an actively developed, governed platform for chat, voice and workflow agents, with a deployment team. Teams with a working Flowise install can keep it running on the archived source while they plan a move; teams choosing a platform going forward fit Dynamiq.

Side by side

Facts checked September 29, 2026. Sources below.

Dimension	Dynamiq	Flowise
Best for	Enterprises in regulated industries that need chat, voice and workflow agents on one governed stack, deployed inside their own environment.	Not a fit for new production deployments: Flowise froze development on July 29, 2026 and reached end of life on August 31, 2026, per its sunset page. The Apache 2.0 source remains for teams that already run it or want to fork it.
Deployment options	Dynamiq Cloud, or self-hosted on your AWS, Azure, GCP, IBM Cloud, Red Hat OpenShift or any Kubernetes 1.32+ cluster, or on-prem. Fully isolated or air-gapped setups are delivered with our engineers.	Self-hosted from npm, Docker, Docker Compose or Kubernetes with Helm, with guides for AWS, Azure, GCP and DigitalOcean. Its homepage still lists Flowise Cloud tiers, and the sunset page does not say what happens to them.
Self-hosted or on-prem	Yes. Self-hosted on your cloud or on-prem, or Dynamiq Cloud; both run the same engine.	Yes, and it is the only path forward: the source stays visible on GitHub indefinitely, but issues and pull requests are locked and npm packages and Docker images are marked deprecated, per Flowise's sunset page.
License and source code	The Python SDK is open source under Apache-2.0 (github.com/dynamiq-ai/dynamiq), and the visual canvas runs on the same engine. The platform around it is not open source.	Apache License 2.0, except an enterprise directory under a commercial license, per its GitHub license file; the repository was archived on August 13, 2026.
Model choice	29 model providers in the SDK, the most-used models behind one OpenAI-compatible AI Gateway endpoint, plus open models served on vLLM and LoRA fine-tuning.	100+ LLMs, embeddings and vector databases through its integrations, including OpenAI, Azure OpenAI, Anthropic, AWS Bedrock, Google Vertex AI, Mistral, Groq and Ollama.
Agent types (chat, voice, workflow)	Chat, inbound voice and workflow agents on one engine. AI Coworker works with its own cloud sandbox computer, in the browser, Slack, Microsoft Teams and Telegram; Voice Agents answer inbound calls; Agent Builder runs workflow agents.	Chatflows for chatbots and single agents with tools and RAG, and Agentflows for multi-agent workflows; no voice agent product, and with the project wound down, no new capabilities are coming.
Developer surface	Agent Builder pairs a visual canvas with the open-source Python SDK on one engine, with Choice and rules nodes, workflows generated from a prompt, and versions with rollback.	A visual flow builder with a REST API, Python and TypeScript SDKs, a CLI, an embeddable chat widget and an MCP client; the archived repository receives no further updates.
Governance (guardrails, approvals, SSO)	Guardrails that detect PII and prompt injection, policy detection, validators and approvals with editable fields on any tool step, on every plan; SSO (OIDC with Okta and Microsoft Entra ID) on Enterprise.	A Human Input node for approve or reject steps, moderation nodes, workspaces with role-based access on Cloud and Enterprise plans, and SSO with Microsoft, Google or Auth0 on its Enterprise plan.
Evals and observability	Evals with datasets built from traces, LLM-as-a-judge, predefined and code metrics, and real-time evaluations on live deployments; traces with cost and latency per node, monitoring, and an AI agent that surfaces issues from production traces.	Evaluations with text, numeric and LLM-based evaluators on Cloud and Enterprise plans, tracing integrations such as LangSmith, Langfuse, Arize and Phoenix, and Prometheus, Grafana and OpenTelemetry metrics.
Compliance	SOC 2 and CASA Tier 2, with a BAA for HIPAA workloads and a DPA under GDPR.	Not publicly documented.
Delivery help (engineers)	Forward-deployed engineers run a bootcamp in your environment, ship the first production agent with your team, then hand over.	None going forward: official core team presence in Discord and GitHub ended at end of life on August 31, 2026, per its sunset page.
Pricing model	Free to start ($0), and Enterprise with custom pricing. Available on AWS Marketplace, Microsoft Azure Marketplace and IBM Marketplace.	Its homepage still lists cloud tiers (Free, Starter at $35 a month and Pro at $65 a month), but the sunset page leaves Flowise Cloud's future unstated; the source itself is free under Apache 2.0.

Best for

DynamiqEnterprises in regulated industries that need chat, voice and workflow agents on one governed stack, deployed inside their own environment.

FlowiseNot a fit for new production deployments: Flowise froze development on July 29, 2026 and reached end of life on August 31, 2026, per its sunset page. The Apache 2.0 source remains for teams that already run it or want to fork it.

Deployment options

DynamiqDynamiq Cloud, or self-hosted on your AWS, Azure, GCP, IBM Cloud, Red Hat OpenShift or any Kubernetes 1.32+ cluster, or on-prem. Fully isolated or air-gapped setups are delivered with our engineers.

FlowiseSelf-hosted from npm, Docker, Docker Compose or Kubernetes with Helm, with guides for AWS, Azure, GCP and DigitalOcean. Its homepage still lists Flowise Cloud tiers, and the sunset page does not say what happens to them.

Self-hosted or on-prem

DynamiqYes. Self-hosted on your cloud or on-prem, or Dynamiq Cloud; both run the same engine.

FlowiseYes, and it is the only path forward: the source stays visible on GitHub indefinitely, but issues and pull requests are locked and npm packages and Docker images are marked deprecated, per Flowise's sunset page.

License and source code

DynamiqThe Python SDK is open source under Apache-2.0 (github.com/dynamiq-ai/dynamiq), and the visual canvas runs on the same engine. The platform around it is not open source.

FlowiseApache License 2.0, except an enterprise directory under a commercial license, per its GitHub license file; the repository was archived on August 13, 2026.

Model choice

Dynamiq29 model providers in the SDK, the most-used models behind one OpenAI-compatible AI Gateway endpoint, plus open models served on vLLM and LoRA fine-tuning.

Flowise100+ LLMs, embeddings and vector databases through its integrations, including OpenAI, Azure OpenAI, Anthropic, AWS Bedrock, Google Vertex AI, Mistral, Groq and Ollama.

Agent types (chat, voice, workflow)

DynamiqChat, inbound voice and workflow agents on one engine. AI Coworker works with its own cloud sandbox computer, in the browser, Slack, Microsoft Teams and Telegram; Voice Agents answer inbound calls; Agent Builder runs workflow agents.

FlowiseChatflows for chatbots and single agents with tools and RAG, and Agentflows for multi-agent workflows; no voice agent product, and with the project wound down, no new capabilities are coming.

Developer surface

DynamiqAgent Builder pairs a visual canvas with the open-source Python SDK on one engine, with Choice and rules nodes, workflows generated from a prompt, and versions with rollback.

FlowiseA visual flow builder with a REST API, Python and TypeScript SDKs, a CLI, an embeddable chat widget and an MCP client; the archived repository receives no further updates.

Governance (guardrails, approvals, SSO)

DynamiqGuardrails that detect PII and prompt injection, policy detection, validators and approvals with editable fields on any tool step, on every plan; SSO (OIDC with Okta and Microsoft Entra ID) on Enterprise.

FlowiseA Human Input node for approve or reject steps, moderation nodes, workspaces with role-based access on Cloud and Enterprise plans, and SSO with Microsoft, Google or Auth0 on its Enterprise plan.

Evals and observability

DynamiqEvals with datasets built from traces, LLM-as-a-judge, predefined and code metrics, and real-time evaluations on live deployments; traces with cost and latency per node, monitoring, and an AI agent that surfaces issues from production traces.

FlowiseEvaluations with text, numeric and LLM-based evaluators on Cloud and Enterprise plans, tracing integrations such as LangSmith, Langfuse, Arize and Phoenix, and Prometheus, Grafana and OpenTelemetry metrics.

Compliance

DynamiqSOC 2 and CASA Tier 2, with a BAA for HIPAA workloads and a DPA under GDPR.

FlowiseNot publicly documented.

Delivery help (engineers)

DynamiqForward-deployed engineers run a bootcamp in your environment, ship the first production agent with your team, then hand over.

FlowiseNone going forward: official core team presence in Discord and GitHub ended at end of life on August 31, 2026, per its sunset page.

Pricing model

DynamiqFree to start ($0), and Enterprise with custom pricing. Available on AWS Marketplace, Microsoft Azure Marketplace and IBM Marketplace.

FlowiseIts homepage still lists cloud tiers (Free, Starter at $35 a month and Pro at $65 a month), but the sunset page leaves Flowise Cloud's future unstated; the source itself is free under Apache 2.0.

Choose Dynamiq when

Actively developed and supported: one engine for chat, voice and workflow agents, with a roadmap rather than a frozen codebase.
Guardrails, approvals, evals (including real-time) and observability with AI issue discovery are part of the same platform, not bolted on.
Runs inside your environment: Dynamiq Cloud, or self-hosted on your AWS, Azure, GCP, IBM Cloud, OpenShift or any Kubernetes 1.32+ cluster, or on-prem, with isolated setups delivered with our engineers.
Forward-deployed engineers ship the first production agent with your team, then hand over. Your team keeps the code and the environment.

Choose Flowise when

Teams with a working Flowise deployment can keep running it on the Apache 2.0 source while they plan a migration.
Teams willing to fork and maintain the codebase themselves keep a familiar visual builder with LangChain and LlamaIndex integrations.
The archived source is a complete reference for existing chatflows and agentflows during a migration.

Moving from Flowise

Chatflows and Agentflows built in Flowise are rebuilt as agents and workflows in Dynamiq's Agent Builder, on the canvas or in the Python SDK, since the archived repository receives no updates. Tool nodes and API integrations reconnect as Dynamiq integrations or MCP servers, document stores and vector store configuration are re-ingested into Dynamiq Knowledge, and Human Input steps become Dynamiq approvals. Because Flowise reached end of life on August 31, 2026, teams still running it are migrating off a fixed, unmaintained version rather than a moving target.

Questions and answers

Is Flowise still actively maintained?

No. Flowise announced on July 29, 2026 that it was winding down and stopped feature development and pull request reviews that day, archived its GitHub repository on August 13, 2026, and reached end of life on August 31, 2026, per its sunset page and GitHub. Its Apache 2.0 source remains on GitHub.

Can I still self-host Flowise after its end of life?

Yes. Flowise's sunset page says the source stays visible indefinitely and encourages teams to fork it, but issues and pull requests are locked and npm packages and Docker images are marked deprecated, so any fixes are up to you or a community fork.

Why did Flowise wind down?

Its sunset page says developers increasingly rely on coding agents for complex tasks, and that rigid low-code workflows quickly hit their limits. Dynamiq pairs a visual canvas with an open-source Python SDK on one engine, so teams can build visually, in code or both.

Is Dynamiq actively developed and supported?

Yes. Dynamiq is under active development, with forward-deployed engineers who ship your first production agent with your team and hand it over. Dynamiq holds SOC 2 and CASA Tier 2, and signs a BAA for HIPAA workloads and a DPA under GDPR.

What happens to a Flowise deployment if I migrate to Dynamiq?

Flows, tools and knowledge sources move to Dynamiq's Agent Builder, integrations or MCP servers, and Dynamiq Knowledge respectively; the original Flowise source remains available under Apache 2.0 if you need to reference it during the migration.

Sources

More comparisons

See how Dynamiq compares on your use case.

Bring your requirements. Our engineers will show you the differences that matter for your environment.

Start free Talk to the team