Welcome to the Naftiko Fleet, the Enterprise platform for Spec-Driven Integration — reinventing API integration for the AI era with governed, versatile capabilities that streamline the API sprawl created by massive SaaS and microservices growth.
A fleet is what you call a group of ships sailing together — here, a group of capabilities running and governed as one.
The Naftiko Fleet delivers Spec-Driven Integration end to end, from authoring a capability to operating and governing it at scale. It is composed of three product components that each own one step of the workflow.
- Crafter is an extension for VS Code compatible IDEs to edit Ikanos specs and lint them with Polychro,
- Warden is a Backstage integration to help with cataloguing, scaffolding and delivery of Ikanos capabilities,
- Skipper is a Kubernetes integration to deploy and operate a fleet of capabilities.
- Not a single monolithic product. The Fleet is three independently usable components, not one binary. You can adopt Crafter, Warden, or Skipper only when you need them.
- Not a paywall on the essentials. The fleet always relies on Ikanos and Polychro which are fully open-source (Apache 2.0).
- Not an all-or-nothing platform. Components compose, but none requires the others.
The complete, always-up-to-date Fleet documentation lives on the Naftiko Shipyard. Start here and keep exploring:
- 🧭 Concepts — Spec-Driven Integration
- 🚢 Fleet Overview
- 🛠️ Crafter — the capability builder
- 🛡️ Warden — governance & policy
- ⛵ Skipper — fleet-wide orchestration
- 🌊 FAQ
- 📣 Releases
- 🔭 Roadmap
Want to see the Fleet in action without installing anything? The Playground. Jump straight into a guided tutorial:
- Track 1 — Context Engineering (mock → live → auth → shaping → legacy → writes → lookups)
- Track 2 — API Reusability (skill groups → aggregates → REST)
- Track 3 — API Orchestration (the Fleet Manifest capstone)
Please join the community of users and contributors in this GitHub Discussion forum!
