Arc0 vs Scalekit.
Considering Arc0 as a Scalekit alternative? A like-for-like read on pricing, consent-screen branding, and token handling for AI agents, including where Scalekit is still the better choice.
Arc0 and Scalekit, line by line.
| Item | ARC0 | SCALEKIT |
|---|---|---|
| Pricing unit | Per active user per month, with 5,000 pooled calls per user included across the workspace. | Per tool call: 5,000 free per month with no credit card, then $0.0005 per call on the Growth plan. |
| Entry pricing | Launch plan: $99/mo including 1,000 active users. | Growth plan: $99/mo including 100,000 tool calls and unlimited connected accounts. |
| Your users' consent screen | Carries the customer's logo on every plan; custom domain and the customer's own OAuth apps on paid plans. | Uses Scalekit's shared OAuth app by default; full branding and a custom domain require registering your own OAuth app, typically on a paid plan. |
| Catalog | 1,500+ apps; vendors' own MCP servers can sit behind Arc0 auth. | Markets 500+ connectors and 8,000+ callable actions; its own connector directory shows roughly 200+ apps across 13+ categories. |
| Token export | Tokens exportable at any time by API; tokens from the customer's own OAuth apps keep working after export. | Tokens stay in Scalekit's vault; agents receive an opaque runtime reference rather than the token, with no documented export path. |
| Audit log | Every call logged on every plan including free; retention 7/30/90 days by plan; OpenTelemetry export on paid plans. | Every plan gets 30-day audit log retention; Enterprise can extend retention to 1 year and stream logs to Datadog or Splunk. |
| Deployment / self-host | Scale plan (from $1,500/mo) includes EU hosting and dedicated hosting. | VPC/on-premises deployment is only on the custom-priced Enterprise plan, with a 99.99% uptime SLA. |
| Focus / ownership | Independent, focused only on agent connectivity; operated by Exa Labs LLC. | Sells three related but separate products -- B2B SSO/SCIM, full-stack app auth, and agent/MCP auth -- from one company. |
Where Scalekit is the better choice.
If you also need enterprise single sign-on and SCIM provisioning for your own product's login, Scalekit sells that today as a companion product (first connection of each type free, then from $60/mo with volume discounts). Arc0 does not offer this yet; it is on Arc0's roadmap.
Unlimited connected accounts ship on every plan, even free, and billing is purely per tool call. For an agent that connects many accounts but calls tools rarely, Scalekit's $0.0005-per-call model can cost less than Arc0's per-active-user pricing.
Scalekit documents OAuth 2.1 support for MCP servers in more protocol-level detail, including Dynamic Client Registration, mandatory PKCE, and Client ID Metadata Documents, plus open-source SDKs and agent skills for 40+ coding tools.
What Arc0 does differently.
Scalekit's Growth plan charges $99/mo for 100,000 tool calls, then $0.0005 per call. Arc0's Launch plan charges $99/mo for 1,000 active users, with 5,000 pooled calls per user included.
Scalekit markets 500+ connectors and 8,000+ callable actions, though its own connector directory lists roughly 200+ apps. Arc0 lists 1,500+ apps.
Scalekit's vault hands agents an opaque runtime reference rather than the token itself, and its docs and marketing pages do not describe an API to export the underlying credential. Arc0 lets you export tokens by API at any time.
Full consent-screen branding on Scalekit requires registering your own OAuth app, and a custom auth domain is a separate setup step; the shared dev-tier flow uses Scalekit's own OAuth app. Arc0 puts the customer's logo on the consent screen on every plan, including free.
Scalekit sells B2B SSO/SCIM, full-stack app authentication, and agent/MCP auth as separate but related products. Arc0 is a single product focused only on agent connectivity.
VPC/on-premises deployment is available only on Scalekit's custom-priced Enterprise plan. Arc0 offers EU and dedicated hosting starting on its $1,500/mo Scale plan.
Free migration from Scalekit.
An engineer moves you over at no charge, on any plan. You keep shipping while we do the work, and nothing changes for your users until you say so.
- 01We map itEvery app, action and auth config your agent uses in Scalekit, matched to Arc0.
- 02We set it upYour OAuth apps registered, Arc0 Connect in your brand, and your first policies written with you.
- 03We move your usersTokens imported wherever Scalekit lets you export them, and reconnects staged in-product where it doesn’t.
What moving from Scalekit looks like.
Moving off Scalekit's agent auth mainly means re-pointing billing from per call to per user and rebuilding your consent flow's branding.
Connections
Scalekit does not document a way to export the underlying OAuth tokens or API keys it holds; agents only ever receive an opaque runtime reference. Plan on your users reconnecting once through Arc0's branded consent flow rather than migrating live credentials.
Your agent
Scalekit issues a per-user authenticated MCP URL or lets your agent call its connectors directly. Switching means pointing your agent at Arc0's MCP endpoint, SDK, or REST proxy instead, and each connected app needs its access re-approved under Arc0's own policy rules.
Questions, answered.
Is Arc0 a good Scalekit alternative?
Yes if you want one connectivity layer billed per active user rather than per tool call, with your brand on the consent screen from the free tier up. Pick Scalekit instead if you also need its B2B SSO/SCIM product for your own app's login today, or if your agent calls tools rarely across many connected accounts, where its per-call pricing can be cheaper.
Does Arc0 charge per tool call like Scalekit?
No. Arc0 charges per active user per month, with 5,000 calls per user pooled across the workspace, and only usage above that pool is billed per 1,000 calls. Scalekit charges per tool call from the first call above its free 5,000-call tier.
Can I export my tokens if I leave Scalekit?
Scalekit's public docs describe tokens as staying in its vault, with agents receiving only an opaque reference; no export API is documented. Arc0 lets you export tokens by API at any time, and tokens created under your own OAuth apps keep working after export.
Do I need to drop Scalekit's SSO/SCIM product to use Arc0?
No. Arc0 does not yet offer SSO or SCIM for your own product's login; it's on Arc0's roadmap. Teams that need that today can keep using Scalekit's auth-for-saas product alongside Arc0 for agent connectivity.
Moving from Scalekit? We’ll move you.
Tell us where your connections live today and what your agent does. An engineer plans and runs the move with you, free, including how to keep reconnects to a minimum.