Softwr

Automation Integration · head to head

Cyclr vs Immuta

Cyclr logo

Cyclr

Automation Integration

Embedded integration platform that SaaS vendors ship inside their own product

From
$1595/month
Free plan
No
Immuta logo

Immuta

Databases

Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery

From
On request
Free plan
No

The short version

  • Cyclr starts at $1595/mo; Immuta prices on request.
  • Only Cyclr lists white-label integration UI; only Immuta lists attribute-based policy.
  • Prices and features on this page were last checked on 31 August 2026.

How do Cyclr and Immuta differ?

Cyclr and Immuta differ on starting price ($1595/month against On request), pricing model and category. Only the attributes on which Cyclr and Immuta actually diverge.

Attributes where Cyclr and Immuta differ
AttributeCyclrImmuta
Starting price$1595/monthOn request
Pricing modelPer month by API call volumeQuote
CategoryAutomation IntegrationDatabases

Identical on both: free tier (No), platforms (Web, API).

Which features does each one have?

They share no listed features; 8 appear only for Cyclr and 8 only for Immuta. 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 Cyclr

  • White-label integration UI
  • Connector library
  • Workflow builder
  • Custom connectors
  • Regional hosting
  • MCP server offering
  • Usage metering
  • Templates

Only in Immuta

  • Attribute-based policy
  • Native enforcement
  • Dynamic masking
  • Row-level filtering
  • Purpose-based access
  • Sensitive data tagging
  • Audit logging
  • Multi-platform

What is each one used for?

The jobs each tool is most often brought in to do.

Cyclr

  • A mid-market SaaS vendor losing deals because prospects ask for a CRM integration it has not builtnot Immuta
  • A product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectorsnot Immuta
  • A European software company that needs its customers' integration data processed inside the EU for procurement reasonsnot Immuta
  • A vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connectornot Immuta

Immuta

  • A bank whose Snowflake estate has grown to tens of thousands of roles that no one can review before an auditnot Cyclr
  • A healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recordednot Cyclr
  • A multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasetsnot Cyclr
  • An organisation running both Snowflake and Databricks that wants one policy set rather than two divergent implementationsnot Cyclr

Where do Cyclr and Immuta fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cyclr

  • Entry pricing of 1,595 US dollars a month for one connector and 100,000 API calls means small vendors will find building two or three integrations in-house genuinely cheaper, and Cyclr only pays off past a certain integration count
  • Connectors and API calls are metered separately, so a successful integration marketplace pushes you up tiers as your customers adopt it, meaning the cost rises with usage rather than with the revenue that usage generates
  • Custom connectors to APIs outside the library are your work to build and maintain, so the promise of not building integrations only holds for applications Cyclr already covers
  • Debugging is harder when the integration runs in a third-party runtime, because your support team sees a failed workflow rather than an HTTP response and has to escalate to Cyclr for anything non-obvious
  • Deep embedding creates real switching cost: your customers' live integrations run on Cyclr, so migrating later means recreating every customer workflow, which in practice means you rarely leave

Immuta

  • Contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate
  • Policy is only as good as the data classification underneath it, so an organisation with poorly tagged columns will spend months on classification before Immuta enforces anything useful
  • Native enforcement means capability varies by platform, and a feature available on Snowflake may be absent or behave differently on BigQuery, which undermines the promise of one policy set everywhere
  • Adding an access governance layer creates a new dependency in the path to data: a misconfigured policy silently returns fewer rows rather than erroring, and analysts can act on incomplete results without noticing
  • It governs cloud data platforms, so personal data in operational databases, files and SaaS applications sits outside its scope and needs separate controls, meaning Immuta is rarely the whole answer

How much do Cyclr and Immuta cost?

Cyclr starts at $1595/mo; Immuta is priced on request. Plan by plan below, from each vendor's own pricing page.

Cyclr

$1595/month
  • PAYG$1,595/mo
    • 100,000 API calls included
    • 1 connector included
    • Unlimited integrations and users
  • Growth$2,595/mo
    • 1,000,000 API calls included
    • 10 connectors included
    • Everything in PAYG
  • Scale$7,195/mo
    • 5,000,000 API calls included
    • Unlimited connectors
    • Everything in Growth
  • Private CloudOn request
    • Dedicated hosting in US, UK or EU
    • Configurable processing and runtime
    • Quoted pricing

Immuta

On request
  • Immuta PlatformOn request
    • Attribute-based policy authoring
    • Native enforcement in supported data platforms
    • Dynamic masking and row-level security

Which should you pick?

Choose Cyclr if

  • You need white-label integration ui.
  • You work on Web, API.
  • You also want connector library.

Choose Immuta if

  • You need attribute-based policy.
  • You work on Web, API.
  • You also want native enforcement.

Questions people ask

Is Cyclr or Immuta better?
Neither clearly leads. Cyclr starts at $1595/month and Immuta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cyclr or Immuta?
Cyclr starts at $1595/month and Immuta at On request.
Does Cyclr or Immuta run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Cyclr best used for?
Cyclr is most often used for a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built, a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors, a european software company that needs its customers' integration data processed inside the eu for procurement reasons, a vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connector. Of those, a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built and a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors are not what Immuta is typically brought in for.
What can Cyclr do that Immuta cannot?
Cyclr covers White-label integration UI, Connector library, Workflow builder, Custom connectors. Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering.

Answered from the vendors’ own pages

Cyclr: What does Cyclr actually cost?

Published tiers start at 1,595 US dollars per month for 100,000 API calls and one connector, rising to 7,195 for unlimited connectors and five million calls.

Immuta: Does Immuta sit in the query path?

No. It compiles policies into the data platform's own native controls, so queries run at normal speed through your existing tools.

Cyclr: Do my customers know they are using Cyclr?

No. The interface is white-labelled to appear as part of your product.

Immuta: What does it cost?

Not published. Market data suggests roughly 100,000 to 200,000 US dollars a year for mid-market deployments and considerably more at enterprise scale.

Cyclr: Can I host it in the EU or UK?

Yes, on the private cloud tiers, which matters for European procurement requirements.

Immuta: Is Immuta still independent?

Yes. It remains independently owned, unlike several competitors in data access governance that have been acquired.

Cyclr: What if the connector I need does not exist?

You build a custom connector using Cyclr tooling, which is work you own rather than work the platform removes.

Immuta: Does it work across more than one warehouse?

Yes, one policy set can target Snowflake, Databricks, BigQuery and Starburst, though enforcement capability varies by platform.

Share

Related pages

Other head to heads