Paragon
Embedded integrations for SaaS — ship native third-party integrations inside your product.
About
Paragon is an embedded integration platform (iPaaS) for B2B SaaS companies: instead of building every customer-requested integration yourself, you configure integrations once and your end customers connect their own third-party accounts through a white-labeled Connect Portal inside your product. Founded in 2019 in Los Angeles, it raised a $13M Series A in 2022 and has grown into the premium option in the embedded-integration space.
The platform covers 130+ pre-built connectors with 1,000+ actions, a low-code workflow builder plus code support, managed OAuth 2.0 per Connected User, managed sync pipelines, and custom actions from OpenAPI specs. The newer ActionKit layer adds an agent surface on top: an API and a hosted MCP server exposing your integrations as tools, plus event triggers (launched August 2026) so agents can subscribe to Slack, HubSpot, or Salesforce events rather than only firing writes. Enterprise options include self-hosting and forward deployment.
Pricing is usage-based per Connected User and quote-based — there is no public pricing page, and it is a sales-led product aimed at mid-market and enterprise SaaS. The platform itself is closed; the MCP adapter over its API is MIT, which is a nice touch for agent builders but does not change the underlying lock-in calculus.
What it can do
- 130+ pre-built connectors with 1,000+ actions; custom APIs via SDK and OpenAPI imports
- White-label Connect Portal with managed OAuth per Connected User (tenant)
- ActionKit: API + hosted MCP server exposing integrations as agent tools; event triggers
- Managed sync pipelines, low-code workflow builder, headless mode
- SOC 2 Type II, GDPR; enterprise self-host / forward-deploy options
Setup
- Talk to sales or start the build-for-free tier and create a Paragon project.
- Configure integrations and workflows in the dashboard; generate a signing key for SDK auth.
- Embed the Connect Portal in your app with the Connect SDK (or headless).
- Issue RS256-signed JWT user tokens from your backend so each Connected User authenticates their own third-party accounts.
Prerequisites
A Paragon project and signing key; backend code to mint JWT user tokens per Connected User. Production plans require a sales conversation.
Use cases
Works with
Trust score — 7/10
Scored 7/10 (metrics tier, metrics-v1). Evidence: Closed SaaS, no public repo; founded 2019 (LA), $13M Series A 2022 — verified via CB Insights profile (403 on direct fetch, facts cross-checked against 2026 comparison coverage); Embedded iPaaS: 130+ connectors, 1,000+ actions, white-label Connect Portal, managed OAuth per Connected User; ActionKit agent layer (API + hosted MCP, triggers launched Aug 2026) — verified via 2026 comparison articles and docs; Pricing quote-based, usage per Connected User; SOC 2, GDPR, on-prem option — verified. Manual review: connector counts and trigger dates are provider/dated-press stated; enterprise sales motion and closed platform are the honest tradeoffs. License: Closed SaaS.
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 7.0/10
- Maintenance · recency, releases, issue load
- 8.0/10
- Openness · license + docs
- 5.0/10
- Manual review · sanity read + red-flag check
- 8.0/10
- · Closed SaaS, no public repo; founded 2019 (LA), $13M Series A 2022 — verified via CB Insights profile (403 on direct fetch, facts cross-checked against 2026 comparison coverage)
- · Embedded iPaaS: 130+ connectors, 1,000+ actions, white-label Connect Portal, managed OAuth per Connected User; ActionKit agent layer (API + hosted MCP, triggers launched Aug 2026) — verified via 2026 comparison articles and docs
- · Pricing quote-based, usage per Connected User; SOC 2, GDPR, on-prem option — verified
- · manual review: connector counts and trigger dates are provider/dated-press stated; enterprise sales motion and closed platform are the honest tradeoffs
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.