Installation¶
The Naftiko Fleet is a family of small, focused components that you install independently. With the v1.0 Alpha 3 release the full Fleet is now available end-to-end: authoring (Crafter), linting (Polychro), running (Ikanos), governance (Warden), and orchestration (Skipper). Pick the components you need today, add the others when you're ready.
| Component | What it does | How you install it |
|---|---|---|
| Ikanos | Runs your YAML capabilities as MCP / REST / Skill servers (multiple capabilities, side by side) | Docker image or native CLI (Linux / macOS / Windows) |
| Polychro | Lints your specs against schema + bundled rulesets | Native CLI or Java library |
| Crafter | Authors capabilities (formerly the Naftiko VS Code extension) | VS Code Marketplace |
| Warden | Governs capabilities from your developer portal (formerly the Naftiko Backstage plugin) | Backstage plugin package |
| Skipper | Orchestrates capabilities on Kubernetes (Operator + Helm chart) | Helm chart |
Open source under it all
Ikanos and Polychro are Apache 2.0 standalone projects. Crafter, Warden, and Skipper are part of the Naftiko Fleet under the Freeware EULA (Community) and the Naftiko Commercial License (Standard / Enterprise). Every capability YAML file you author works identically across all components.
Ikanos Engine¶
Option A — Docker (recommended)¶
Prerequisites:
- Docker, Docker Desktop, or any OCI-compatible runtime
- One or more capability YAML files you want to run
# Pull the latest stable release
docker pull ghcr.io/naftiko/ikanos:v1.0.0-alpha3
# Or pull the rolling snapshot
docker pull ghcr.io/naftiko/ikanos:latest
Run it against a local capability file:
Localhost inside containers
When your capability references a service running on your host machine,
use host.docker.internal instead of localhost. To expose a server
from inside the container, bind on 0.0.0.0 rather than 127.0.0.1.
Option B — Native CLI¶
Download the binary for your platform from the Ikanos releases page.
New-Item -ItemType Directory -Force -Path "C:\Program Files\Ikanos"
Invoke-WebRequest `
-Uri "https://github.com/naftiko/ikanos/releases/latest/download/ikanos-cli-windows-amd64.exe" `
-OutFile "C:\Program Files\Ikanos\ikanos.exe"
$oldPath = [Environment]::GetEnvironmentVariable('Path','Machine')
[Environment]::SetEnvironmentVariable('Path', "$oldPath;C:\Program Files\Ikanos", 'Machine')
Verify the install:
Ikanos can run multiple capabilities in parallel out of the box — either as separate processes (one capability per container or binary invocation) or, declaratively, under Skipper on Kubernetes. See First fleet for both patterns.
Polychro Linter¶
Option A — Native CLI¶
# macOS / Linux
curl -L https://github.com/naftiko/polychro/releases/latest/download/polychro-$(uname -s | tr A-Z a-z)-amd64 -o polychro
chmod +x polychro && sudo mv polychro /usr/local/bin/
# Lint a spec
polychro lint my-capability.yml
Option B — As a Java library¶
<dependency>
<groupId>io.polychro</groupId>
<artifactId>polychro-core</artifactId>
<version>0.1.0</version>
</dependency>
See the Polychro getting-started guide for the full Java API.
Crafter — the capability builder¶
Crafter is the v1.0 Alpha 3 rename of the Naftiko VS Code extension. Same engine you may already know — now part of the Fleet under its new name, with a clear path to a hosted web builder in Standard.
Install from the VS Code Marketplace:
Files saved as *.naftiko.yaml or *.naftiko.yml activate JSON Schema
validation, Spectral-style rules, and inline diagnostics directly in the
editor — no CLI required. See Components → Crafter for the
full feature list.
Migrating from the Naftiko VS Code extension
If you had the previous extension installed, VS Code will offer to migrate it automatically the first time you open a capability file after upgrading. Settings keys keep their old names where possible; a few are aliased — see the Crafter FAQ.
Warden — capability governance in Backstage¶
Warden is the v1.0 Alpha 3 rename of the Naftiko Backstage plugin. It surfaces every capability in your developer portal, attaches policy to it (built on Polychro rulesets), and produces an audit trail of decisions.
Install the plugin in your Backstage app:
# In the Backstage frontend
yarn --cwd packages/app add @naftiko/plugin-warden
# In the Backstage backend
yarn --cwd packages/backend add @naftiko/plugin-warden-backend
Then register the plugin routes — see Components → Warden for the full integration guide and policy authoring reference.
Skipper — Kubernetes operator + Helm chart¶
Skipper is the new Kubernetes operator that turns Capability custom
resources into running Ikanos workloads. It ships in v1.0 Alpha 3 as a
Helm chart that installs the operator, CRDs, and default
CapabilityClass.
helm repo add naftiko https://charts.naftiko.io
helm repo update
helm install skipper naftiko/skipper \
--namespace naftiko-system --create-namespace \
--version 1.0.0-alpha3
Verify the install:
Once the operator is running, declare capabilities the Kubernetes way:
apiVersion: naftiko.io/v1alpha1
kind: Capability
metadata:
name: registry
spec:
source:
configMapRef:
name: registry-spec
key: registry.naftiko.yml
class: standard
See Components → Skipper for the CRD reference, GitOps patterns, and multi-region orchestration.
Next steps¶
- Quickstart — your first Ikanos capability in 5 minutes
- First fleet — multiple capabilities running side by side, linted by Polychro, orchestrated by Skipper
- Tutorials — hands-on, ten-step learning paths
- Fleet → Overview — how the components fit together
- Fleet → Releases — what's in v1.0 Alpha 3