Fleet — FAQ¶
Questions and answers for the three components of the Naftiko Fleet: Crafter, Warden, and Skipper.
Crafter¶
Is Crafter a code editor?¶
No — it's a specification editor. Capability YAML is the artifact; there is no generated code to manage. Crafter helps you author and maintain the spec; Ikanos runs it.
Will it work without an internet connection?¶
Yes. Crafter caches resolved $ref targets locally for offline editing.
AI-assist features require connectivity if enabled.
Is the YAML the source of truth, or the canvas?¶
The YAML. Crafter never holds state the YAML can't represent. Round-trip edits preserve comments, ordering, and formatting.
Can multiple people edit the same capability?¶
Yes — Crafter is designed around the YAML file, so any merge-friendly VCS workflow works. Real-time collaboration is on the post-1.0 roadmap.
Does Crafter run Ikanos?¶
Crafter includes a Run button that spawns a local Ikanos process against the current capability for fast feedback loops. For production deployment, use Docker / Kubernetes / Skipper.
How is Crafter licensed?¶
Crafter ships in every edition of the Naftiko Fleet. The Community baseline (local-first builder via CLI + VS Code) is distributed under the Naftiko Fleet Freeware EULA — free for personal and internal business use. The Standard premium features (hosted web builder, catalog, OpenAPI import) are per-seat for teams and free for individual developers under the Naftiko Commercial License. Enterprise premium features (SSO/RBAC, approval workflows) are per-instance. See Fleet → License.
When did Crafter ship?¶
Crafter shipped in Fleet v1.0.0-alpha3 (Trimaran) on 2026-05-26 as the
VS Code extension naftiko.crafter, published to the
VS Code Marketplace.
See the Fleet release notes and the
Fleet → Roadmap for upcoming milestones.
Warden¶
Is Warden an OPA fork?¶
No — Warden uses OPA's Rego language for policy authoring (so existing Rego expertise transfers), but is implemented independently with Fleet-native integration: MCP trust propagation, audit chaining, and Skipper-distributed policy bundles.
Can I use Warden with non-Naftiko services?¶
Yes. Warden speaks a standard HTTP decision protocol; any service that can make a decision call can ask Warden. The deepest integration is with Ikanos, where authorization hooks are first-class.
Do I need Warden for basic auth?¶
No. Ikanos handles bearer / API-key / Basic / Digest / OAuth 2.1 natively. Warden is for fine-grained authorization — who can call what operation under which conditions — beyond what authentication alone can express.
What's the performance cost?¶
Sub-millisecond per decision when sidecar-deployed, with per-session caching. Centralized mode adds network latency (typically 1-5ms intra-VPC).
Is the audit log tamper-proof?¶
Hash-chained — each record contains the hash of the previous record, so tampering is detectable. For full tamper-proof guarantees, ship the log to a write-once SIEM or to a blockchain anchor (post-1.0).
How is policy distributed across a fleet?¶
In standalone mode: file-system bundles loaded on startup or via hot reload. In Skipper-coordinated mode: Skipper signs bundles and pushes them to every Warden instance, with version-pinning per capability.
How is Warden licensed?¶
Warden ships in every edition of the Naftiko Fleet. The Community baseline (local policy evaluation, Rego authoring, decision API) is distributed under the Naftiko Fleet Freeware EULA — free for personal and internal business use. Standard premium features (team-shared bundles, dry-run analytics) are per-seat. Enterprise premium features (fleet-wide distribution, audit trail, regulated-environment integrations) are per-instance with SLA terms under the Naftiko Commercial License. See Fleet → License.
When did Warden ship?¶
Warden shipped in Fleet v1.0.0-alpha3 (Trimaran) on 2026-05-26. See the Fleet → Roadmap for upcoming Standard and Enterprise milestones (fleet-wide policy distribution, immutable audit trail, signed policy bundles).
Skipper¶
Is Skipper a service mesh?¶
No. Skipper integrates with service meshes (Linkerd, Istio, Consul) or falls back to a built-in router when no mesh is present. It is the fleet operator that knows about capabilities and Naftiko semantics; the mesh remains the transport plane.
Is it Kubernetes-only?¶
The Kubernetes operator is the primary deployment. A non-K8s mode for Docker Swarm / Nomad / plain Docker Compose is planned post-1.0.
How does it differ from Argo Rollouts / Flagger?¶
Skipper uses progressive-delivery primitives (and integrates with Argo Rollouts) for the rollout layer, but adds Naftiko-aware features: capability-level health, MCP tool inventory, cross-capability tracing, Warden bundle distribution. It's the fleet brain, not the rollout engine.
Do I need Skipper if I only run one capability?¶
No. A single capability is fine on plain Docker / K8s / a single Ikanos process. Skipper earns its place once you have a fleet — multiple capabilities, environments, and lifecycles to coordinate.
How does GitOps work?¶
The fleet manifest (naftiko.fleet.yaml) is the source of truth. Argo CD
or Flux reconciles it into the Skipper operator. The operator then drives
Kubernetes resources, Warden bundles, and routing config.
How is observability distributed?¶
Each capability runs a Control adapter exposing health, metrics, and traces. Skipper aggregates these into a fleet dashboard. Traces are correlated across capability boundaries via standard W3C TraceContext propagation.
How is Skipper licensed?¶
Skipper ships in every edition of the Naftiko Fleet. The Community baseline (single-host orchestration via local fleet manifest) is distributed under the Naftiko Fleet Freeware EULA — free for personal and internal business use. Standard premium features (multi-host orchestration, team dashboards) are per-seat. Enterprise premium features (multi-region routing, fleet placement, blue/green & canary, SLA-grade observability) are per-instance with SLA terms under the Naftiko Commercial License. See Fleet → License.
When will Skipper ship?¶
See Fleet → Roadmap. v0.1 preview is post-Ikanos GA, alongside Warden.