Arcade.dev vs Nango

Arcade.dev

Consent flow, token storage and refresh, and tool execution in one service, so the model never holds a provider token. The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise.

Nango

1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan.

Arcade.dev

1. Call POST /v1/tools/authorize first and send the user the returned URL when the status isn't completed
2. Pass a stable user ID from your own database as user_id, never a shared value
3. Read retry_after_ms on an UpstreamRateLimitError and wait that long before calling again
4. Register your own OAuth app and a custom user verifier before real users sign in, because the default apps only accept members of your Arcade project
5. Revoke a user's access with DELETE /v1/admin/user_connections/{id}

Nango

1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
2. Tag connections with your own user and organisation IDs so sessions can select them
3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
4. Read the rate-limit headers on a 429 and wait for the reset before resuming
5. Run 0.71.6 or later when self-hosting, and keep the runner port off the network