Nango – Unified API Platform for SaaS Integrations

TL;DR

TL;DR: Nango is a source-available unified API platform that handles 167+ SaaS integrations, letting you embed custom connections in your app in minutes instead of weeks.

Source and Accuracy Notes

• Official site: https://nango.dev
• Documentation: https://docs.nango.dev
• GitHub: https://github.com/NangoHQ/nango (open-source)
• Founded: YC W23 (190 points on HN)

What Is Nango?

Building integrations with external SaaS APIs is one of the most tedious parts of any product that touches third-party services. OAuth flows, token refresh logic, API version mismatches, rate limit handling — it all adds up to weeks of work per integration, and maintenance is an ongoing tax.

Nango abstracts all of that. It gives you a single unified API — the Nango API — that connects to 167+ external services. You write your integration once against Nango’s interface, and it handles the rest: authentication, pagination, rate limits, error recovery, and keeping up with API changes.

Because it’s source-available, you can self-host it and retain full control. The product works like a middleware layer between your app and any external API you need to connect to.

The integrations cover the usual suspects — Salesforce, Slack, GitHub, Notion, HubSpot — and quite a few more. The library is actively maintained, so new integrations get added regularly.

Setup Workflow

Step 1: Deploy Nango

The fastest path is their managed cloud, but for self-hosting:

# Clone the repo
git clone https://github.com/NangoHQ/nango.git
cd nango

# Docker compose for self-hosted
docker-compose up -d

Step 2: Configure Your First Integration

# Install the CLI
npm install -g @nangohq/nango

# Authenticate
nango login

# Create a new integration config
nango init my-project

Then define your integration in nango.yaml:

integrations:
  github:
    syncing:
      commits:
        runs: every hour
        response: ${base.url}/webhooks/commits

Step 3: Embed in Your App

// Install the SDK
npm install @nangohq/sdk

// List all available integrations
const nango = new Nango({ secretKey: 'your-secret-key' });

// Trigger a sync
const result = await nango.triggerSync('github', 'commits');
console.log(result);

Deeper Analysis

What makes it different from Zapier/Make? Those are no-code automation tools. Nango is a developer-facing API layer — you write code against it, not a visual builder. You’re not limited to predefined triggers and actions.

The integration maintenance problem. External APIs change. A Slack API update can break your integration silently until someone notices data is missing. Nango’s model handles this at the library level — when an upstream API changes, you update your Nango dependency, not your integration code. That shifts maintenance from “fix each integration individually” to “update the SDK version.”

Source-available vs open-source. The core Nango platform is source-available. The hosted version is commercial. Self-hosting is free for small teams; pricing scales with usage at the higher tiers. This gives you the flexibility to run it yourself while the product has a sustainable business model behind it.

Auth handling. OAuth is where most integration work dies. Nango provides pre-built auth flows for all 167+ integrations — you don’t have to implement the PKCE flow, handle token rotation, or manage refresh tokens. That alone is a significant time savings.

Sync vs real-time. Nango supports both polling-based syncs (runs on a schedule) and real-time webhooks where the external service supports them. The sync model is flexible — you can set different frequencies per integration depending on how time-sensitive the data is.

Practical Evaluation Checklist

• Does it support the specific SaaS products you need to connect?
• How active is the integration library — how quickly are new APIs added?
• Self-hosting: what does the operational overhead look like at your scale?
• Auth scope: are the OAuth permissions narrow enough for your use case?
• Sync latency: the scheduled polling model may not suit real-time use cases

Security Notes

• Nango stores OAuth tokens in encrypted form. If self-hosting, the encryption key is yours.
• Tokens are never logged or exposed in API responses — they stay in the Nango vault.
• The open-source SDK means you can audit the code before trusting it with production credentials.
• For enterprise use, consider their hosted product which adds SOC 2 compliance and audit logs.

FAQ

Q: Is Nango free to self-host? A: Yes, the self-hosted version is free for small teams. The hosted product has tiered pricing based on sync volume and team size. See nango.dev/pricing for details.

Q: How does Nango handle rate limits? A: Nango queues requests and respects each external API’s rate limits automatically. It spreads requests over time rather than bunching them up. For high-volume integrations you can configure rate limit handling per integration.

Q: Can I add a custom integration that isn’t in the 167+ library? A: Yes. Nango provides a framework for building custom integrations. You define the API endpoints, auth method, and data transformations in a configuration file. See their docs on building custom integrations.

Q: Does Nango support bi-directional data sync? A: Yes. You can both read from and write to external APIs through Nango. The sync is not read-only.

Q: How do I handle webhook events from external services? A: Nango receives webhooks at a provided endpoint and routes them to your app. You configure the webhook URL in your Nango dashboard and it validates signatures before forwarding payloads.

Conclusion

Nango solves the integration maintenance problem that kills developer velocity on anything that touches external SaaS. The library of 167+ pre-built integrations covers most common needs, and the self-hosted source-available model means you’re not locked in.

For products that need 3-5+ SaaS integrations, Nango pays for itself in weeks of avoided integration work. Even for a single integration, the auth handling alone is worth the tradeoff — OAuth implementation is not something you want to debug in production.

If you find yourself building yet another Slack integration or maintaining yet another Salesforce connector, Nango is worth evaluating. The setup is quick, the SDK is well-documented, and the maintenance story is significantly better than doing it yourself.