Softwr

Automation Integration · head to head

Camunda vs Nango

Camunda logo

Camunda

Automation Integration

BPMN process orchestration engine, now source-available rather than open source

From
On request
Rated
-
Full reviewWebsite
Nango logo

Nango

Automation Integration

Open source unified API and OAuth infrastructure for product integrations, licensed under Elastic License 2.0

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Nango has a free tier, so it costs nothing to try first.
  • Each has a real cost: Camunda camunda 7 Community Edition stopped receiving security patches after the 7.24 release in October 2025, so free production deployments are now running unpatched software.; Nango the licence is Elastic License 2.0, which is source available rather than OSI open source, and it forbids offering Nango to third parties as a managed service, so anyone planning to resell or embed it in a platform for their own customers has a genuine legal problem.
  • They diverge on capability: Camunda covers BPMN 2.0 execution, Nango covers Managed OAuth.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Camunda and Nango actually diverge.

Attributes where Camunda and Nango differ
AttributeCamundaNango
Starting priceOn requestFree
Pricing modelquotePer connection per month
Free tierNoYes
PlatformsWeb, Linux, Docker, KubernetesWeb, Linux, Docker

Identical on both: user rating (Not yet rated), category (Automation Integration).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Camunda

  • BPMN 2.0 execution
  • DMN decision tables
  • Zeebe engine
  • Operate console
  • Job workers
  • Optimize

Only in Nango

  • Managed OAuth
  • Pre-built integrations
  • Custom syncs and actions
  • Incremental sync
  • Rate limit and retry handling
  • Webhooks
  • Self-hosting
  • Unified models

What people use each for

The jobs each tool is most often brought in to do.

Camunda

  • Long-running business processes crossing several services where the state must be visible to non-developersnot Nango
  • Insurance claims or loan origination where the process model is itself a compliance artefactnot Nango
  • Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot Nango
  • A regulated organisation that needs an auditable record of how each process instance actually executednot Nango

Nango

  • A SaaS product that needs to ship twenty customer-facing integrations without hiring a team to maintain OAuth and token refresh for eachnot Camunda
  • A team that needs a niche or internal API integrated, which closed unified API vendors will not build for themnot Camunda
  • A company with data residency or security constraints that must self-host the integration layer rather than send customer tokens to a vendornot Camunda
  • An engineering team replacing a homegrown integration service whose main cost is silent token expiry and rate limit failures in productionnot Camunda

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Camunda

  • Camunda 7 Community Edition stopped receiving security patches after the 7.24 release in October 2025, so free production deployments are now running unpatched software.
  • Camunda 8 Self-Managed is source-available under the Camunda License 1.0, not open source: production use requires a paid licence, and organisations that adopted Camunda for its Apache licence have to renegotiate that decision.
  • Migrating from Camunda 7 to 8 is a rewrite rather than an upgrade because the engine, the API and the persistence model all changed, and there is no in-place migration for running instances.
  • Camunda 8 Self-Managed has substantial infrastructure requirements including Zeebe brokers, Elasticsearch and Identity, which is a considerable operations burden compared with the single database that Camunda 7 needed.
  • Pricing is not published at all, so evaluating total cost requires a sales process, and there is no way to size a budget before committing engineering time to a proof of concept.

Nango

  • The licence is Elastic License 2.0, which is source available rather than OSI open source, and it forbids offering Nango to third parties as a managed service, so anyone planning to resell or embed it in a platform for their own customers has a genuine legal problem.
  • Pricing is per connection where a connection is one authorised end-user account, so cost scales linearly with your customer base and a product where each user links several services multiplies quickly beyond what a headline plan price suggests.
  • Pre-built integrations vary in depth, and a connection that exists is not the same as a connection that covers the endpoints and objects your feature needs, so each one must be verified before it is designed into a roadmap.
  • Custom syncs are written in TypeScript and run in Nango model, which means integration logic lives in a vendor runtime and migrating away later requires rewriting it rather than lifting it out.
  • Self-hosting removes the vendor from the data path but transfers operational responsibility for a component that holds customer OAuth tokens, and few teams appreciate the security burden that comes with running that themselves.

Pricing, plan by plan

Camunda

On request
  • Camunda 8$undefined/year
    • Self-Managed under Camunda License 1.0, production licence required
    • SaaS with a thirty day full trial
    • Free unlimited BPMN and DMN modelling after the trial

Nango

Free
  • FreeFree
    • 10 connections
    • Pre-built integrations
    • Managed OAuth
  • Starter$50/month
    • 20 connections included
    • 1 USD per additional connection
    • Custom syncs and actions
  • Growth$500/month
    • 100 connections included
    • 1 USD per additional connection
    • Higher limits
  • Enterprise$undefined/month
    • Quoted
    • Custom connection volumes
    • Security review and SLA

Which should you pick?

Choose Camunda if

  • You need bpmn 2.0 execution.
  • You work on Web, Linux, Docker, Kubernetes.
  • You also want dmn decision tables.
Camunda review

Choose Nango if

  • You need managed oauth.
  • You want to start without paying.
  • You work on Web, Linux, Docker.
  • You also want pre-built integrations.
Nango review

Questions people ask

Is Camunda or Nango better?
Neither clearly leads. Camunda starts at On request and Nango at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Camunda or Nango?
Nango has a free tier; the other does not. Paid plans start at On request for Camunda and Free for Nango.
Does Camunda or Nango run on more platforms?
Camunda runs on Web, Linux, Docker, Kubernetes. Nango runs on Web, Linux, Docker.
Can I use Nango for free?
Yes. Nango has a free tier, so you can try it without paying. Camunda starts at On request.
What is Camunda best used for?
Camunda is most often used for long-running business processes crossing several services where the state must be visible to non-developers, insurance claims or loan origination where the process model is itself a compliance artefact, replacing orchestration logic scattered across microservices with one engine that owns the state machine, a regulated organisation that needs an auditable record of how each process instance actually executed. Of those, long-running business processes crossing several services where the state must be visible to non-developers and insurance claims or loan origination where the process model is itself a compliance artefact are not what Nango is typically brought in for.
What can Camunda do that Nango cannot?
Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. Nango covers Managed OAuth, Pre-built integrations, Custom syncs and actions, Incremental sync.

Answered from the vendors’ own pages

Camunda: Is Camunda still open source?

No. Camunda 8 Self-Managed ships under the Camunda License 1.0, which is source-available and requires a paid production licence.

Nango: Is Nango open source?

It is source available under Elastic License 2.0. You can read, modify and self-host it, but you cannot offer it to third parties as a managed service. That is not the same as an OSI approved open source licence.

Camunda: What happened to Camunda 7?

Its final feature release, 7.24, was in October 2025 and the Community Edition receives no further patches. Enterprise support runs to April 2030.

Nango: How is it priced?

Per connection per month, where a connection is one authorised end-user account. Free to 10 connections, 50 dollars a month for Starter with 20, 500 for Growth with 100, and one dollar per additional connection.

Camunda: Can I upgrade from 7 to 8?

Not in place. The engine, API and persistence changed, so it is a rewrite of the integration layer.

Nango: Can we integrate an API Nango does not support?

Yes. Custom syncs and actions in TypeScript cover any API including internal ones, which is the main advantage over closed unified API products.

Camunda: What does it cost?

Camunda does not publish prices. Both self-managed production and SaaS require a quote.

Nango: Can we self-host it?

Yes, under the Elastic License 2.0 terms, which permit self-hosting for your own use but not resale as a service.

Share

Related pages

More on Camunda

More on Nango

Keep looking

Other head to heads