Softwr

Automation Integration · head to head

Cyclr vs Hookdeck

Cyclr logo

Cyclr

Automation Integration

Embedded integration platform that SaaS vendors ship inside their own product

From
$1595/month
Rated
-
Full reviewWebsite
Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Hookdeck has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • They diverge on capability: Cyclr covers White-label integration UI, Hookdeck covers Ingest and persist.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cyclr and Hookdeck actually diverge.

Attributes where Cyclr and Hookdeck differ
AttributeCyclrHookdeck
Starting price$1595/monthFree
Pricing modelPer month by API call volumePer month by delivered event count
Free tierNoYes
PlatformsWeb, APIWeb, Linux, macOS, Windows
CategoryAutomation IntegrationDeveloper Tools

Identical on both: user rating (Not yet rated).

What each one covers

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 Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

What people use each 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 Hookdeck
  • A product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectorsnot Hookdeck
  • A European software company that needs its customers' integration data processed inside the EU for procurement reasonsnot Hookdeck
  • A vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connectornot Hookdeck

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Cyclr
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Cyclr
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Cyclr
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Cyclr

Where each one falls 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.

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

Pricing, plan by plan

Cyclr

$1595/month
  • PAYG$1595/month
    • 100,000 API calls included
    • 1 connector included
    • Unlimited integrations and users
  • Growth$2595/month
    • 1,000,000 API calls included
    • 10 connectors included
    • Everything in PAYG
  • Scale$7195/month
    • 5,000,000 API calls included
    • Unlimited connectors
    • Everything in Growth
  • Private Cloud$undefined/month
    • Dedicated hosting in US, UK or EU
    • Configurable processing and runtime
    • Quoted pricing

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated support

Which should you pick?

Choose Cyclr if

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

Choose Hookdeck if

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.
Hookdeck review

Questions people ask

Is Cyclr or Hookdeck better?
Neither clearly leads. Cyclr starts at $1595/month and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cyclr or Hookdeck?
Hookdeck has a free tier; the other does not. Paid plans start at $1595/month for Cyclr and Free for Hookdeck.
Does Cyclr or Hookdeck run on more platforms?
Cyclr runs on Web, API. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use Hookdeck for free?
Yes. Hookdeck has a free tier, so you can try it without paying. Cyclr starts at $1595/month.
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 Hookdeck is typically brought in for.
What can Cyclr do that Hookdeck cannot?
Cyclr covers White-label integration UI, Connector library, Workflow builder, Custom connectors. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

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.

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

Cyclr: Do my customers know they are using Cyclr?

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

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

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

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

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

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.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Share

Related pages

More on Cyclr

More on Hookdeck

Keep looking

Other head to heads