Connector frameworks

Nango

A code-first integration platform that handles auth, syncs, actions and MCP tools for 1,000+ APIs, for products and their agents.

nango.dev · founded 2022 (the codebase began in 2020 as Bearer's open-source Pizzly OAuth proxy) · San Francisco, California (per Y Combinator) · researched 2026-10-10

Scope: Nango manages OAuth and API keys for your users' accounts, proxies requests, runs your TypeScript sync and action functions on its infrastructure, and keeps a records cache your app reads as a change stream. It ships pre-built Xero syncs and read and write actions. It does not keep history, model accounting, or give an end user a copy of their own data; it is infrastructure for software companies.
Backing: Y Combinator W23. No funding amounts were confirmed from primary sources.
Serves: developers, smb, mid-market
Covers: integration
To ownpurse: Design cousin. Nango is the plumbing a SaaS product uses to read and write its customers' Xero and other accounts. ownpurse solves the same sync problems for one owner on their own machine. Its deletion and change-detection rules are directly reusable; its hosted, latest-only cache is the opposite of ownpurse's record.

What it is

Nango is an integration platform for software companies. You put its auth flow in your app, your users connect their Xero, HubSpot or Slack, and Nango stores and refreshes the tokens, proxies requests and runs the sync and action code you write. It says it covers 1,000+ APIs (GitHub). The code began in 2020 as Pizzly, Bearer’s open-source OAuth proxy; the company was founded in 2022 and went through Y Combinator’s W23 batch (YC).

How it works

Integrations are TypeScript functions. A sync function fetches pages and calls batchSave, which writes to Nango’s records cache. Each record is keyed by the source id and a hash of its payload: the same id and hash means nothing changed. Your app reads GET /records as an ordered change stream of ADDED, UPDATED and DELETED, with a cursor. The cache keeps only the latest version, prunes payloads not updated for 30 days and hard-deletes everything after 60 days without a sync run.

Deletion detection is its most careful rule. For incremental syncs you call batchDelete when the API reports a delete. For full syncs, trackDeletesStart and trackDeletesEnd bracket the sweep and Nango diffs what existed before against what was saved, but only if the run finished with no uncaught exception. The docs warn that swallowing an error causes false deletes and advise against hard-deleting anything on Nango’s word alone. Checkpoints let a run save progress mid-way and resume.

The Xero templates show this in practice: hourly syncs on If-Modified-Since with includeArchived, page offsets, the general ledger by JournalNumber offset, and DELETED or VOIDED invoices passed to batchDelete.

Data and access

The free tier allows 10 connections, 10 compute hours and 10 GB of egress a month. Pay-as-you-go is $50 a month including $50 of credit, then $0.29 a connection, $0.72 a compute hour and $0.50 a GB (pricing, read 2026-10-10). The source is under the Elastic License 2.0. The free self-host covers only auth and proxy; syncs, tools, webhooks and MCP need Enterprise BYOC or Self-Managed.

Agents

Nango is arguably the most agent-ready product in this segment. Agent sessions give each agent its own MCP server URL and a short-lived token, scoped by your backend; the agent never sees credentials and cannot widen its own scope. Write tools for Xero, such as create-invoice, create-payment and update-bank-transaction, are available. There is no approval step: the example code sets require_approval to never, and confirmation is left to the client.

Customers

Product teams building customer-facing integrations and agent tools; its site names Replit, Vapi, Plain, Electric and Motion. It reports 1M+ integrations and customer code running 150M+ times a month (June 2026). Review sites could not be read for this dossier, and no funding figures were confirmed.

History

Nango grew out of the unified-API wave but took the other side of that bet: rather than one normalized model for every CRM or ledger, give developers raw access and the plumbing (auth, retries, scheduling, a cache), and let them write the mapping. Its 2026 blog is almost entirely about agents, which is where it now sells.

For ownpurse

Nango’s sync rules are the ones ownpurse should keep. Only a completed sweep may retract. A hash decides whether anything changed. The output is a stream of changes, not a snapshot. The difference is custody and time. Nango holds a hosted, latest-only cache that expires, built for a vendor serving many customers. ownpurse keeps every version, on the owner’s machine, for one owner. Nango also shows the risk to avoid: a VOIDED invoice is a fact the books need, not a deletion, and an agent with write tools needs a person in the loop. That is ownpurse’s sealed package.

Data and access

Public API: Yes. REST HTTP API and Node SDK for connections, proxy, records and syncs; TypeScript functions SDK for sync and action code; MCP over Streamable HTTP for agent sessions
Auth: Environment secret keys with scopes (for example environment:agent_sessions:write); session tokens as bearer auth for agent MCP; end users authorize providers through Nango Connect
Limits: Free tier hard-capped at 10 connections, 10 compute hours and 10 GB egress a month; provider limits are handled by Nango's retries and rate-limit logic
What access costs: Free $0; Pay-as-you-go $50 a month including $50 of credit, then $0.29 per connection, $0.72 per compute hour and $0.50 per GB egress (ingress free); Enterprise custom, down to about $0.01 a connection at scale (pricing page, read 2026-10-10)
Export: Records through GET /records with cursors (ADDED, UPDATED, DELETED); there is no history to export, and the cache expires.
Notes: Xero: OAuth, pre-built syncs (accounts, bank transactions, contacts, credit notes, invoices, items, organisations, payments, purchase orders, general ledger journals) and create, get, list and update actions. The invoices sync uses If-Modified-Since with includeArchived and turns DELETED and VOIDED invoices into deletes.

Price

Model: Usage-based: connections, compute time and egress, with a free capped tier and an Enterprise contract
Entry: $0 (10 connections, 10 compute hours, 10 GB a month)
Top: Enterprise custom; a Growth support add-on at $450 a month
Notes: Self-hosting and BYOC are Enterprise only for syncs, tools and MCP; there is no EU-hosted cloud.

Agents

MCP: official
AI features: Agent sessions with a per-session MCP server, 7,000+ MCP tools and templates, MCP auth for third-party MCP servers, a management MCP to operate Nango itself, and integrations generated from plain-English descriptions.
Agent writes: Yes. Action functions such as create-invoice, create-payment and update-bank-transaction for Xero are exposed as tools; a session can be scoped to read-only tools.
Approval: None built in. Scoping is the control: your backend chooses the tools and the agent cannot change its session's scope. Nango's own example sets require_approval to never.
Notes: The older Connection MCP is being replaced by agent sessions, which keep raw credentials out of the agent's reach.

Integration and customers

Connects to: 1,000+ APIs (site and GitHub, read 2026-10-10), with pre-built syncs and actions for many, including Xero.
Notes: Integrations are code: TypeScript functions with zod schemas, checkpoints, deletion tracking and sync partitioning, deployed from a CLI. Templates live in the public NangoHQ/integration-templates repo.
Scale: Nango reports 1M+ integrations and running customer code 150M+ times a month (blog, 2026-06-08); 12.6K GitHub stars and about 130 open issues (2026-10-10). Named customers include Replit, Vapi, Plain, Electric and Motion.
Ratings: Not retrieved: review sites refused automated access on 2026-10-10; no G2 or Capterra count confirmed.
What customers say: Testimonials on its site praise breadth and speed of building integrations (Motion cites 60+). Independent review themes could not be checked.

Timeline

2020-04
Code begins as Pizzly, Bearer's open-source OAuth proxy
2022
Nango founded by Robin Guldener and Bastien Beurier
2022-11-30
v0.3, a rewrite of the codebase
2023
Y Combinator W23
2026-06-08
Reports running untrusted customer code 150M+ times a month
2026-08-06
Reports operating auth for 1,000+ APIs
2026-10-02
Release v0.71.12

Borrow and avoid

Borrow: Infer deletes only from a full sweep that completed without an exception, and never act irreversibly on an inferred delete; a payload hash per record so a re-save that changed nothing emits nothing; a change stream with ADDED, UPDATED and DELETED plus a cursor (ownpurse's assert and retract); typed checkpoints saved mid-run; agent sessions scoped by the backend that the agent cannot widen.
Avoid: A cache that keeps only the latest version and expires payloads after 30 days; treating a VOIDED invoice as a deleted one, which loses an accounting fact; write tools wired to agents with require_approval set to never; gating syncs behind an enterprise self-host.

Sources

Not confirmed against a primary source

Funding amounts, rounds and investors beyond Y Combinator W23
When the licence became ELv2 (a short-licence update was committed 2023-04-24)
G2, Capterra and Reddit ratings and sentiment
Current headcount (YC lists 6, which may be dated)
Compliance certifications (the site links a trust center without naming SOC 2)

On the spectrum

0 to 4. The grey tick is ownpurse.

Custody: 2
Where it runs: 1
History: 1
Openness: 2
Breadth: 3
Autonomy: 2
Agent-ready: 4
Easy to connect: 4
Market: 2

See it on the map

Also in connector frameworks

ownpurse is not affiliated with Nango or any company named here. Names are their owners' trademarks. Figures come from the company's own pages and the press, as linked, as of 2026-10-10; scores are our reading of them against the definitions in the landscape. This is not legal or financial advice.