Integration Infrastructure Comparison

Ampersand vs Merge:
Depth vs Abstraction

Ampersand delivers real-time, native integrations for AI agents and enterprise workflows. Merge offers broad coverage with a unified API. Here's how they compare for teams building integrations that enterprise customers actually need.

See the Full Comparison ↓ Read the Docs

TL;DR — The Key Differences

Ampersand gives you native API access with full custom object and field support on every plan. No abstraction layer to bypass. Read and write any object or field, standard or custom.
Ampersand is the native integration infrastructure for AI agents. Sub-second webhooks, an open-source AI SDK, and declarative config that agents can read and write make Ampersand agent-ready out of the box. Merge's polling-based unified API introduces latency that breaks agentic and real-time workflows.
Ampersand lets you own and export your OAuth credentials — zero vendor lock-in. Merge holds your customers' tokens, so switching providers means every customer must re-authenticate.
Ampersand delivers sub-second webhooks via event-driven architecture — critical for AI agents, voice products, and real-time workflows. Merge syncs on 15-minute to 24-hour polling intervals.
Ampersand starts at $999/month with transparent usage-based pricing. Merge charges per linked account ($650/mo + $65 per connection), which compounds fast as you scale.
Ampersand skips the abstraction layer entirely so you can support the complex enterprise configurations your customers actually run. Merge uses a unified API that normalizes data into common models — great for standardized fields, but it forces passthrough workarounds for custom objects.

Feature-by-Feature Comparison

How the two platforms stack up across the dimensions that matter most for product integrations.

Dimension	Ampersand	Merge
Philosophy	Depth-first, native API access, declarative framework Best for enterprise	Breadth-first, common data models across categories
Connectors	250+ across 15 categories (CRM, ERP, HRIS, GTM, more)	220+ across 7 categories Broader for HRIS/ATS
Custom Objects	Full native support, all tiers All plans	Passthrough workarounds; field mapping gated to Professional+ Enterprise-gated
Per-Customer Field Mapping	Built-in on every tier with embeddable UI Included	Limited; JMESPath queries on higher tiers
Data Freshness	Sub-second webhooks (event-driven) Real-time	15-min to 24-hour polling/cache Not real-time
Sync Direction	Bi-directional with conflict resolution	Primarily read; write support varies by category
Credential Ownership	You own & export OAuth tokens Your keys	Vendor holds tokens; no documented export Vendor lock-in
Configuration	Declarative YAML in Git + CI/CD pipelines	Dashboard + API configuration
AI / Agent Support	Open-source AI SDK + MCP server; Docs MCP for instant setup Agentic-ready	REST API (no native agent tooling)
Embeddable UI	White-labeled React components for auth, field mapping, sync settings	Merge Link (auth component)
Open Source	250+ connectors as Go libraries on GitHub Inspect + extend	Closed source
Compliance	SOC 2 Type II, GDPR, ISO 27001	SOC 2 Type II, GDPR, HIPAA
Pricing Entry	Free tier → $999/mo (usage-based credits) Transparent	Free for 3 accounts → $650/mo + $65/linked account Scales fast
Implementation Time	Minutes with Docs MCP; 1–2 weeks first deep integration	Hours for unified API; weeks for custom passthrough work

Where Ampersand Wins

The advantages that matter most when you're selling to mid-market and enterprise customers.

🔑

Your Keys, Your Integrations

Ampersand lets you own your customers' OAuth credentials. Import existing tokens from another platform. Export them if you ever leave. Customers never re-authenticate if you switch. Try asking Merge if you can export your credentials.

⚡

Sub-Second Real-Time Sync

Ampersand's event-driven architecture delivers webhook notifications in under one second. 11x cut their AI phone agent's CRM response time from 60 seconds to 5. Merge's 15-minute to 24-hour polling cannot support conversational AI, voice agents, or real-time workflows.

🧩

Full Custom Object Support

Ampersand lets you read and write any object or field — standard or custom — on every tier. Merge's unified API normalizes data into common models, requiring passthrough requests for anything outside the standard schema. When passthrough calls outnumber unified API calls, you're paying for abstraction you're bypassing.

🤖

Built for AI Agents

Ampersand's open-source AI SDK exposes integrations as tools that LLMs can invoke. The Docs MCP lets AI coding agents (Claude Code, Cursor) spin up a functioning integration in minutes. Declarative YAML configs are machine-writable; visual dashboards are not.

📎

Declarative, Version-Controlled

Ampersand lets you define integrations in amp.yaml files that live in Git, integrate with CI/CD, and go through pull requests. Your infrastructure team works in the same workflow as everything else. No context-switching to a separate dashboard.

💰

Transparent, Predictable Pricing

