Fleet — Editions¶

The Naftiko Fleet ships in four editions — Community, Developer, Team, and Enterprise. Every edition ships the same Apache 2.0 core (Ikanos + Polychro) and the same author → lint → run inner loop. What changes as you move up is where and how your capabilities are hosted, and the governance, scale, and support layered on top.

At a glance¶

Feature comparison¶

Core (always Apache 2.0)¶

Hosting¶

Tooling¶

Governance + compliance¶

Support + SLA¶

The feature mapping for unreleased hosted editions is illustrative and will firm up as their roadmaps mature. Ikanos and Polychro are committed to staying 100% Apache 2.0 OSS in every edition.

Picking an edition¶

Community edition¶

The Community edition is the free, self-hosted baseline of the Naftiko Fleet. It is free forever for personal and internal business use and ships the full author → lint → run inner loop: Ikanos + Polychro under Apache 2.0, plus free Crafter.

What's included¶

What you can do today¶

• Author capabilities in YAML and run them on Ikanos
• Validate every change with Polychro (locally and in CI)
• Scaffold and catalog capabilities in CNCF Backstage
• Edit .ikanos.yaml files with inline validation in VS Code
• Expose capabilities as MCP, Skill, REST, and Control adapters
• Use the full Spec-Driven Integration workflow on your own infrastructure

Where to get it¶

• Docker images — ghcr.io/naftiko/ikanos, ghcr.io/naftiko/polychro
• Native binaries — Ikanos releases, Polychro releases
• VS Code Marketplace — search "Naftiko"
• GitHub Discussions — community.naftiko.io

Freeware EULA — what it does and doesn't allow¶

The Naftiko Fleet — Community edition EULA grants you a non-exclusive, non-transferable, royalty-free license to use the Software for personal or internal business purposes, on any number of devices under your direct control. You may redistribute the installer unchanged and free of charge. You may not reverse-engineer, modify, sublicense, or remove Naftiko branding. See the full text at naftiko/fleet/LICENSE.md.

The Apache 2.0 components (Ikanos and Polychro) are not restricted by that EULA — they are independently licensed Apache 2.0 OSS and you can fork, modify, and redistribute them freely under standard Apache terms.

When to move up¶

The Community edition has no usage limits and no telemetry phone-home. You will want Developer when you want Naftiko-hosted serving for a quick prototype or demo, Team when you run real workloads and need always-warm production hosting with an SLA, and Enterprise when you need governance and scale — premium Warden and Skipper, dedicated tenancy, continuous compliance, domain-level dashboards, and RBAC.

Developer edition¶

The Developer edition is the first paid dollar — managed dev hosting. Push a capability to Naftiko-hosted serving for prototyping and demos, without standing up any infrastructure of your own. Cold-start (scale-to-zero) economics keep it cheap — you pay for what you actually run.

What Developer adds on top of Community¶

When to move up¶

Choose Team when your prototype becomes a real workload and you need always-warm production hosting with higher throughput, reliability, and an SLA.

Team edition¶

The Team edition is managed production hosting — the land step from prototype to production. It is always-warm, with no cold start, delivering higher throughput and reliability for real workloads, FCU-metered so you pay in proportion to the flow-compute you consume.

What Team adds on top of Developer¶

When to move up¶

Choose Enterprise when you need dedicated tenancy or customer-infra deployment, continuous compliance (NIST, SOC 2, PCI, GDPR), domain-level dashboards, and RBAC.

Enterprise edition¶

The Enterprise edition is governance and scale for regulated organizations running many capabilities across environments and compliance domains. It adds premium Warden (Backstage catalog + scaffold, with federation) and premium Skipper (Kubernetes operator, multi-cluster, RBAC), plus dedicated tenancy, continuous compliance, and domain-level dashboards.

What Enterprise adds on top of Team¶

The layers in production¶

                 ┌──────────────────────────────┐
                 │           Skipper            │   ← global placement & routing
                 │   (fleet orchestrator)       │
                 └──────────────┬───────────────┘
                                │
              ┌─────────────────┼─────────────────┐
              ▼                 ▼                 ▼
       ┌──────────┐      ┌──────────┐      ┌──────────┐
       │   Ship   │      │   Ship   │      │   Ship   │     ← runtime cells
       │  (cell)  │      │  (cell)  │      │  (cell)  │
       └────┬─────┘      └────┬─────┘      └────┬─────┘
            ▼                 ▼                 ▼
       Ikanos engines   Ikanos engines   Ikanos engines    ← capability runtime
       (one per cap.)   (one per cap.)   (one per cap.)
            ▲                 ▲                 ▲
            └─────────────────┼─────────────────┘
                              │
                       ┌──────┴───────┐
                       │    Warden    │   ← policy gate on every deploy
                       └──────────────┘

Compliance¶

Enterprise targets the controls expected in regulated environments:

• Continuous compliance against NIST, SOC 2, PCI, and GDPR control sets
• Data residency via region-scoped ships
• Customer-managed keys for at-rest encryption
• Domain-level dashboards and RBAC for auditable, isolated operations

Ikanos and Polychro stay Apache 2.0 throughout — the premium features apply to Warden, Skipper, and the surrounding hosted services.

Licensing summary¶

Every edition ships the same Apache 2.0 core — Ikanos and Polychro — with no commercial add-ons. The Community Fleet bundle (Shipyard, Crafter, basic Warden, basic Skipper) is distributed under the Naftiko Fleet Freeware EULA, free for personal and internal business use. Developer, Team, and Enterprise hosted services and premium features are licensed under the Naftiko Commercial License.

See Fleet → License for the full three-license picture, and talk to us about the Design Partner program to start a trial.