Side by Side
At a Glance
14 dimensions of comparison between Naftiko and Composio — 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
Composio
Category
Naftiko
Spec-driven integration platform
Composio
Agent execution platform — 1000+ pre-built tool integrations + managed OAuth + MCP gateway
Origin
Naftiko
Kin Lane (API Evangelist) + Jerome Louvel (Restlet → Talend → Qlik), 2025
Composio
Composio.dev (YC W24)
Primary primitive
Naftiko
Capability — declared in YAML; consumes + exposes
Composio
Toolkit + Tool + ConnectedAccount + Session
Layer in the stack
Naftiko
Build-time + ship-time + runtime engine that authors integrations
Composio
Runtime execution surface with a hosted catalog of pre-built integrations
Core artifact
Naftiko
YAML capability spec (declarative)
Composio
Hosted catalog entry (read-only consumer); per-account session at runtime
Open source posture
Naftiko
Apache 2.0 Framework, free Fleet community, paid Standard / Enterprise
Composio
SaaS-only — Hobby (20K calls free), Starter $29/mo, Pro $229/mo, Enterprise custom (VPC available)
Multi-protocol exposure
Naftiko
REST + MCP + Skills + A2A (roadmap) — same capability, all protocols
Composio
Tool API + MCP gateway + outbound Webhooks (Triggers + execution events)
Governance scope
Naftiko
Design-time (Spectral lint), admission (Kyverno / OPA), runtime engine
Composio
Per-account auth scope + per-session tool isolation + per-plan rate-limit + tool-call quota
Discovery surface
Naftiko
Backstage capability catalog + scorecards
Composio
Hosted Toolkit / Tool catalog (1000+ entries, search + filter)
Audit / observability
Naftiko
OpenTelemetry + Prometheus + structured logs
Composio
Outbound webhook events + per-trigger / per-execution log surface (incident-driven, less mature)
Identity / OAuth
Naftiko
Runtime secret injection (env, ExternalSecrets); Keycloak / OpenFGA roadmap
Composio
AuthConfig (developer OAuth profiles) + ConnectedAccount (per-user delegated tokens) — agents never see raw credentials
Cost / FinOps
Naftiko
Cost-center labels propagated to K8s; Kubecost integration
Composio
Per-tool-call metering with monthly quota + overage; FOCUS-aligned billing model
Catalog breadth
Naftiko
Bring-your-own — author any integration as a capability YAML
Composio
1000+ pre-integrated toolkits ship out of the box
Founder framing
Naftiko
“Capability fleet” — many ships, one navy
Composio
“Give your agent 1000+ tools in one SDK call”
Common Ground
Where They Overlap
Both Naftiko and Composio 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 ship a managed MCP surface
Composio's MCP gateway exposes 1000+ toolkits to MCP-compatible clients (Claude Desktop, Cursor) with delegated auth. Naftiko exposes any consumed API as an MCP server through the
exposes: mcp adapter. Both treat MCP as protocol-level (SSE, JSON-RPC, credential delegation), not just ‘another API.’2
Both treat OAuth / credentials as the load-bearing concern
Composio's AuthConfig + ConnectedAccount split is exactly the pattern Naftiko's roadmap targets — developer-owned OAuth profiles separated from per-user tokens. Both products refuse to let agents hold long-lived credentials directly.
3
Both ship event-driven Triggers / Webhooks
Composio's Triggers API subscribes to webhook events from connected apps (Slack messages, GitHub issues, HubSpot deals). Naftiko's roadmap includes a Webhook server adapter and event-driven capabilities. Both target the same async-integration pain.
4
Both ship a discovery surface as a first-class concern
Composio ships a hosted Toolkit + Tool catalog with search and filter. Naftiko Fleet ships a Backstage capability catalog with scorecards. Both refuse the 'manual catalog registration goes stale' anti-pattern.
5
Both meter usage and surface FinOps signal
Composio publishes a FOCUS-aligned billing model with per-tool-call dimensions (toolkit, account, environment). Naftiko propagates cost-center labels into Kubecost for per-call attribution. Both refuse the ‘no per-call cost visibility’ anti-pattern.
6
Both have a session-shaped runtime concept
Composio's Tool Router Session is an ephemeral container that scopes tool discovery + execution to a single connected account. Naftiko's runtime engine instantiates capability containers with their own consume + expose topology. Both isolate at the session / capability level, not the tenant level.
7
Both publish operational maturity signals
Composio's recent incident report (April 28 trigger outage) demonstrates a queue-isolation discipline and post-mortem culture. Naftiko's roadmap shows the same posture — circuit breakers, bulkheads, and resilience patterns built in. Both are running for production, not demos.
8
Both are pulling agent-first UX upmarket
Composio shipped ‘agents can sign up for Composio’ (autonomous account creation at agents.composio.dev). Naftiko's
exposes: skill adapter is built so agents can discover and consume capabilities directly. Both treat agents as first-class consumers, not afterthought channels.Where We Diverge
How Naftiko Is Different
The clearest single-sentence difference: Composio ships a hosted catalog of 1000+ pre-built integrations behind one SDK; Naftiko ships an open-source engine for authoring your own integrations as governed YAML capabilities. Different bets — Composio for breadth and managed convenience; Naftiko for depth, openness, and customization.
1
Pre-built catalog vs spec-driven authoring
Naftiko
Author any integration as a YAML capability — declare consume + expose + governance + observability. Bring your own integration depth.
Composio
Consume any of 1000+ pre-integrated toolkits with no authoring required. Maximum out-of-the-box breadth.
Different bets on where the value lives — convenience (Composio) vs control (Naftiko).
2
SaaS-only vs open-source-self-hosted
Naftiko
Apache 2.0 Framework runs in your container, your Kubernetes, your VPC. Open-source is the engine.
Composio
Hosted SaaS by default; per-tool-call pricing from $29/mo. Enterprise tier offers VPC / on-prem; standard tiers do not.
3
Capabilities as the primitive vs Toolkits + Tools as the primitives
Naftiko
Primary identity is ‘the thing that does X’ — a functional unit composed from declared consumes and exposes.
Composio
Primary identities are toolkits (apps), tools (actions), and connected accounts (per-user auth scopes). Catalog-shaped, not capability-shaped.
4
Three governance altitudes vs single-altitude scoping
Naftiko
Spectral rulesets at design time, Kyverno / OPA at admission time, and runtime checks in the engine. Lifecycle-shaped governance.
Composio
Per-account auth scope + per-session tool isolation + per-plan rate-limit + per-call quota. Runtime-shaped governance.
5
Observability is OTel-native vs incident-driven
Naftiko
OpenTelemetry events emitted from every capability container; native pipe into Datadog / New Relic / Prometheus.
Composio
Outbound webhook events for trigger fires + execution results; observability surface is event-driven and less standardized.
6
Open expose surface vs catalog-bounded surface
Naftiko
Any capability can expose REST + MCP + Skills + A2A. The exposed surface is whatever the capability author declares.
Composio
Exposed surface is bounded by the 1000+ toolkit catalog Composio maintains. Custom integrations require custom toolkits or a different platform.
7
Consumes-side governance vs auth-only consumes-side
Naftiko
Governs the consume side at three levels — HTTPS enforcement, PII detection, retry safety per upstream, schema validation. Owns the supply chain.
Composio
Consumes side is the catalog itself; auth is the governance surface. No HTTPS / PII / retry-safety policies on the upstream.
8
Bring-your-own infrastructure vs managed infrastructure
Naftiko
Customer runs the engine on their infra; controls the data plane, the network egress, the secrets, the storage.
Composio
Composio runs the infra; customer hands them an OAuth scope and a webhook URL. Standard tiers offer no on-prem deployment.
Partnership Thesis
Service Partnership
Naftiko is the spec-driven authoring engine. Composio is the hosted 1000+ integration catalog. The capability map below treats the entire Composio catalog as a Naftiko-consumable surface — every Composio toolkit becomes accessible from a Naftiko-built capability, with the Naftiko engine layering Spectral / OPA / OpenTelemetry on top of Composio's managed integration.
“Naftiko brings the spec-layer governance, the multi-protocol exposure, and the open-source engine. Composio brings 1000+ pre-built integrations. Together: customers get governed access to every integration Composio ships without losing the open-source spec-driven control plane.”
Two First-Meeting Questions
Q1. Composio toolkits as Naftiko capabilities
Would Composio support a documented ‘wrap me as a Naftiko capability’ pattern — where every Composio toolkit can be auto-synthesized as a Naftiko capability YAML and consumed through the Naftiko engine? The capability map below treats every Composio API surface as a Naftiko-consumable one for exactly this reason.
Q2. Naftiko-built capabilities back into the Composio catalog
Would Composio open a path for customer-built Naftiko capabilities to land in the Composio catalog as managed toolkits — bringing the breadth of Composio's catalog and the customization of Naftiko's spec layer together in one discovery surface? Today the Composio catalog is Composio-curated; opening it to Naftiko-authored entries would compound the breadth advantage.
Integration Kit
Partnership Capability Map
10 Naftiko capabilities authored to integrate with Composio as a service partner. Each one consumes a specific Composio 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.
Composio Toolkits Discovery
composio-toolkits-discovery
Pull Composio's 1000+ pre-integrated toolkit catalog into Naftiko Fleet discovery so Backstage shows the Composio catalog alongside Naftiko-built capabilities.
Composio Tool Execute
composio-tool-execute
Execute any of Composio's 1000+ pre-integrated tools as a governed Naftiko operation — same Spectral / OPA / OTel guards apply on top.
Composio Tool Router Session
composio-tool-router-session
Wrap Composio's session-based Tool Router so Naftiko hands an AI agent a runtime container scoped to a single connected account — ephemeral, audit-trailed, no raw credentials exposed.
Composio OAuth Broker
composio-oauth-broker
Route Naftiko consume-side OAuth flows through Composio's managed Connected Accounts so the Naftiko engine never holds long-lived third-party tokens.
Composio Auth Configs
composio-auth-configs
Manage Composio AuthConfigs (reusable developer OAuth client profiles per toolkit) declaratively from Naftiko capability spec — white-label OAuth at the spec layer.
Composio Triggers Subscribe
composio-triggers-subscribe
Subscribe to Composio's webhook-driven Triggers (Slack message posted, GitHub issue opened, HubSpot deal moved, etc.) and bridge those events into Naftiko's event-driven workflows.
Composio MCP Gateway Bridge
composio-mcp-gateway-bridge
Wrap Composio's MCP gateway so Naftiko capabilities can consume Composio tools via MCP and re-expose them as Naftiko-governed MCP — entire Composio catalog as one Naftiko consumable.
Composio Webhooks Bridge
composio-webhooks-bridge
Manage Composio's outbound webhook subscriptions so trigger fires, account state changes, and execution events land in Naftiko's webhook-driven workflows.
Composio Toolkit as Naftiko Capability
composio-toolkit-as-naftiko-capability
Synthesize a Naftiko capability YAML from any Composio toolkit's metadata — every tool in the toolkit becomes a Naftiko expose. Where the two products bridge at the spec layer.
Composio FinOps Bridge
composio-finops-bridge
Pull Composio's tool-call usage stats and correlate with Naftiko's per-call cost attribution to produce a unified FOCUS-aligned cost view across both systems.
