Related projects
This is a research index for products adjacent to AuthProxy. Vendor packaging, self-hosting terms, and connector counts change frequently; verify the linked vendor sources before using the tables for a procurement decision.
The landscape splits into a few overlapping domains:
- Unified APIs: Normalize a vertical (e.g., HRIS/ATS/Accounting) behind a single data model and endpoint set.
- Embedded iPaaS: Integration infrastructure designed to be embedded into your SaaS product for customer-facing integrations.
- Traditional iPaaS / Workflow Automation: Internal automation platforms with large connector catalogs and visual builders.
- AI / Agent Integration Gateways: Tool-calling, MCP servers, or AI gateways that broker auth + actions to many services.
- Open-source Frameworks / Building Blocks: Libraries or frameworks for teams that want full control.
Below are summaries and comparison tables for the projects in this repo’s list. Connector counts are taken from the vendors’ public catalogs or docs when available; when not available, it’s noted explicitly.
Where AuthProxy fits
Section titled “Where AuthProxy fits”AuthProxy is a strong fit when a team wants to keep using native third-party APIs, run the credential data plane in infrastructure it controls, and reuse a connection lifecycle across many integrations. It provides embedded connection and administration UIs, but the host application keeps its own business logic and provider-specific requests.
That produces different tradeoffs from adjacent categories:
- A unified API reduces provider differences but introduces a normalized data model. AuthProxy preserves the provider’s full native surface.
- A managed embedded iPaaS can provide a larger maintained catalog and hosted operations. AuthProxy provides source access and deployment control, while the adopting team owns its connectors and environment.
- A workflow automation system owns orchestration and transformations. AuthProxy focuses on connections, authentication, proxying, and governance; application code still owns the workflow.
- A secret manager or credential proxy protects secret access. AuthProxy adds OAuth callbacks and refresh, user-facing setup, connector versions, health, rate limits, and request-event context.
The relevant build-versus-buy question is therefore not only connector count. It is whether the team wants to own provider-specific integration behavior and its deployment in exchange for native API access, extensibility, and control of credential and request data.
Unified APIs
Section titled “Unified APIs”| Product | Commercial / OSS | Traditional vs Embedded | Connector Count | Self-hosting | Notes |
|---|---|---|---|---|---|
| Merge | Commercial | Primarily embedded (customer-facing) | 220+ integrations | Yes (paid option; details not public) | Unified APIs across HRIS, ATS, CRM, Accounting, Ticketing, etc. |
| Kombo | Commercial | Embedded | 250+ integrations | No public self-host option; regional SaaS (EU/US) | Unified API focused on HRIS/ATS/LMS/Payroll. |
Unified API product notes
Section titled “Unified API product notes”- Merge: Provides unified APIs across multiple verticals plus a hosted platform that manages auth, maintenance, and monitoring. Connector count published in their integrations catalog. Supports webhooks and standard API patterns in docs. Code-first via REST APIs, with SDKs and platform tooling. Pricing indicates a self-hosted option available for purchase. See: https://www.merge.dev/integrations, https://docs.merge.dev/, and https://www.merge.dev/pricing.
- Kombo: Unified API focused on HR/ATS/LMS/Payroll. Connector counts published in their integrations catalog and category pages. Built for embedding into SaaS products. Docs describe EU/US regional hosting, with no self-host option mentioned. See: https://www.kombo.dev/integrations and https://docs.kombo.dev/data-residency-compliance.
Embedded iPaaS (customer-facing integrations)
Section titled “Embedded iPaaS (customer-facing integrations)”| Product | Commercial / OSS | Traditional vs Embedded | Connector Count | Self-hosting | Notes |
|---|---|---|---|---|---|
| Paragon | Commercial | Embedded | 130+ native connectors | Yes (managed or unmanaged on-prem) | Embedded SDK, white-labeled UI, auth, logs, multi-tenant. |
| Prismatic | Commercial | Embedded | 190+ connectors | Partial (on-prem agent for private resources) | Low-code + code SDK, integration marketplace tooling. |
| Workato | Commercial | Traditional iPaaS w/ embedded option | 1,000+ connectors | Partial (on-prem agent for private systems) | Enterprise automation platform; embedded option exists. |
| Tray.io | Commercial | Traditional + embedded offering | Not publicly stated | Partial (on-prem agent for private systems) | Visual workflow builder + embedded product. |
| Cyclr | Commercial | Embedded | 600+ applications | Yes (self-hosted private cloud) | Embedded integration platform and connector library. |
| Pandium | Commercial | Embedded | 200+ connectors (docs mention 210) | No public self-host option; managed infrastructure | Code-first, connectors focus on auth + webhooks. |
| Ampersand | Commercial + OSS connectors | Embedded | Not publicly stated | No public self-host for platform; OSS connectors library | Declarative, code-first integrations; open connectors repo. |
| Nango | Commercial + OSS (Elastic License) | Embedded / integration infrastructure | 500-700+ APIs (varies by page) | Yes (limited free self-host; enterprise self-host) | Code-first integration platform with auth, sync, webhooks. |
| Frigg | Open Source | Embedded framework | Not publicly stated | Yes (runs in your cloud) | OSS framework for building integrations in your own cloud. |
Embedded iPaaS product notes
Section titled “Embedded iPaaS product notes”- Paragon: Embedded integration platform with 130+ native connectors plus a custom integration builder, white-labeled connect portal, multi-tenant auth, and logs. Paragon supports cloud, managed on-prem, and unmanaged on-prem deployments. See: https://docs.useparagon.com/overview and https://docs.useparagon.com/on-premise/choosing-a-hosting-solution.
- Prismatic: Embedded iPaaS with built-in connectors and SDK for custom ones; integration marketplace tooling. Connectors page lists 190+ built-in connectors. An on-prem agent (Docker container) can run in a private network to access private resources. See: https://prismatic.io/connectors/ and https://prismatic.io/docs/integrations/connections/on-prem-agent/.
- Workato: Traditional enterprise iPaaS with an embedded option; docs list 1,000+ connectors. On-premise agents provide secure access to private systems. See: https://docs.workato.com/connectors and https://docs.workato.com/on-prem/agents.
- Tray.io: Traditional iPaaS with an embedded product; public connector count not clearly stated in official docs. Tray provides an on-prem agent that runs on your infrastructure to connect to private systems. See: https://developer.tray.ai/openapi/trayapi/tag/connectors/ and https://docs.tray.ai/tray-uac/connecting-to-on-premise-systems/on-prem-agent/getting-started/.
- Cyclr: Embedded iPaaS; marketing page claims 600+ applications supported. See: https://cyclr.com/application-connectors.
- Pandium: Embedded iPaaS emphasizing code-first integrations; marketing lists 200+ connectors; docs note "210" connectors. Pandium emphasizes managed infrastructure for running integrations, with no self-host option mentioned. See: https://www.pandium.com/connectors and https://docs.pandium.com/connectors/connectors-101.
- Ampersand: Code-first embedded integration platform; open-source connectors library on GitHub. Connector count not publicly stated. Ampersand docs describe the Ampersand server as a managed service; connectors library is open source. See: https://github.com/amp-labs/connectors and https://docs.withampersand.com/.
- Nango: Code-first integration infrastructure with auth, sync, webhooks, and managed execution. Open-source core uses the Elastic License. Connector counts vary across pages: 500+ to 700+ depending on page (catalog and homepage). Nango offers a limited free self-hosted option plus an enterprise self-hosted edition. See: https://github.com/NangoHQ/nango, https://nango.dev/, https://www.nango.dev/api-integrations, and https://nango.dev/docs/guides/platform/self-hosting.
- Frigg: Open-source framework for building customer-facing integrations that runs in your cloud; provides an API module library, but no published connector count. See: https://lefthook.com/frigg/ and https://docs.friggframework.org/.
Traditional iPaaS / workflow automation
Section titled “Traditional iPaaS / workflow automation”| Product | Commercial / OSS | Traditional vs Embedded | Connector Count | Self-hosting | Notes |
|---|---|---|---|---|---|
| n8n | Open source + commercial hosting | Traditional iPaaS | 1,000+ apps | Yes (self-hosted editions) | Visual workflow automation, self-hostable. |
| Pipedream | Commercial (free tier) | Traditional iPaaS | "Thousands of apps" | No (publicly stated no self-host option) | Code-first workflows with triggers/actions and webhook support. |
| Workato | Commercial | Traditional iPaaS | 1,000+ connectors | Partial (on-prem agent for private systems) | Enterprise automation, recipe-based workflows. |
| Tray.io | Commercial | Traditional iPaaS | Not publicly stated | Partial (on-prem agent for private systems) | Visual workflow builder with strong API tooling. |
| Apache Camel | Open Source (Apache-2.0) | Integration framework; adjacent to traditional iPaaS via Camel K / Karavan | 370 non-core components (plus core components and Kamelets) | Yes (library/runtime you operate; Camel K runs on Kubernetes) | Enterprise Integration Patterns, route DSLs, components, Kamelets, and low-code/Kubernetes tooling. |
Traditional iPaaS product notes
Section titled “Traditional iPaaS product notes”- n8n: OSS workflow automation with a very large app catalog; their integrations pages note 1,000+ apps. Docs explicitly support self-hosted editions. See: https://n8n.io/integrations/ and https://docs.n8n.io/choose-n8n/.
- Pipedream: Developer-first automation platform with triggers/actions and code steps; docs describe integrations as "thousands of apps." Pipedream staff state there is no self-host option at this time. See: https://pipedream.com/docs/apps, https://pipedream.com/docs/workflows/building-workflows/triggers/, and https://pipedream.com/community/t/how-can-i-self-host-pipedream-on-my-development-machine-and-ec2-instance/4978.
- Workato and Tray.io: included above; widely used enterprise iPaaS tools with large connector libraries and visual builders.
- Apache Camel: Long-running open-source integration framework based on Enterprise Integration Patterns. Camel Core is a small embeddable Java library with DSLs for routes, URI-addressed endpoints, data formats, and a large component catalog; the current component reference lists 370 non-core components. It is not an embedded SaaS integration product by itself: teams operate it inside their own applications or infrastructure. Related projects make it more platform-like: Camel K runs Camel integrations natively on Kubernetes, Karavan provides a low-code UI for designing/configuring routes with Kamelets and components, and Kamelets package source/sink connector snippets behind simpler interfaces. Compared with AuthProxy, Camel is much broader for routing, transformation, and message mediation, but does not primarily focus on customer-facing connection lifecycle, tenant-scoped OAuth/API-key credential storage, or authenticating proxy behavior. See: https://camel.apache.org/manual/faq/what-is-camel.html, https://camel.apache.org/components/4.18.x/index.html, https://camel.apache.org/docs/, and https://camel.apache.org/.
AI / agent integration gateways
Section titled “AI / agent integration gateways”| Product | Commercial / OSS | Traditional vs Embedded | Connector Count | Self-hosting | Notes |
|---|---|---|---|---|---|
| Composio | Commercial | Embedded for AI agents | 900-1000+ toolkits (500+ apps) | Not stated in docs | Managed auth, triggers, MCP servers. |
| Metorial | OSS + commercial hosting | Embedded for AI agents | 600+ MCP servers | Yes (open source; self-hostable) | MCP-native integration platform and observability. |
| Pica | Commercial | Embedded for AI + SaaS | 200+ integrations | No public self-host option; SaaS with API key | AuthKit + Passthrough API with 25k+ actions. |
| Airweave | Open source + hosted | Embedded for AI (data ingestion) | 50+ data sources | Yes (open source; self-host or hosted) | Unified retrieval layer for agents. |
| LiteLLM | Open source + commercial | AI gateway | 100+ providers | Yes (OSS self-host; cloud option) | LLM gateway with auth, quotas, and routing. |
| Bifrost | Open source + commercial | AI gateway | 20+ providers | Yes (self-hostable gateway) | OpenAI-compatible gateway with governance and routing. |
| Agent Vault | Open source (MIT) + commercial | Credential proxy for AI agents | Any HTTPS service (no connector catalog) | Yes (binary, Docker, from source) | Infisical’s HTTP credential broker; injects credentials at the network layer so agents never see secrets. |
AI / agent product notes
Section titled “AI / agent product notes”- Composio: Managed auth and tool execution for AI agents. Docs mention 1000+ toolkits; the toolkits catalog shows ~900 toolkits; other pages reference 500+ apps. No self-host option is documented. See: https://docs.composio.dev/, https://docs.composio.dev/toolkits, and https://docs.composio.dev/toolkits/introduction.
- Metorial: Open-source MCP integration platform; GitHub repo states it is open source and self-hostable, with a hosted option available. See: https://github.com/metorial/metorial.
- Pica: Integration infrastructure for SaaS + AI; AuthKit handles OAuth/token refresh and multi-tenant auth. Docs require a Pica account and API key, implying hosted service. See: https://docs.picaos.com/authkit/setup and https://docs.picaos.com/authkit.
- Airweave: Open-source context retrieval layer with 50+ prebuilt connectors; focuses on ingestion and unified search for agents. Site FAQ says it is open source and can be self-hosted or used via hosted platform. See: https://airweave.ai/ and https://docs.airweave.ai/.
- LiteLLM: Open-source LLM gateway supporting 100+ provider integrations, with spend tracking and routing. OSS page highlights self-hosting with no data sent to LiteLLM servers; docs show running the proxy via Docker or CLI. See: https://www.litellm.ai/oss and https://docs.litellm.ai/.
- Bifrost: Open-source AI gateway with 20+ providers and OpenAI-compatible APIs; supports routing, failover, and governance. GitHub repo is Apache-2.0 and docs show local deployment via Docker or NPX. See: https://github.com/maximhq/bifrost and https://docs.getbifrost.ai/.
- Agent Vault: Open-source HTTP credential proxy by Infisical, purpose-built for AI agents. Agents get a scoped session and a local
HTTPS_PROXY; Agent Vault injects the credential at the network layer so credentials are never returned to the agent. Works with any HTTP-speaking agent (Claude Code, Cursor, Codex, custom Python/TypeScript, sandboxed processes) and any HTTPS API — there is no prebuilt connector catalog; you register your own services and credentials. Ships as a binary, Docker image, or from source; MIT-licensed with a separateee/directory for enterprise features. Offers a container-sandbox mode (iptables-locked egress through the proxy) and an SDK for orchestrating sandboxed agents (Docker/Daytona/E2B). See: https://github.com/Infisical/agent-vault, https://docs.agent-vault.dev, and https://infisical.com/blog/agent-vault-the-open-source-credential-proxy-and-vault-for-agents.
Open-source frameworks / building blocks
Section titled “Open-source frameworks / building blocks”| Project | Commercial / OSS | Traditional vs Embedded | Connector Count | Self-hosting | Notes |
|---|---|---|---|---|---|
| Frigg | Open Source | Embedded framework | Not publicly stated | Yes (runs in your cloud) | Serverless framework + API modules library. |
| Ampersand Connectors | Open Source | Embedded building blocks | Not publicly stated | Yes (library you run yourself) | OSS connector library used by Ampersand. |
| Apache Camel | Open Source (Apache-2.0) | Integration framework / building block | 370 non-core components (plus core components and Kamelets) | Yes (library/runtime you operate) | EIP-based routing and mediation framework with route DSLs, components, data formats, Camel K, and Karavan. |
Framework notes
Section titled “Framework notes”- Frigg: OSS framework for teams that want to own infrastructure and build embedded integrations; provides a modular API library and serverless architecture, and runs in your cloud. See: https://lefthook.com/frigg/ and https://docs.friggframework.org/.
- Ampersand Connectors: OSS connector library used by Ampersand; useful for teams building their own integration infrastructure. See: https://github.com/amp-labs/connectors.
- Apache Camel: OSS integration building block for teams that want full control over routes, transports, and deployment. It is strongest when the problem is message routing, mediation, protocol bridging, transformation, or running integration logic inside Java/Spring Boot/Quarkus/Kubernetes environments. It is less directly comparable to embedded iPaaS products because it does not provide a hosted multi-tenant connection UI, unified API model, or credential lifecycle out of the box. See: https://camel.apache.org/manual/faq/what-is-camel.html and https://camel.apache.org/docs/.
Quick Comparison (High-Level)
Section titled “Quick Comparison (High-Level)”| Product | Primary Use Case | Code vs UI | Eventing/Webhooks | Connector Definition | Self-hosting |
|---|---|---|---|---|---|
| AuthProxy | Embedded connection lifecycle and authenticating proxy | Code-first with embedded Marketplace and Admin UIs | Not a workflow or event platform | Declarative, versioned definitions maintained by the adopting team | Yes |
| Merge | Unified API for B2B SaaS data | API-first (code) | Webhooks supported | Vendor-defined connectors maintained by Merge | Yes (paid option) |
| Kombo | Unified HR/ATS/LMS/Payroll | API-first (code) | Webhooks supported | Vendor-defined connectors maintained by Kombo | No public self-host option |
| Paragon | Embedded integrations for SaaS | Hybrid (SDK + UI) | Webhooks + workflow triggers | Prebuilt + custom connector builder | Yes (managed or unmanaged on-prem) |
| Prismatic | Embedded iPaaS | Hybrid | Webhooks + workflows | Prebuilt + SDK | Partial (on-prem agent) |
| Workato | Traditional enterprise iPaaS | UI-heavy | Triggers + actions | Prebuilt + custom connectors | Partial (on-prem agent) |
| Tray.io | Traditional + embedded iPaaS | UI-heavy | Triggers + actions | Prebuilt + custom connector SDK | Partial (on-prem agent) |
| Cyclr | Embedded iPaaS | UI-heavy | Triggers + actions | Prebuilt + custom connector tools | Yes (self-hosted private cloud) |
| Pandium | Embedded iPaaS (code-first) | Code-first | Webhooks supported | Auth-focused connectors + code integrations | No public self-host option |
| Ampersand | Embedded iPaaS (code-first) | Code-first | Subscribe to events | Declarative YAML + OSS connectors | No public self-host option (platform) |
| Nango | Integration infrastructure | Code-first | Webhooks + syncs | Prebuilt auth + custom integrations | Yes (limited free self-host; enterprise self-host) |
| n8n | Workflow automation | UI-heavy + code nodes | Webhooks + triggers | Community + core nodes | Yes (self-hosted editions) |
| Pipedream | Workflow automation | Code-first + UI | Webhooks + triggers | App actions + custom code | No (publicly stated) |
| Composio | AI agent tool access | Code-first | Triggers supported | Toolkits + MCP servers | Not stated in docs |
| Metorial | MCP integration platform | Code-first | N/A (agent tool calls) | MCP servers (hosted or OSS) | Yes (open source; self-hostable) |
| Pica | Auth + actions for AI & SaaS | Code-first + embeddable UI | Webhooks supported | AuthKit + Passthrough API | No public self-host option |
| Airweave | Agent data ingestion | Code-first | Sync + retrieval | Connectors for data sources | Yes (open source; self-host or hosted) |
| LiteLLM | LLM gateway | Code-first | N/A | Provider integrations | Yes (OSS self-host; cloud option) |
| Bifrost | LLM gateway | Code-first | N/A | Provider integrations | Yes (self-hostable gateway) |
| Agent Vault | Credential brokerage for AI agents | Code-first (CLI + SDK) | N/A (network-layer proxy) | User-registered services + credentials; no prebuilt connectors | Yes (OSS MIT; binary or Docker) |
| Apache Camel | Routing, mediation, and protocol integration framework | Code-first DSLs + Karavan low-code tooling | Routes, timers, polling, messaging components, Kamelets | Components, route DSLs, Kamelets | Yes (OSS library/runtime; Camel K on Kubernetes) |