Data Integration & iPaaS
139 martech vendors in Data Integration & iPaaS, part of Data, Analytics & Measurement. Each record carries the date we last verified it, so you can see how current it is before you rely on it.
Last verified:
Procurement-readiness profiles — SOC 2, ISO 27001, GDPR and DPA posture, data residency, AI-training policies — are available when you sign in.
Data integration and iPaaS software connects separate systems and moves data between them on a schedule or in real time, replacing one-off custom scripts with a managed pipeline. IT and data teams depend on it to keep everything else in sync; security reviewers need it audited because it holds the credentials to every connected system at once.
Who it is for
- IT and data engineering leads shortlisting a platform to replace fragile custom scripts with managed, monitored pipelines.
- IT security reviewers assessing how stored credentials for every connected downstream system are protected in one place.
- Data governance teams confirming what data actually passes through the platform in transit, even when it isn't stored there long-term.
What your No-Committee will ask
- IT security
- Are stored connection credentials and API keys for every linked system encrypted, and is admin access to pipeline configuration protected by MFA? Credential encryption and MFA support are each recorded as an evidenced claim, marked verified, self-attested, or not found.
- Data governance
- Does data passing through the platform get logged or cached in transit, and where does that log data sit if so? We confirm data location and DPA coverage against the vendor's own legal pages, not a marketing FAQ.
- AI governance
- If the platform uses AI to suggest field mappings or transform logic on its own, is that labeled clearly, and does the model learn from data flowing through a customer's own pipelines? We track the label and the training question as one combined claim.
- Legal
- Does the vendor publish a sub-processor list, given that this platform sits between every other vendor's own data flows? Sub-processor disclosure is recorded with a link back to where the vendor names its infrastructure partners.
- Risk / finance
- A silent sync failure here can quietly break several other systems downstream, so does the vendor publish an uptime SLA and a status page for past pipeline incidents? We record both wherever the vendor makes them public.
How we verify
Every claim above comes from the vendor's own public pages — trust center, privacy policy, or security page — never inferred from a connector-count marketing page. The full breakdown of what verified, self-attested, and not-found each require is on our methodology page.
Frequently asked questions
How is iPaaS different from a customer data platform?
A customer data platform builds and owns a unified customer profile for activation. Data integration and iPaaS software instead moves data between systems generally, including feeding a CDP its raw inputs or moving a CDP's output elsewhere. The two are often complementary rather than substitutes for each other.
Do iPaaS vendors typically publish SOC 2 or ISO 27001 certification?
Platforms handling credentials for many enterprise systems at once more often publish a SOC 2 report, since a breach here has outsized downstream reach. Smaller or workflow-automation-focused tools more often rely on a general security page without independent certification, which our audits mark as self-attested rather than verified.
Is pricing usually based on tasks run or on the number of connections?
Most vendors price by monthly task or operation volume once a free tier is exceeded, with some also charging per active connector or workflow. Enterprise tiers with custom connectors or dedicated infrastructure are more often quote-only, which we note rather than estimate from a published starting price.
What should I check beyond the connector catalog before shortlisting a platform?
Confirm how credentials for connected systems are stored and rotated, what happens to in-transit data if a sync fails partway, and whether the vendor publishes a status page for past incidents. A pipeline this central to daily operations deserves the same scrutiny as the systems it connects.