Nango

Nango is an open-source platform for building product integrations — managed OAuth, an authenticated proxy, and a TypeScript runtime for syncs and actions across 700+ APIs. We rate it 82/100 — the most code-first, developer-friendly choice in the iPaaS / unified-API space if your team is happy writing TypeScript and wants the integration logic in version control rather than a third-party visual builder.

What is Nango?

Nango is a Y Combinator-backed (W23) open-source integrations platform created by Bastien Beurier and Robin Guldener. The first commit on the public NangoHQ/nango repository landed in September 2022, and as of May 6, 2026 the project has crossed 7,270+ GitHub stars, 710+ forks and ships under the Elastic License v2. The latest tagged release at the time of writing is v0.70.1, published on April 17, 2026.

The pitch is simple: every B2B SaaS eventually drowns in integration work — OAuth flows, token refresh, rate limits, per-customer data syncs, webhook ingestion. Off-the-shelf iPaaS tools either lock you into a low-code builder or charge per-connection in ways that punish growth. Nango exposes three primitives — Auth, Proxy, and Functions — and lets you write integration code as plain TypeScript that runs on Nango's production infrastructure (Temporal-backed runtime, per-tenant isolation, automatic retries). It is used in production by Replit, Ramp, Mercor, Typeform and Semgrep, among others.

Key Features of Nango

• Managed auth for 700+ APIs: OAuth 1, OAuth 2, API keys, Basic, custom token flows — all wrapped behind one embeddable Connect UI. Token refresh, per-tenant credential storage and multi-environment isolation are handled out of the box.
• Authenticated proxy: One nango.get/post/put call per request — Nango injects the right credentials, retries on 429s, normalizes rate-limit headers and returns the raw response. No more bespoke fetch wrappers per integration.
• TypeScript Functions runtime: Write a sync, action or webhook handler as a plain async function and deploy with nango deploy. The runtime gives you per-tenant isolation, scheduled execution, automatic retries, structured logs and a built-in record store for sync state.
• AI builder for new integrations: Generate Function code from a natural-language description of an endpoint or sync. Output is reviewable TypeScript — not a black-box config — so you can edit, version-control and test it like normal code. Compatible with Cursor, Codex and Claude Code.
• MCP and tool-calling support: Each integration exposes its actions over Model Context Protocol, so AI agents (LangChain, OpenAI agent SDK, Claude desktop) can call them directly without a custom adapter layer.
• Open source and self-hostable: The full repo is Elastic-licensed and runnable with a single docker compose up. Free self-host has a limited feature set; Cloud and Enterprise Self-Hosted unlock everything, with SOC 2 Type II, HIPAA and GDPR available on paid plans.
• Battle-tested infrastructure: Nango processes billions of API requests monthly across hundreds of customers, with Temporal-powered orchestration and ElasticSearch-backed logs.

What Users Say About Nango

Sentiment across G2, the Y Combinator launches, and developer threads is broadly positive on developer experience and notably mixed on pricing. On G2, reviewers consistently praise the speed of going from zero to a working OAuth flow ("less than an hour" is a recurring phrase) and the responsiveness of the founding team in their public Slack.

The most common criticism is the connection-based meter. Several reviewers flag that the Free tier's 10 connections and the Starter tier's 20 connections feel low relative to the price jump, and that for a multi-tenant SaaS each end-user counts as a separate connection — which can make the bill scale faster than expected. Engineering posts on Hacker News point to a real maintenance reality: every integration is TypeScript code you write and own, which is a feature for teams that want control and a downside for teams hoping for a fully managed unified API. Competing platforms like Merge and Truto have published direct comparisons highlighting exactly this trade-off.

Nango Pricing

Nango uses a free tier plus tiered, usage-based pricing. All tiers include two-way syncs & RAG, MCP / tool-calling and API unification — the difference is volume, environments, security/compliance, and turnaround on requesting new APIs.

