AI FinOps
Costs are unpredictable -- tokens, models, and upstream API usage. You can't govern, secure, or optimize what you can't see.
Take Me to the Repo
AI costs are multi-dimensional -- usage-based, model-based, API call-based, input and output tokens, caching -- and no single vendor provides cross-platform cost visibility. Teams lack the ability to set budgets, thresholds, and alerts to prevent runaway costs. Many teams consume external APIs with no central visibility into aggregate spend. Leadership is demanding AI FinOps as a 2026 priority, but cost attribution to teams, projects, and specific capabilities does not exist.
Naftiko brings cost controls to the execution surface -- policy-driven budgets and attribution mapped to capabilities, not scattered across vendor dashboards. Cost-center labels propagate from the capability spec through Kubernetes resources to Kubecost and FinOps tooling. Billing granularity tags on consumed API operations and per-operation Prometheus metrics make spend observable at the granularity that matters -- by team, domain, capability, and consumer.
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
You can't optimize what you can't see.
Chart your next course
Context Engineering