Merge | Compare | Ampersand - Integration Infrastructure vs Unified API

Integration Infrastructure Comparison

Ampersand vs Merge: Integration Infrastructure 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.

Talk to an engineer Read the docs

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.

  • Sub-second real-time sync

    Ampersand's event-driven architecture delivers webhook notifications in under one second. Merge's time-based polling cannot makes it difficult to 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.

  • 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 prices on infrastructure consumption. Merge charges per linked account.

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 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

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

Frequently Asked Questions

  • Can I migrate from Merge without disrupting my customers?

    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.

  • Does Ampersand support the same integrations as Merge?

    Ampersand covers 200+ 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.

  • What does "sub-second webhooks" actually mean?

    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.

  • How does pricing work at scale?

    Ampersand prices on actions. You pay for the infrastructure, not per customer connection. Merge charges per linked account.

  • What if I need custom objects in Salesforce or NetSuite?

    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 higher tiers.

  • Is Ampersand suitable for AI and agentic use cases?

    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 find it difficult to interact with.

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.

Talk to an engineer