Side by Side
At a Glance
14 dimensions of comparison between Naftiko and Hookdeck — same row, different layer of the stack. Scan top-to-bottom to see where each product makes a different choice on the same axis.
Dimension
Naftiko
Hookdeck
Category
Naftiko
Spec-driven integration engine + capabilities catalog
Hookdeck
Managed event gateway for webhook ingress and async delivery
Origin
Naftiko
Kin Lane (API Evangelist) — open-source Apache 2 framework, originated 2026
Hookdeck
Hookdeck Technologies, Inc. — founded Montreal, 2020, raised in 2022
Primary primitive
Naftiko
Capability YAML (alpha2) — declares consumes, exposes, governance metadata
Hookdeck
Source → Connection → Destination model with Transformations as middleware
Layer in the stack
Naftiko
Control plane — authors the handler that gets called
Hookdeck
Data plane — routes and retries the call to the handler
Core artifact
Naftiko
Docker container running the Ikanos JVM engine on a single capability YAML
Hookdeck
Hosted Source URL + persistent Connection topology + Destination delivery state
Open source posture
Naftiko
Apache 2 framework, open YAML spec, open capabilities catalog at capabilities.apis.io
Hookdeck
Closed-source SaaS; CLI + SDKs open-sourced; OpenAPI spec publicly available
Multi-protocol
Naftiko
REST + MCP + Agent Skills + Webhooks (roadmap) from one capability spec
Hookdeck
HTTP/HTTPS in and out; webhook signing verification across 13+ providers
Governance scope
Naftiko
Spec-level — blocking + advisory rules, tags for sensitivity/billing/provenance, Spectral lint, Kyverno admission gates
Hookdeck
Delivery-level — Issues, Issue Triggers, audit log, SOC2, DPA, EU data residency
Discovery surface
Naftiko
capabilities.apis.io public catalog; Backstage plugin auto-catalog from Git or K8s CRDs
Hookdeck
First-party Integrations catalog (Stripe, Shopify, Twilio, SendGrid, GitHub, etc. — 13+ providers wired)
Audit / observability
Naftiko
Per-capability /metrics (Prometheus), /health, structured JSON logs, OTel roadmap
Hookdeck
Per-event + per-attempt history with raw body, replayable bookmarks, queue-depth + latency metrics API
Identity / OAuth
Naftiko
Bearer, Basic, API Key, Digest on consumes; per-operation Bearer / API Key on exposes; OAuth 2.1 on roadmap
Hookdeck
Bearer / Basic auth to the management API; signature verification on inbound webhooks from each integration provider
Cost / FinOps
Naftiko
Spec tags for cost-center attribution; K8s label propagation to Kubecost
Hookdeck
Usage-based pricing — primary meter is API requests/month; tiered (Free 1K / Pro 100K / Enterprise uncapped)
AI / MCP posture
Naftiko
MCP-native — every capability spec exposes a parallel MCP tool surface alongside REST
Hookdeck
Anthropic integration for triaging delivery failures with Claude; no MCP server surface today
Founder framing
Naftiko
Spec-driven multi-protocol exposure as governance — write once, expose REST + MCP + Skills
Hookdeck
Webhooks-as-infrastructure — unglamorous but critical layer that makes webhook architectures reliable at scale
Common Ground
Where They Overlap
Both Naftiko and Hookdeck bet on the layer above per-vendor MCPs. Here are the 8 concrete places where those bets actually meet — same problem, sometimes the same shape, increasingly the same conversation.
1
Both sit at the integration seam
Hookdeck and Naftiko both live where vendor APIs meet internal systems. Hookdeck handles the inbound webhook edge; Naftiko handles the outbound + bidirectional capability edge. The seam itself is the shared ground.
2
Both are spec-first
Hookdeck publishes a versioned OpenAPI (2025-07-01) covering 83 endpoints across 15 resource families. Naftiko publishes a JSON Schema-backed alpha2 YAML spec. Both treat the spec as the source of truth — the api-evangelist/hookdeck repo already carries 17 Naftiko-format capability YAMLs derived from Hookdeck's OpenAPI, proving the spec-to-spec translation path.
3
Both expose CRUD against a structured resource model
Hookdeck has Sources, Destinations, Connections, Transformations, Events, Bookmarks, Issues, Issue Triggers, Bulk Operations, Metrics. Naftiko has Capabilities, Bindings, Consumes, Exposes, Tools, Resources. Both modelled as resources with REST CRUD, both queryable by an MCP-aware client.
4
Both ship pre-built integrations for the major SaaS providers
Hookdeck ships 13 first-party integrations (Stripe, Shopify, Twilio, SendGrid, Slack, Datadog, PagerDuty, AWS SQS, Kafka, Anthropic, Linear, GitHub). Naftiko's capabilities.apis.io catalog publishes capabilities for many of the same — and adds spec-driven authoring on top of the connector.
5
Both treat retry / backoff as first-class
Hookdeck retries failed deliveries automatically with configurable exponential backoff per Connection. Naftiko ships Resilience4j-backed circuit breaker + retry + bulkhead + rate-limiter on every consumes namespace. Both treat the unreliable-network reality as a primitive, not an afterthought.
6
Both have explicit governance tagging
Hookdeck tags Connections with retry policy, filter rules, rate-limit policy; surfaces Issues as governance-relevant events. Naftiko tags everything — consumes, exposes, individual operations — with provenance, sensitivity, billing, agent-safety, lifecycle. Different shapes, same instinct: machine-readable governance is a feature, not docs.
7
Both expose metrics for FinOps / SRE
Hookdeck exposes per-event / per-attempt / per-connection metrics via REST. Naftiko exposes Prometheus metrics per capability container. Both shapes can be aggregated into the same observability backplane (Datadog, Grafana).
8
Both lean into AI integration
Hookdeck ships an Anthropic integration to triage delivery failures with Claude. Naftiko ships MCP exposes on every capability so AI agents can read and act on the resource model directly. Same instinct, different layers.
Where We Diverge
How Naftiko Is Different
Naftiko writes the handler. Hookdeck delivers the event to the handler. The two products are at different layers of the same stack — every Naftiko-built webhook capability deserves a Hookdeck destination in front of it, and every Hookdeck destination deserves a spec-driven Naftiko capability behind it.
1
Layer in the stack
Naftiko
Control plane — authors the capability (the handler). The Naftiko YAML compiles into a Docker container with a live REST + MCP surface.
Hookdeck
Data plane — routes events to the handler. Hookdeck does not author the handler; it is opinionated about delivery, not about what runs at the other end.
These are not competing layers. Naftiko + Hookdeck stack vertically — Hookdeck in front, Naftiko behind.
2
What is the primitive
Naftiko
Capability YAML — declares consumes, exposes, governance metadata, runs as a Docker container.
Hookdeck
Source → Connection → Destination — a hosted webhook URL, a routing edge, and a delivery target with retry policy.
Naftiko's primitive is a spec that becomes a container. Hookdeck's primitive is a managed delivery topology.
3
How webhooks get handled
Naftiko
Webhook handler is authored as a Naftiko capability with consumes/exposes — multi-protocol REST + MCP + Skills generated from the same spec.
Hookdeck
Webhook ingress is a Hookdeck-hosted Source URL with verification, transformation, filter, and retry handled before any code runs.
The natural pairing: Hookdeck Source → Hookdeck Destination → Naftiko-built capability handler.
4
How deliveries get retried
Naftiko
Resilience4j retry + circuit breaker on every consumes namespace, sized per-capability. Concerned with outbound calls.
Hookdeck
Per-Connection retry policy with exponential backoff, manual replay via UI or API, bulk-retry jobs for population recovery.
Naftiko retries when consuming. Hookdeck retries when delivering. Same word, opposite directions.
5
What MCP looks like
Naftiko
Every capability spec exposes a parallel MCP tool surface alongside REST — agents talk to the same primitive humans talk to.
Hookdeck
No MCP server surface today; AI integration is Claude-as-triage-helper for delivery failures (one-way analysis, not agentic execution).
Naftiko's MCP-native posture is the most natural path for Hookdeck to add an agent-facing surface — wrap the Hookdeck OpenAPI as a Naftiko capability and you get the MCP server for free.
6
What governance means
Naftiko
Spec-level governance — blocking rules (HTTPS, auth required, version), advisory rules (cost-center, billing, PII auth), Spectral lint, Kyverno admission gates.
Hookdeck
Delivery-level governance — Issues for escalated failures, Issue Triggers for SLO-style rules, audit log, SOC2, DPA, EU residency for compliance.
Spec governance and delivery governance are complementary. Naftiko governs what is written. Hookdeck governs what is delivered.
7
Open-source posture
Naftiko
Apache 2 framework, open YAML spec, open capabilities catalog. Everything checked into Git is the source of truth.
Hookdeck
Closed-source SaaS. OpenAPI spec is public. CLI and SDKs are open-sourced. The runtime is the product.
Naftiko-the-engine is freely runnable; Hookdeck-the-service is managed. Different commercial wedges.
8
Commercial wedge
Naftiko
Open-source Framework engine (free); paid Signals (enterprise intelligence) when shipped; bottom-up adoption via Fleet developer tooling.
Hookdeck
Tiered SaaS — Free 1K req/month / Professional 100K req/month / Enterprise uncapped with SLA, dedicated support, data residency.
Naftiko's revenue lives upstream of capability authoring. Hookdeck's revenue lives in metered ingress + delivery.
Partnership Thesis
Service Partnership
Hookdeck and Naftiko are not competitors — they are different layers of the same webhook-driven architecture. Hookdeck is the managed gateway that guarantees a webhook gets delivered. Naftiko is the spec-driven engine that produces the handler the webhook gets delivered to. Every Naftiko capability with a webhook-handler expose is a natural Hookdeck destination, and every Hookdeck destination is a natural target for a Naftiko-built capability. The integration is bidirectional: Naftiko publishes the OpenAPI of its capability handlers so Hookdeck can auto-register destinations; Hookdeck publishes its delivery metrics + Issues + Bookmarks so Naftiko governance dashboards can show event-plane state alongside capability-plane state.
“Naftiko + Hookdeck = spec-driven capabilities sitting behind a managed event gateway, with SLA-grade webhook delivery in front and multi-protocol REST + MCP + Agent Skills behind.”
Two First-Meeting Questions
Q1. How would joint customers wire a Hookdeck destination at a Naftiko capability?
The natural pattern is: a developer authors a Naftiko capability with a webhook-handler REST expose, the deploy pipeline reads the capability's OpenAPI, and the hookdeck-spec-driven-destination capability (in this partnership map) auto-creates the matching Hookdeck Destination. The question is whether Hookdeck would want to ship the Naftiko-as-spec-source pattern as a first-class deployment template — equivalent to your existing Integrations catalog but for the handler-side rather than the provider-side.
Q2. Should Hookdeck become an MCP server via Naftiko?
Naftiko already runs the api-evangelist/hookdeck repo with 17 alpha2 capability YAMLs that wrap the Hookdeck OpenAPI as MCP tools. Wrapping the Hookdeck API as Naftiko capabilities is the cheapest path to a Hookdeck MCP server — agents could list sources, retry events, dismiss issues, and orchestrate bulk recovery jobs through a single MCP surface. The partnership question: do you want to co-promote this surface, brand it as 'Hookdeck MCP powered by Naftiko', or absorb the pattern into the Hookdeck product directly?
Integration Kit
Partnership Capability Map
12 Naftiko capabilities authored to integrate with Hookdeck as a service partner. Each one consumes a specific Hookdeck surface and exposes it as REST + MCP through the Naftiko engine — shipped as inline alpha2 YAML in the api-evangelist repository and published to the apis.io capability catalog.
Hookdeck Sources Discovery
hookdeck-sources-discovery
Read-only discovery of Hookdeck Source resources for Naftiko Fleet inventory and agent introspection.
Hookdeck Destinations Registry
hookdeck-destinations-registry
Read-only inventory of Hookdeck Destination resources so Fleet can show which Naftiko containers sit behind a Hookdeck destination.
Hookdeck Connections Topology
hookdeck-connections-topology
Surfaces the live source → destination edge graph as a Naftiko REST + MCP surface for topology visualization and governance audits.
Hookdeck Spec-Driven Destination
hookdeck-spec-driven-destination
Auto-creates Hookdeck Destinations from a Naftiko capability's REST expose so capability deploys and gateway config stay in lockstep.
Hookdeck Events Replay
hookdeck-events-replay
Surgical event-by-id tooling for Naftiko-built webhook handlers — get / retry / cancel / mute single events.
Hookdeck Issues Triage
hookdeck-issues-triage
Pulls Hookdeck Issues into Naftiko governance dashboards and gives agents a tool to list / get / dismiss escalated delivery failures.
Hookdeck Transformations Author
hookdeck-transformations-author
CRUD on Hookdeck Transformations so a Naftiko-published normalizer (Stripe → canonical etc.) becomes a Hookdeck transformation.
Hookdeck Bookmarks Snapshot
hookdeck-bookmarks-snapshot
Pins named replay cursors for audit and rollback — useful before risky Naftiko capability deploys.
Hookdeck Metrics Bridge
hookdeck-metrics-bridge
Bridges Hookdeck event-plane metrics (events, attempts, queue depth, connections) into Naftiko governance dashboards.
Hookdeck Issue Trigger Author
hookdeck-issue-trigger-author
CRUD on Hookdeck Issue Triggers so SLO-style alerting rules can be generated from Naftiko capability reliability tags.
Hookdeck Bulk Retry Orchestrator
hookdeck-bulk-retry-orchestrator
Kicks off bulk retry / cancel / ignored-event recovery jobs from an MCP tool — built for the 'Naftiko handler came back up at 3am' scenario.
Hookdeck Integrations Catalog
hookdeck-integrations-catalog
Surfaces Hookdeck's first-party integrations (Stripe, Shopify, Twilio, etc.) so Naftiko discovery agents can cross-reference Hookdeck-native providers against Naftiko capabilities.