Plan	Price	Key Limits
Free	$0/mo	10 connections, 100k proxy requests, 100k function runs, 2 environments. No SOC 2.
Starter	from $50/mo	20 connections then $1 each, 200k proxy requests, 3 environments, SOC 2 Type II.
Growth	from $500/mo	100 connections then $1 each, 1M proxy requests, 10 environments, RBAC, custom branding, logs export. SAML SSO and HIPAA available as add-ons.
Enterprise	Custom	Unlimited environments, 2-day new-API turnaround, SAML SSO, HIPAA, self-hosting and SLAs included.

There is no traditional "14-day trial" — the Free plan is permanent and is how most teams pilot. Self-hosting is also free with a reduced feature set.

Who Should Use Nango?

Best for: startup and scale-up engineering teams shipping a B2B SaaS that needs 5–50 native integrations, AI-product teams that want their agents to call real customer APIs (HubSpot, Slack, Google Drive, GitHub) over MCP, and any team that wants to keep integration logic in their own Git repository instead of a third-party low-code builder.

Not ideal for: non-technical operators who need a Zapier-style visual builder, teams that explicitly want a fully normalized unified-API schema (Merge or Finch are closer to that), and very high-volume tenants where the per-connection meter would dominate cost — in that case talk to Nango about Enterprise rather than staying on Growth.

Pros and Cons

Pros:

• Managed OAuth + token refresh for 700+ APIs is the fastest path from zero to a working "Connect to X" button in production.
• Integrations are real TypeScript code you can review, diff and test — not a black-box visual flow.
• Open source with a credible self-host story; SOC 2 Type II, HIPAA and GDPR on paid tiers.
• Founders are visibly active in the public Slack and on GitHub issues.

Cons:

• Per-connection metering can scale quickly for multi-tenant SaaS — do the maths before committing to Starter.
• You still own the integration code, so 30+ integrations can become a real headcount line item.
• Some advanced features (SAML SSO, HIPAA) sit behind add-ons or Enterprise even on Growth.

Alternatives to Nango

Composio takes the opposite approach — a managed catalog of 250+ tools designed primarily as ready-made AI-agent skills, with less code ownership. Merge is the established unified-API option (HRIS, ATS, accounting) and is closer to plug-and-play but offers far less control over integration logic. Paragon and Workato sit further toward the embedded-iPaaS end with visual builders. If you are mostly looking for OAuth and don't need syncs, hand-rolling with Stytch's connected-apps feature can be cheaper, though much narrower.

Verdict: Is Nango Worth It?

Yes — with one caveat about pricing. If you are a B2B SaaS or AI-product engineering team that wants integration logic to live in your own Git repo, Nango is the most credible open-source option in 2026 and is the rare iPaaS-adjacent tool whose code-first stance survives contact with production. The 82/100 rating reflects the genuinely excellent core platform, mature 700+ API catalog and active OSS community, balanced against a connection-based pricing model that punishes high-tenant SaaS and a still-real maintenance burden as your integration count grows past 20–30.

Frequently Asked Questions

Is Nango free?

Yes — Nango has a permanent Free plan that includes 10 connections, 100k proxy requests, 100k function runs and 2 environments. Paid Cloud plans start at $50/month for Starter. The full source is also open and self-hostable for free, with a reduced feature set.

What APIs does Nango support?

700+ APIs out of the box, including HubSpot, Salesforce, GitHub, Slack, Linear, Google Workspace, Microsoft 365, QuickBooks, Stripe, Notion, Jira, Zendesk and most of the long tail of B2B SaaS. The community can contribute new providers via pull request.

How does Nango compare to Merge?

Merge is a managed unified-API platform with normalized schemas across categories like HRIS, CRM and accounting — minimal code, less flexibility. Nango is code-first: you keep integration logic as TypeScript and own the runtime, which is more work but gives you full control and version-controllable integrations.

Is Nango open source?

Yes — the project lives at github.com/NangoHQ/nango under the Elastic License v2. You can self-host the full platform with Docker Compose.

Does Nango support AI agents and MCP?

Yes. Each Nango integration exposes its actions over Model Context Protocol, so agents from frameworks like LangChain, the OpenAI Agent SDK or Claude can call them as tools without a bespoke adapter. The AI builder also generates new TypeScript Function integrations from a natural-language description.