Fleet Management Enterprise

Manage thousands of agents with fleet tokens and Kubernetes-style label selectors. Group agents by client, region, tier, or any custom dimension. Issue bounded tokens, fan-out commands, and monitor your entire fleet from a single dashboard.


Architecture Overview

Fleet management is built on two primitives: fleet tokens (authentication + authorization) and labels (routing + grouping). Together they let you control who can connect and how requests are distributed.

FLEET TOKENS Token: acme-prod labels: client=acme, env=prod Token: us-east-fleet labels: region=us-east Token: iot-sensors labels: type=sensor, tier=free Admin Dashboard Create / Revoke / List NFLTR SERVER Token Validation Label Matching Fan-out Dispatch Metrics + Audit AGENT FLEET acme-web-1 client=acme env=prod acme-web-2 client=acme env=prod sensor-001 type=sensor region=us sensor-002 type=sensor region=eu edge-node-us region=us-east tier=paid edge-node-eu region=eu-west tier=paid + 9,994 more agents connected

Fleet Tokens

Fleet tokens are scoped authentication credentials that restrict which agents can connect and what labels they can carry. Create them via the dashboard or API:

# Create a fleet token for a specific client
curl -X POST https://nfltr.xyz/api/v1/dashboard/fleet-tokens \
  -H "Authorization: Bearer $ADMIN_KEY" \
  -d '{
    "name": "acme-production",
    "labels": {"client": "acme", "env": "prod"},
    "max_agents": 100
  }'

The returned token is given to the client. Agents authenticating with this token can only use matching labels and are bounded by the max_agents limit.

Labels & Selectors

Agents carry key-value labels that describe their role, location, and ownership:

# Agent connects with labels
nfltr http 8080 --name web-server \
  --labels client=acme,env=prod,region=us-east

Labels enable Kubernetes-style selectors for routing and querying:

SelectorMatches
client=acmeAll agents with client label "acme"
env=prod,region=us-eastProduction agents in US East (AND logic)
type=sensorAll sensor-type agents across regions
tier!=freeAll agents NOT on the free tier

Fan-Out Commands

Send messages to groups of agents using agent-to-agent messaging:

# Send reload command to a specific agent
nfltr a2a send acme-web-1 '{"action":"reload-config"}'

# Broadcast to multiple agents by name
nfltr a2a send sensor-001 '{"action":"update","version":"2.1.0"}'
nfltr a2a send sensor-002 '{"action":"update","version":"2.1.0"}'

Dashboard Management

📊 Fleet Overview

See all connected agents, their labels, connection duration, and current status in a single view.

🔑 Token Management

Create, list, and revoke fleet tokens. Set agent limits, label restrictions, and expiry dates.

📋 Audit Trail

Every connection, authentication, and command is logged. Filter by agent, token, label, or time range.

Scaling

NFLTR's fleet management scales horizontally. In multi-pod SaaS deployments:

💡 Works with the Go SDK

The embeddable Go SDK supports WithLabels() — embed the agent in your product and let fleet tokens manage authentication automatically.

Manage your fleet

Fleet tokens, label selectors, and audit logging — all included free.

Download Agent On-Premise Access →