Rightsize a Set of Microservices
Create a simpler capability layer over many microservices to reduce client complexity and improve consistency.
Take Me to the Repo
Aggregate multiple microservice endpoints under one exposed namespace and a small set of business-oriented resources and tools. Standardize authentication, header behavior, and parameter handling at capability level instead of duplicating logic in every client.
Use orchestration and output shaping to hide service fragmentation and return consistent contracts. Support sequence of steps with calls, YAML and Protobuf payload conversion.
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
Simplify what clients see. Keep what works underneath.
Chart your next course
Rightsize a Monolith
