Rightsize a Monolith API
Extract focused capabilities from a broad monolith API so consumers get only what they need for each use case.
Take Me to the Repo
Select only required monolith operations in your capability spec and remap them to narrower exposed resources and tools. Use output filtering and mapping to publish smaller, purpose-built payloads for each consumer scenario.
Optionally forward selected routes with target namespace to keep passthrough paths where full transformation is not needed. Each extracted capability becomes a focused, discoverable unit.
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
Extract what matters. Leave the rest in place.
Chart your next course
MCP-First Design
