Softwr

Automation Integration · head to head

Merge vs Testsigma

Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Free plan
Yes
Testsigma logo

Testsigma

Testing

Natural language test automation for web, mobile and API with a self hosted open source edition

From
Free
Free plan
Yes

The short version

  • Merge is a unified API platform.
  • Testsigma is free; Merge starts at $650/mo.
  • Only Merge lists HRIS integrations; only Testsigma lists self hosted community edition.
  • Where Merge falls short: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings.
  • Where Testsigma falls short: support and engineering are concentrated in Indian time zones, which slows incident turnaround for teams working in the Americas.
  • Prices and features on this page were last checked on 20 November 2026.

How do Merge and Testsigma differ?

Merge and Testsigma differ on pricing model (Usage-based against Per user per month), platforms and category. Only the attributes on which Merge and Testsigma actually diverge.

Attributes where Merge and Testsigma differ
AttributeMergeTestsigma
Pricing modelUsage-basedPer user per month
PlatformsAPIWeb, iOS, Android, Linux
CategoryAutomation IntegrationTesting

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Testsigma.

Which features does each one have?

They share no listed features; 20 appear only for Merge and 6 only for Testsigma. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

Only in Testsigma

  • Natural language authoring
  • Unified web, mobile and API tests
  • Self hosted community edition
  • Cloud device and browser grid
  • Data driven runs
  • Custom functions

What is each one used for?

Merge is most often brought in for workflow Automation. The jobs each tool is most often brought in to do.

Merge

  • Workflow Automationnot Testsigma
  • Data Integrationnot Testsigma
  • Process Automationnot Testsigma
  • App Integrationnot Testsigma
  • API Connectivitynot Testsigma

Testsigma

  • A team maintaining separate Selenium and Appium suites that wants one place for web and native mobile coveragenot Merge
  • Organisations that must keep test data and execution on premises for regulatory reasonsnot Merge
  • QA groups with manual testers being asked to automate without first learning Javanot Merge
  • Evaluating low code test automation properly before committing budget, by running the free edition against the real applicationnot Merge

Where do Merge and Testsigma fall short?

Merge's most cited limit: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

Testsigma

  • The natural language layer is a fixed vocabulary rather than real English, so testers spend the first weeks learning which phrasings the parser accepts, which is learning a language after all
  • Anything conditional or arithmetic falls through to custom Java or JavaScript, and that code lives in the platform editor rather than your repository, where it gets no code review and no version history you control
  • The community edition lags the cloud product and is not the version the vendor demonstrates, so a self hosted evaluation can understate or overstate what you would actually buy
  • Cloud execution is billed separately from authoring seats, so a suite that grows from two hundred to two thousand tests changes the bill without anyone changing the plan
  • Support and engineering are concentrated in Indian time zones, which slows incident turnaround for teams working in the Americas

How much do Merge and Testsigma cost?

Merge has a free plan, with paid plans from $650/mo; Testsigma is free to use. Plan by plan below, from each vendor's own pricing page.

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/mo
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2,500/mo
    • Unlimited accounts
    • Priority support
    • SLA
  • EnterpriseOn request
    • Dedicated support
    • Custom contracts
    • Advanced security

Testsigma

Free
  • Community EditionOn request
    • Self hosted, open source, no licence fee
    • You supply the infrastructure and the browser or device grid
  • CloudOn request
    • Priced per authoring user with additional charges for parallel cloud executions and device minutes
    • Published tiers exist but the figures that matter at team scale come from sales
  • ProOn request
  • EnterpriseOn request

Which should you pick?

Choose Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on API.
  • You also want hris integrations.

Choose Testsigma if

  • You need natural language authoring.
  • You want to start without paying.
  • You work on Web, iOS, Android, Linux.
  • You also want unified web, mobile and api tests.

Questions people ask

Is Merge or Testsigma better?
Neither clearly leads. Merge starts at Free and Testsigma at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Merge or Testsigma?
Merge starts at Free and Testsigma at Free.
Does Merge or Testsigma run on more platforms?
Merge runs on API. Testsigma runs on Web, iOS, Android, Linux.
Can I use Merge for free?
Both have a free tier, so you can try either at no cost before committing.
What is Merge best used for?
Merge is most often used for workflow automation, data integration, process automation, app integration. Of those, workflow automation and data integration are not what Testsigma is typically brought in for.
What can Merge do that Testsigma cannot?
Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations. Testsigma covers Natural language authoring, Unified web, mobile and API tests, Self hosted community edition, Cloud device and browser grid.

Answered from the vendors’ own pages

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
Testsigma: Is the open source edition genuinely usable in production?

Yes for self hosted execution, though it trails the cloud version on newer features and you maintain the grid yourself.

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
Testsigma: Do testers need to know Selenium?

Not to write ordinary steps. They will need someone who does as soon as the suite needs custom functions or awkward waits.

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

Testsigma: Can it test native iOS and Android applications?

Yes, through Appium underneath, on the hosted device grid or your own devices.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

Share

Related pages

Other head to heads