Side by Side
At a Glance
14 dimensions of comparison between Naftiko and Jentic — 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
Jentic
Category
Naftiko
Spec-driven integration platform
Jentic
Standards-based control plane for AI agents — search → load → execute over 1,500+ APIs + 2,000+ Arazzo workflows
Origin
Naftiko
Kin Lane (API Evangelist) + Jerome Louvel (Restlet → Talend → Qlik), 2025
Jentic
Jentic (Dublin), founded late 2024, $4.5M pre-seed
Primary primitive
Naftiko
Capability — declared in YAML; consumes + exposes
Jentic
Operation (op_*) + Workflow (wf_*, Arazzo) + Agent
Layer in the stack
Naftiko
Build-time + ship-time + runtime engine that authors integrations
Jentic
Hosted control plane that searches, hydrates, and executes catalog entries on behalf of any agent
Core artifact
Naftiko
YAML capability spec (declarative)
Jentic
Arazzo workflow spec (OpenAPI Initiative standard) + OpenAPI operation
Open source posture
Naftiko
Apache 2.0 Framework, free Fleet community, paid Standard / Enterprise
Jentic
Arazzo Engine, Standard Agent, Jentic Mini all open source; hosted control plane is SaaS
Multi-protocol exposure
Naftiko
REST + MCP + Skills + A2A (roadmap) — same capability, all protocols
Jentic
Hosted REST API + Remote MCP server (api.jentic.com/mcp, OAuth + API key)
Workflow standard
Naftiko
Naftiko capability YAML (custom spec); Arazzo on roadmap
Jentic
Arazzo first-class — every workflow is Arazzo, UUIDs prefixed wf_, vocabulary lists Arazzo as canonical
Discovery surface
Naftiko
Backstage capability catalog + scorecards
Jentic
Hosted semantic search (search → load → execute), 1,500+ public APIs + 2,000+ Arazzo workflows
Audit / observability
Naftiko
OpenTelemetry + Prometheus + structured logs
Jentic
Per-execution_id with agent_uuid + api_name + execution_type + status (FOCUS-aligned)
Identity / OAuth
Naftiko
Runtime secret injection (env, ExternalSecrets); Keycloak / OpenFGA roadmap
Jentic
Server-side credential vault — agents never hold tokens; agent-scoped API key + OAuth/PKCE for MCP
Agent framework
Naftiko
Bring-your-own (any agent that speaks REST / MCP / Skills)
Jentic
Standard Agent (open-source ReWOO Python reference) + BYOL for Claude / ChatGPT / Cursor / Windsurf / VS Code
Cost / FinOps
Naftiko
Cost-center labels propagated to K8s; Kubecost integration
Jentic
Subscription + usage; meters: workflow_executions, operation_executions, integrations_used, agent_runs, seats, mcp_calls, search_queries, load_calls, data_egress
Founder framing
Naftiko
“Capability fleet” — many ships, one navy
Jentic
“Standards-based control plane for AI agents” — JITT, Arazzo-first, MCP-native
Common Ground
Where They Overlap
Both Naftiko and Jentic 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 bet hard on OpenAPI as the foundational spec
Jentic's catalog is OpenAPI-driven (every operation is op_*, every spec is canonical OpenAPI). Naftiko's capability spec consumes OpenAPI imports natively (Postman → OpenAPI → capability). Both refuse the ‘hand-write tool descriptions in JSON’ anti-pattern.
2
Both treat MCP as first-class infrastructure
Jentic publishes a Remote MCP server at api.jentic.com/mcp with OAuth/PKCE for Claude Desktop, ChatGPT, Cursor, Windsurf, and VS Code. Naftiko's
exposes: mcp adapter ships MCP servers from any capability YAML. Neither product treats MCP as bolted on.3
Both reject vendor-MCP-per-app sprawl
Jentic's pitch is ‘single agent-scoped API key over 1,500+ APIs’ — one MCP / one credential / one catalog. Naftiko's pitch is ‘vendor MCPs are too generic; compose your own.’ Same realization on both sides — vendor MCPs aren't enterprise-shaped.
4
Both are open-source-first on the engine layer
Jentic ships Arazzo Engine, Standard Agent, and Jentic Mini all as open source for self-hosted execution. Naftiko's Framework is Apache 2.0 with paid Fleet on top. Both refuse the ‘the engine is closed source, only the SDK is OSS’ pattern.
5
Both centralize credentials away from the agent
Jentic's server-side credential vault injects credentials into operations + workflows so agents never see raw tokens. Naftiko's runtime secret injection (env + ExternalSecrets) takes the same posture from the engine side. Both refuse to let agents hold long-lived credentials.
6
Both treat governance as load-bearing, not optional
Jentic ships JAIRF (Jentic AI-Readiness Framework) — a scoring rubric for how operable / interpretable an API is for agents. Naftiko ships Spectral + OPA + runtime checks. Different shapes, same insistence: agent-era governance is load-bearing infrastructure.
7
Both ship a hosted catalog as a discovery moat
Jentic ships 1,500+ APIs and 2,000+ Arazzo workflows out of the box. Naftiko Fleet ships a Backstage capability catalog with scorecards + dependency graphs. Both refuse the ‘every team rebuilds the same integration’ anti-pattern.
8
Both publish a FOCUS-aligned FinOps model
Jentic publishes a per-execution + per-meter billing model with FOCUS-aligned dimensions (agent_uuid + api_name + execution_type + status). Naftiko propagates cost-center labels into Kubecost for per-call attribution. Both refuse the ‘no per-call cost visibility’ anti-pattern.
Where We Diverge
How Naftiko Is Different
The clearest single-sentence difference: Jentic ships a hosted catalog of pre-built operations and Arazzo workflows; Naftiko ships an open-source spec-driven engine for authoring your own capabilities. Same standards stack (OpenAPI + Arazzo + MCP), different positions in it — Jentic is upstream catalog; Naftiko is downstream engine.
1
Hosted catalog vs spec-driven authoring engine
Naftiko
Author any integration as a YAML capability — declare consume + expose + governance. Bring-your-own integration depth. Naftiko engine runs the artifact in customer infra.
Jentic
Consume any of 1,500+ pre-curated APIs and 2,000+ Arazzo workflows from the hosted catalog through a single agent-scoped API key. Maximum out-of-the-box breadth.
Different bets on where the value lives — pre-curated catalog (Jentic) vs spec-driven authoring (Naftiko).
2
Arazzo-first vs Naftiko-spec-first
Naftiko
Naftiko capability YAML is the authoring primitive — captures consume + expose + orchestration + governance in one spec. Arazzo support on the roadmap.
Jentic
Arazzo is the workflow primitive — every multi-step recipe is Arazzo, every wf_* UUID resolves to an Arazzo spec. The OpenAPI Initiative's workflow standard is load-bearing.
Convergence likely — Naftiko could absorb Arazzo as a workflow alternative; Jentic could expose Naftiko-shaped output. Standards-aligned products have the easiest partnership path.
3
Capabilities as the primitive vs Operations + Workflows + Agents
Naftiko
Primary identity is ‘the thing that does X’ — a functional unit composed from declared consumes and exposes.
Jentic
Three primitives: Operation (atomic API call), Workflow (Arazzo recipe), Agent (consumer with scoped API key). Different layer of abstraction.
4
Three governance altitudes vs JAIRF + scope governance
Naftiko
Spectral rulesets at design time, Kyverno / OPA at admission time, runtime checks in the engine. Lifecycle-shaped governance.
Jentic
JAIRF readiness scoring + agent-scoped API key + agent-level allow-list enforced server-side. Catalog-level + agent-level governance.
5
Builds MCP servers from any source vs ships hosted MCP for the catalog
Naftiko
Any consumed API (REST / file / HTML / event stream) becomes an MCP server through
exposes: mcp. Author decides the MCP shape.Jentic
Hosted Remote MCP server exposes search → load → execute over the entire Jentic catalog with one OAuth/API-key handshake.
Same protocol, different scope. Naftiko = author the MCP; Jentic = wrap the catalog as one MCP.
6
Customer-controlled execution vs hosted execution (with self-hosted option)
Naftiko
Naftiko engine runs in customer container / Kubernetes / VPC. Customer controls the data plane, network egress, secrets, storage.
Jentic
Default execution is hosted (Jentic infrastructure). Self-hosted via Jentic Mini open-source execution layer for air-gapped / regulated workloads.
7
Open expose surface vs catalog-bounded surface
Naftiko
Any capability can expose REST + MCP + Skills + A2A. Exposed surface is whatever the capability author declares.
Jentic
Exposed surface is bounded by Jentic's curated catalog (1,500+ APIs + 2,000+ workflows). Custom integrations require enterprise tier ingestion.
8
Naftiko as engine layer vs Jentic as catalog layer
Naftiko
Sits at the engine / authoring layer — defines and runs capabilities, brings governance + observability natively.
Jentic
Sits at the catalog / control-plane layer — defines what's findable, governs what's executable, brokers credentials. Doesn't compete on engine authoring.
Most-aligned partnership shape across all comparisons so far — both products want the same standards outcome from opposite directions.
Partnership Thesis
Service Partnership
Jentic and Naftiko are the most standards-aligned products in this comparison set — both bet hard on OpenAPI, Arazzo, and MCP from opposite positions in the same stack. The 10 capabilities below treat every Jentic API surface as a Naftiko-consumable one and treat every Naftiko expose as a Jentic-publishable one — the entire Jentic catalog (1,500+ APIs + 2,000+ Arazzo workflows) becomes consumable from a Naftiko capability, JAIRF AI-Readiness scores enrich Naftiko Signals, and the open-source Arazzo Engine becomes a self-hosted execution alternative for air-gapped Naftiko deployments.
“Jentic ships the standards-aligned catalog of agent-ready APIs and Arazzo workflows. Naftiko ships the spec-driven engine that consumes them, governs them, and re-exposes them as multi-protocol capabilities. Together: every standards-conformant API in the world becomes a governed, observable, multi-protocol capability inside the customer's infrastructure.”
Two First-Meeting Questions
Q1. Naftiko consumes the entire Jentic catalog as one capability
Would Jentic support a documented ‘wrap me as a Naftiko capability’ pattern — where a single Naftiko capability YAML can search-load-execute against the hosted Jentic catalog (or against a self-hosted Arazzo Engine instance) so 1,500+ APIs become Naftiko-reachable through one declared dependency? The capability map below treats every Jentic surface as Naftiko-consumable for exactly this reason.
Q2. Naftiko-built Arazzo workflows back into the Jentic catalog
Would Jentic open a path for Naftiko-authored Arazzo workflows to land in the Jentic catalog as customer-published workflows — so Naftiko's spec-driven authoring engine becomes a publish path for Jentic's catalog of 2,000+ Arazzo workflows? Both products produce Arazzo today (Naftiko via export, Jentic natively) — the bridge is a one-page submission flow.
Integration Kit
Partnership Capability Map
10 Naftiko capabilities authored to integrate with Jentic as a service partner. Each one consumes a specific Jentic 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.
Jentic Search
jentic-search
Call Jentic's semantic search API over its 1,500+ APIs and 2,000+ Arazzo workflows; surface ranked op_/wf_ results into Naftiko Fleet for tool discovery.
Jentic Load
jentic-load
Hydrate execution specs (method, path, JSON Schema, auth) for one or more Jentic operations or workflows by UUID — the JITT pattern that avoids preloading 1,500+ tools.
Jentic Execute
jentic-execute
Execute a Jentic operation (op_*) or Arazzo workflow (wf_*) with server-side credential injection. Returns execution_id for downstream observability correlation.
Jentic Arazzo Workflow Import
jentic-arazzo-workflow-import
Import a Jentic-cataloged Arazzo workflow and synthesize a Naftiko capability YAML from it — every step in the Arazzo recipe becomes a Naftiko consume operation. The standards-aligned bridge between the two products.
Jentic MCP Server Bridge
jentic-mcp-server-bridge
Wrap Jentic's hosted Remote MCP server (api.jentic.com/mcp) as a Naftiko consume so any Naftiko capability can reach the entire Jentic catalog via MCP and re-expose it as a governed Naftiko-built MCP.
Jentic Arazzo Engine Bridge
jentic-arazzo-engine-bridge
Bridge to a self-hosted Jentic Arazzo Engine for air-gapped / regulated / private Arazzo workflow execution — the open-source Python workflow runner becomes a Naftiko-callable surface.
Jentic Credentials Vault
jentic-credentials-vault
Manage Jentic's server-side credential vault from Naftiko spec — Naftiko declares third-party SaaS dependencies, Jentic brokers the credentials, Naftiko engine never holds long-lived tokens.
Jentic Execution Logs Bridge
jentic-execution-logs-bridge
Pull Jentic execution history (per execution_id with agent_uuid / api_name / execution_type / status) into Naftiko's OpenTelemetry pipeline — single observability dashboard across both systems.
Jentic JAIRF Bridge
jentic-jairf-bridge
Pull Jentic's JAIRF AI-Readiness Framework scores into Naftiko Signals so company / API landing pages get an ‘AI-ready’ governance signal alongside service / standard / tool coverage.
Jentic FinOps Bridge
jentic-finops-bridge
Pull Jentic execution + integration + agent-run usage stats and correlate with Naftiko's per-call cost attribution to produce a unified FOCUS-aligned cost view across both systems.
