API-First Design
Start from existing APIs and define reusable capabilities on top, so API investments can power new AI and app experiences.
Take Me to the Repo
Begin with consumed API declarations -- base URI, authentication, resources, operations -- then incrementally add exposed API and MCP adapters. Reuse existing security and configuration using external references with file and runtime resolution and injected variables.
Add format-aware parsing and mapping (JSON, YAML, XML, CSV, Avro, Protobuf support) to normalize diverse backends. Your API investments become the foundation for new AI and application experiences.
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
Start with what you have. Build what you need.
Chart your next course
Context Engineering