Ampersand uses credit-based, usage-based pricing starting at $999/month. Merge charges $65 per linked account on top of a $650/month base. At 200 customers with 3 connections each, Merge could cost ~$39,000/month. That cost compounds, not simplifies, as you grow.

Pricing at Scale

Integration costs should shrink as a percentage of revenue, not grow. Here's how the economics compare.

Ampersand

$999 /month

✓ Free tier available (5 customers, one-time credit package)
✓ Transparent usage-based credits (1 action = 1 credit)
✓ Custom objects included on all tiers
✓ Per-customer field mappings included on all tiers
✓ Sub-second webhooks included
✓ Credential ownership & export included
✓ SOC 2 Type II, GDPR, ISO 27001
✓ AI SDK & Docs MCP included

Merge

$650 /mo + $65/acct

✓ Free for 3 linked accounts
⚠ Per-linked-account pricing compounds quickly
✗ Custom objects require Professional+ plan (contract-based)
✗ Field mappings limited on lower tiers
✗ 15-min to 24-hour polling (no real-time)
✗ Vendor holds OAuth tokens; no export
✓ SOC 2 Type II, GDPR, HIPAA
✗ No native AI agent tooling

What Customers Say

"Using Ampersand, we cut Julian's response time from 60 seconds to 5."

Muizz Matemilola, Engineering — 11x

"We chose Ampersand because we want to build an integration that we don't need to rebuild, and we want to meaningfully accelerate our upmarket journey."

Kshitij Grover, CTO — Orb

"Ampersand is the first developer platform that gets it right."

Eric Engoron, Engineering — Clay

"Ampersand is core to how we grow."

John Peña, CTO — Hatch (acq. by Yelp)

"Ampersand is helping Square connect to more upmarket Sellers, driving strong revenue growth."

Max Friz, Partnerships Lead — Square

When to Choose Each Platform

We believe in being honest. These tools solve different problems — most teams will eventually want both.

Choose Ampersand When You Need…

✓ Deep CRM/ERP integrations with custom objects and fields
✓ Real-time, sub-second data for AI agents or voice products
✓ Per-customer field mappings without enterprise pricing
✓ Bi-directional sync with conflict resolution
✓ Credential ownership and zero vendor lock-in
✓ Declarative config that AI coding agents can generate
✓ Mid-market and enterprise customers with complex systems
✓ An integration you don't need to rebuild as you scale

Choose Merge When You Need…

✓ Broad, standardized integrations across HRIS/ATS/Accounting
✓ Read-only access to standard fields (no custom objects)
✓ Quick setup for SMB customers with vanilla configurations
✓ A single unified API for shallow, category-wide coverage
✓ Batch data sync where 15-minute+ latency is acceptable

Switching from Merge? It's Painless.

Ampersand supports token import, so your customers don't need to re-authenticate. Start with one integration and expand at your own pace.

Speak with an Engineer →

Frequently Asked Questions

Yes. Ampersand supports OAuth token import, so your existing customers don't need to re-authenticate. You can migrate integrations incrementally — start with one connector and expand over time. Note that Merge does not offer token export, so you'll need to coordinate with your customers for any credentials Merge holds.

Ampersand covers 250+ connectors across 15 categories, including CRM, ERP, HRIS, ticketing, marketing, and more. Merge covers ~220+ across 7 categories. Merge has stronger coverage in HRIS and ATS specifically; Ampersand has deeper coverage in CRM, ERP, and GTM systems. If you need a connector Ampersand doesn't have, their team can build it quickly.

When data changes in your customer's CRM or ERP, Ampersand's event-driven architecture detects and delivers that change to your application in under one second. This is critical for AI agents, voice products, and real-time workflows. Merge uses a polling/caching architecture that typically refreshes data every 15 minutes to 24 hours.

Ampersand uses credit-based pricing: 1 read/write action = 1 credit. The Catalyst plan ($999/month) includes a monthly credit package. You pay for what you use, not per customer connection. Merge charges per linked account ($65 each above the base). A customer who connects 3 systems counts as 3 linked accounts. At scale (200 customers, 3 connections), Merge's model can reach ~$39,000/month vs. Ampersand's predictable usage-based rate.

Ampersand supports custom objects and custom fields natively on every tier. You can read, write, and sync any object — standard or custom — without workarounds. Merge requires passthrough requests for custom objects, and field mapping features are gated to their Professional and Enterprise plans (contract-based pricing).

Ampersand was built with AI agents in mind. The open-source AI SDK exposes integrations as tools that LLMs can invoke. The Docs MCP allows AI coding agents like Claude Code and Cursor to generate integration configurations in minutes. The declarative YAML format is machine-readable and machine-writable — unlike visual dashboards that agents can't interact with.

Ampersand vs Merge: Depth vs Abstraction