Sync your users' data
into your product
Keep a fresh copy of your users' external data in your own database, synced from 1,000+ APIs.
Continuous, incremental sync
A Nango sync delivers clean, normalized records to your backend. It fetches only what changed, resumes after any failure, and detects deletions.
Real-time updates
Get changes within seconds via provider webhooks, backed by periodic polling that reconciles anything missed.
Two-way sync
Write changes back to the provider with actions — same auth, same logs, same retries as your syncs, so both systems stay consistent.
Customize per customer
Map custom fields, choose which objects to sync, and adjust behavior per tenant.
{
"custom_fields": [ ... ],
"syncContacts": false
}Enterprise-grade security & scale
Granular access
RBAC, per-user API scopes
Encrypted
At rest & in transit encryption
Self-hostable
Deploy in your environment
99.9% uptime
All incidents reported on our status page
1M+ integrations
Proven at real-world scale
Open-source
Inspectable infrastructure
Compliance
SOC 2, GDPR & HIPAA
Observability
Detailed traces, export with OTel
Support
From Nango engineers
FAQ
Both. Webhooks (where supported by the provider) provide instant updates. Polling can be used to implement change detection when webhooks aren't supported, or to reconcile changes missed by webhooks. Docs (opens in a new tab)
Only what your sync saves, and only briefly. Records sit encrypted in a cache on Nango Cloud (AWS, US) until you fetch them, are pruned 30 days after their last update, and deleted entirely if a sync stops running for 60 days. Self-hosting and bring-your-own-cloud are available if data can't leave your infrastructure. Docs (opens in a new tab)
No. Syncs save a checkpoint after each batch and fetch only what changed since. Every record is hashed, so only real changes are reported. For APIs without incremental filters, Nango diffs the full set for you. Docs (opens in a new tab)
Yes. Custom fields and objects are ordinary fields in a sync. Each customer's choices are stored on their connection and read at runtime. Docs (opens in a new tab)
Nango sends a webhook when a sync finishes with details of what was added, updated, and deleted. You fetch changes with a cursor, so nothing is skipped even if your client restarts. Docs (opens in a new tab)
It resumes from the last checkpoint on the next run instead of starting over. Especially useful for large first-time syncs or long sync jobs. Failures are logged and trigger a webhook. Docs (opens in a new tab)
Incremental syncs fetch only what changed, which keeps volume low. Requests respect provider rate-limits, and a sync can wait out a throttle for up to 24 hours instead of failing. Docs (opens in a new tab)
Yes. Store each customer's configuration (objects, folders, field mappings, filters) on their connection and the sync uses it. Syncs can also stay off until a customer finishes setup. Docs (opens in a new tab)