Skip to main content

Introduction

Nango provides open-source infrastructure for native integrations.

Why?

Building native integrations is costly, particularly as you support more integrations, deeper integrations and higher traffic. Most companies end up building the same infrastructure: scheduling, queueing, error handling, retries, authentication, logging, local development environment, CI/CD, etc. Nango's goal is to make integration developers 10x more productive by providing them with this common infrastructure.

A packaged micro-service for native integrations

Nango is an independent micro-service that centralizes interactions with external APIs. It can be run locally, self-hosted or managed by Nango Cloud. Nango runs your own integration-specific code, abstracting away the common infrastructure across integrations. It supports integrations of arbitrary complexity and scale, while remaining simple to use, reliable and extensible.

Nango Server

Nango comes with bullet-proof infrastructure focused on native integrations:

  • Queuing & scheduling
  • Retries & error handling
  • OAuth & token refresh
  • Rate limit handling
  • Logging & monitoring
  • Delightful local development & testing
  • CI/CD
  • Many more features companies end up building from scratch!

What is a native integration?

Native integrations designate the features in your product, for the benefit of your users, that are reliant on external services that your users also use. Native integrations are sometimes called "embedded", "customer-facing" or "product" integrations. Your product integrates to the external service via their public API. Users provide you with credentials to the 3rd-party service, usually via OAuth directly from your product. Here are example pages advertising native integrations.