Developer Tools · head to head
Cortex vs Hookdeck
Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Rated
- -
Hookdeck
Developer Tools
Event gateway that receives, queues, retries and replays inbound webhooks
- From
- Free
- Rated
- -
The short version
- Only Hookdeck has a free tier, so it costs nothing to try first.
- Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; 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: Cortex covers Service catalogue, Hookdeck covers Ingest and persist.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Cortex and Hookdeck actually diverge.
Identical on both: user rating (Not yet rated), category (Developer Tools).
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 Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
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.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Hookdeck
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Hookdeck
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Hookdeck
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Hookdeck
Hookdeck
- A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Cortex
- Fanning one provider webhook out to several internal services without each subscribing separatelynot Cortex
- Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Cortex
- Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Cortex
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.
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
Cortex
On request- Cortex$undefined/year
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
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 Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
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.
Questions people ask
- Is Cortex or Hookdeck better?
- Neither clearly leads. Cortex starts at On request and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cortex or Hookdeck?
- Hookdeck has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Hookdeck.
- Does Cortex or Hookdeck run on more platforms?
- Cortex 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. Cortex starts at On request.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Hookdeck is typically brought in for.
- What can Cortex do that Hookdeck cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.
Answered from the vendors’ own pages
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
Hookdeck: Is there a free plan?
Yes, ten thousand events a month with three-day retention and one user.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
Hookdeck: How is usage counted?
By delivered events, so a single inbound webhook fanned out to three destinations counts as three.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
Hookdeck: Can I replay a failed webhook?
Yes, individually or in bulk from the console, with the original payload.
Cortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
Hookdeck: Does it work for outbound webhooks too?
Yes, the same queueing, retry and observability applies to webhooks you send.
Related pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs Earthly
- Cortex vs Spacelift
- Cortex vs Atlantis
- Cortex vs Depot
- Cortex vs Nix
- Cortex vs SonarQube
- Cortex vs Keycloak
- Cortex vs Ona (formerly Gitpod)
- Cortex vs Vite
- Cortex vs Bazel
- Cortex vs Namespace
- Cortex vs Nixpacks
- Cortex vs Octopus Deploy
- Cortex vs Okteto
- Cortex vs Jitsu
- Cortex vs Garden
- Cortex vs Webpack
- Cortex vs Cloud Native Buildpacks
- Cortex vs Dagger
- Cortex vs Visual Studio Code
- Cortex vs Daytona
- Cortex vs Harness
- Cortex vs Ansible
- Cortex vs Coder
- Cortex vs GitLab CI/CD
- Cortex vs HCP Terraform
- Cortex vs Helm
- Hookdeck vs Backstage
- Hookdeck vs OpsLevel
- Hookdeck vs Earthly
- Hookdeck vs Spacelift
- Hookdeck vs Atlantis
- Hookdeck vs Depot
- Hookdeck vs Nix
- Hookdeck vs SonarQube
- Hookdeck vs Keycloak
- Hookdeck vs Ona (formerly Gitpod)
- Hookdeck vs Vite
- Hookdeck vs Bazel
- Hookdeck vs Namespace
- Hookdeck vs Nixpacks
- Hookdeck vs Octopus Deploy
- Hookdeck vs Okteto
- Hookdeck vs Jitsu
- Hookdeck vs Garden
- Hookdeck vs Webpack
- Hookdeck vs Cloud Native Buildpacks
- Hookdeck vs Dagger
- Hookdeck vs Visual Studio Code
- Hookdeck vs Daytona
- Hookdeck vs Harness
- Hookdeck vs Ansible
- Hookdeck vs Coder
- Hookdeck vs GitLab CI/CD
- Hookdeck vs HCP Terraform
- Hookdeck vs Helm