Cluster license is License — lattice.entitlement.json, managed IPs. Fleet is a different spec. Upload fleet.entitlement.json on the Fleet License page, or place it at /etc/lattice/fleet.entitlement.json.

Same signature scheme as cluster files. No phone-home. Missing or invalid Fleet file → Community, 2 clusters.

Caps and list prices

Same names as cluster Lattice. Same annual USD. Pricing.

Face	Clusters	Annual
Community (missing file)	2	$0
Starter	10	$4,800
Professional	25	$7,200
Team	50	$12,000
Org	200	$24,000
Scale	500	$48,000
Quoted (custom)	unlimited, or the number on the file	hello@

Over max_clusters: refuse new enrollments; existing clusters stay managed. Expired Fleet file: Fleet console read-only; no new proxy sessions; agents may stay connected.

Each cluster still needs its own Lattice file. Fleet does not pool IPs. Mix Community and paid clusters in one Fleet.

File shape

{
  "kid": "v1",
  "payload": {
    "spec": "lattice.fleet.entitlement/v1",
    "tier": "team",
    "max_clusters": 50
  },
  "sig": "<base64 Ed25519>"
}

Missing file is Community, two clusters. Paid raises the cluster cap and adds SSH-tunnel connectivity. The portal does not auto-issue a Fleet file at signup. Download fleet.entitlement.json from the customer portal when you have a paid Fleet seat.

Support

Fleet support is the control plane. Each cluster keeps its own support: Community is no SLA; paid is business hours America/Chicago. Mixing Community sites into a paid Fleet does not change those cluster files.

Broken	Obligation
Agent, enroll, proxy, Fleet console, search, inbox, SSO, break-glass	Paid Fleet — business hours
Same, on Community Fleet (no file)	No SLA
DHCP / IPAM / DNS / HA on a paid cluster	That cluster’s paid file
Same DDI symptoms on a Community cluster	No SLA

Tickets: [email protected]. No phone. No 24×7. Lattice’s customer is the org that holds the files, not an ISP’s subscriber. Say whether the ticket is Fleet or cluster, and the cluster license_id or “community.”