Sync context data for AI agents
Continuously sync your users' external data as context for AI agents across 1,000+ APIs.
Easy ingestion
A Nango sync fetches your users' data, metadata and delivers clean, normalized records to your backend. Put them in a vector or a relational database.
Flexible syncs
Control and customize exactly what's fetched. Supports per-customer changes, custom objects, fields from CRMs.
```
inputs = { ... };
outputs = { ... };
function sync = { ... };
```Durable execution
Syncs are incremental and resumable: they fetch only what’s changed, and resume from exactly where they left off after any failure.
Real-time updates
When a user's data changes, Nango updates your store in real time via webhooks. Your agents see new context within seconds, not on tomorrow's batch.
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
Yes, down to every 30 seconds on any plan. You can also set a different frequency per customer. For updates within seconds, combine polling with provider webhooks. Docs (opens in a new tab)
Yes, all of it. Nango syncs are code-based: you can customize the data it fetches, how it's mapped, how often it runs, and how deletions are detected. Start from a pre-built sync and customize it or start from scratch. Docs (opens in a new tab)
You can build custom syncs using the Nango CLI. Most teams generate syncs and actions using Claude Code, Cursor, or Codex with the Nango skill and review them as a normal PR. Docs (opens in a new tab)
Probably yes. Our catalog (opens in a new tab) includes 7,000+ pre-built syncs and actions, with more added every week. You can also add custom syncs yourself or ask us; we typically add it within days.
Yes. It can be normalized to the schema you define. Each sync maps the provider's data into your model before saving, so if you're looking to unify and normalize data from multiple sources, you can do that using custom syncs.
No. Nango tracks what changed, notifies your backend, and you pull the changes and write them wherever you like (Postgres, a vector store, S3). Your database credentials never touch Nango. Docs (opens in a new tab)
From the dashboard, API, SDK, or the Management MCP: start and pause per customer, trigger a run, re-sync from scratch, change the frequency, and check status. Docs (opens in a new tab)