Softwr

Automation Integration · head to head

Nango vs Umami

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
Umami logo

Umami

Marketing

Open source, cookie-free web analytics you can self-host for the cost of a database

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Umami there is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • They diverge on capability: Nango covers Managed OAuth, Umami covers Cookie-free tracking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nango and Umami actually diverge.

Attributes where Nango and Umami differ
AttributeNangoUmami
Pricing modelPer connection per monthPer month by event count
PlatformsWeb, Linux, DockerWeb, Linux
CategoryAutomation IntegrationMarketing

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Nango

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

Only in Umami

  • Cookie-free tracking
  • Small tracking script
  • Custom events
  • Funnels and goals
  • Multi-site and teams
  • Public dashboards
  • API access

Both cover

  • Self-hosting

What people use each for

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

Nango

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

Umami

  • A developer who wants traffic numbers on a personal or client site without adding a consent bannernot Nango
  • An organisation whose legal or procurement team has ruled out sending visitor data to a US advertising companynot Nango
  • A high-traffic site where hosted analytics priced by pageview band has become expensive and self-hosting removes the ceiling entirelynot Nango
  • A team that wants analytics data in a database they already control so they can query and join it themselvesnot Nango

Where each one falls short

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

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.

Umami

  • There is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • Self-hosting is only free in licence terms; you own the database, the upgrades, the backups and the query performance at scale, and a busy site's events table grows quickly enough to need real attention.
  • Because it stores no persistent identifier, it cannot follow a user across devices or sessions in any meaningful way, which makes returning-visitor and lifetime-value questions unanswerable by design rather than by omission.
  • Cloud overage is billed per event beyond the plan allowance, so a traffic spike or a badly instrumented custom event can produce a bill materially above the $20 or $200 headline before anyone notices.
  • It is maintained by a small team, so the pace of new capability is modest and enterprise expectations such as SSO, granular role permissions and formal support agreements are limited compared with commercial analytics vendors.

Pricing, plan by plan

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

Umami

Free
  • Self-hostedFree
    • MIT licensed, no licence fee
    • No event limit imposed by the software
    • Unlimited websites and users
  • Cloud HobbyFree
    • Up to 100,000 events per month
    • 3 websites
    • 6 months data retention
  • Cloud Pro$20/month
    • Up to 1,000,000 events per month
    • Unlimited websites
    • Unlimited team members
  • Cloud Business$200/month
    • Up to 10,000,000 events per month
    • All Pro features
    • Higher volume overage rate

Which should you pick?

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

Choose Umami if

  • You need cookie-free tracking.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want small tracking script.
Umami review

Questions people ask

Is Nango or Umami better?
Neither clearly leads. Nango starts at Free and Umami at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nango or Umami?
Nango starts at Free and Umami at Free.
Does Nango or Umami run on more platforms?
Nango runs on Web, Linux, Docker. Umami runs on Web, Linux.
Can I use Nango for free?
Both have a free tier, so you can try either at no cost before committing.
What is Nango best used for?
Nango is most often used for a saas product that needs to ship twenty customer-facing integrations without hiring a team to maintain oauth and token refresh for each, a team that needs a niche or internal api integrated, which closed unified api vendors will not build for them, a company with data residency or security constraints that must self-host the integration layer rather than send customer tokens to a vendor, an engineering team replacing a homegrown integration service whose main cost is silent token expiry and rate limit failures in production. Of those, a saas product that needs to ship twenty customer-facing integrations without hiring a team to maintain oauth and token refresh for each and a team that needs a niche or internal api integrated, which closed unified api vendors will not build for them are not what Umami is typically brought in for.
What can Nango do that Umami cannot?
Nango covers Managed OAuth, Pre-built integrations, Custom syncs and actions, Incremental sync. Umami covers Cookie-free tracking, Small tracking script, Custom events, Funnels and goals. Both handle Self-hosting.

Answered from the vendors’ own pages

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.

Umami: Is Umami really free?

Self-hosted, yes; it is MIT licensed with no event cap. You pay for the server and database. Umami Cloud has a free tier at 100,000 events a month and paid tiers from $20.

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.

Umami: Do I need a cookie consent banner?

For Umami analytics specifically, generally no, because it sets no cookies and stores no personal data. Other tags on your site may still require one.

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.

Umami: Can it replace Google Analytics?

For traffic, referrers and event counts, yes. For attribution modelling, audiences and advertising integration, no.

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.

Umami: What does it need to run?

A container and a PostgreSQL or MySQL database. Most people deploy it on infrastructure they already pay for.

Share

Related pages

More on Nango

More on Umami

Keep looking

Other head to heads