Compose AI Context
Combine data from multiple APIs into one capability to deliver richer, task-ready context to AI clients.
Take Me to the Repo
Register multiple consumed APIs with unique namespaces, then orchestrate cross-source calls using ordered steps. Bridge calls through step mappings and per-step input injection, so outputs from one source feed inputs of the next.
Return a single composed output model via mapped output parameters, giving AI clients one coherent result instead of multiple fragmented API responses.
The Naftiko Fleet — six components, all at v1.0.0-alpha3
Spec-Driven Integration (SDI) ties every component to a single declarative YAML spec — authored once, linted by Polychro, executed by Ikanos, authored in Crafter, governed by Warden, orchestrated by Skipper, and documented in Shipyard.
Shipyard
The documentation hub and public front door for the Fleet. Tutorials, concepts, editions. Soon: a hosted Playground and AI-assisted Ask Navi search across the corpus.
Ikanos
The OSS capability engine. Runs a Naftiko spec as a multi-protocol server — REST, MCP, and Skill from the same definition. Apache 2.0.
Polychro
The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs. The new Spectral for SDI. Apache 2.0.
Crafter
The capability builder for VS Code and most AI IDEs. Visual + spec-driven authoring with inline governance and live topology.
Warden
Capability governance and policy enforcement for Backstage. Scorecards, scaffolding, fleet explorer, impact tracing.
Skipper
Fleet-wide orchestration for Kubernetes — across teams, regions, and compliance domains. Continuous compliance and FinOps tagging.
Start small, scale smart
One call. Multiple sources. Coherent context.
Chart your next course
Rightsize Microservices
