Running nfltr as a service, Multi Agent Orchestration

nfltr Agency Implementation, Distributed AI Delivery at Scale

Learn how to architect multi-machine agent workflows that let you deliver parallel coding and automation projects to clients without scaling your own infrastructure. This course covers hub session setup, node onboarding, capability controls, and billing models for agencies reselling distributed agent capacity.

Open the decision record for nfltr

What does running nfltr for clients commit you to?

Published figures for this service. Blank fields are not published.

Monthly tool cost
Custom pricing, contact vendor (nfltr publishes no plan prices)
Time to first value
days (vendor-published time_to_value)
Payback
Not modeled
Guided implementation
8 hours

Is nfltr worth running as a client service?

nfltr has strong published evidence for distributed Claude Code orchestration and exactly-once delivery, so it can support a high-complexity managed service for engineering-heavy clients. What remains unknown is vendor pricing, client price tolerance, labor cost, and delivery volume, so no ROI can be modeled from the supplied data.

An agency-fit judgement for reselling this service. It is separate from the tool description on the decision record.

Before you start

What has to be in place before the first client engagement.

Tools and subscriptions

  • Claude Code installation for hub sessions
  • nfltr CLI with 'nfltr node join' and 'nfltr orch' commands
  • Account key for relay TLS authentication
  • Joined machines (nodes) with available agent slots
  • Repository allowlist configured per node via --allow-repo

People and inputs

  • Documentation review of outbound-only relay routing and exactly-once delivery behavior
  • Per-machine capability opt-in policy for tools, repositories, and monitors
  • E2EE pairing key file distributed to machines that must communicate
  • Engineering staff with CLI and infrastructure experience, since nfltr excludes no-code teams

Estimated investment: Vendor pricing is not published. Use 'Custom pricing, contact vendor' for nfltr relay costs. setup_complexity is 'high' and time_to_value is 'days', so budget internal engineering onboarding time rather than a fixed dollar figure.

Included with the course

7 working documents for delivering this service.

  • nfltr Node Onboarding Checklist for Client Environmentschecklist
  • Hub Session Configuration Template with spawn_agent Patternstemplate
  • Per-Machine Capability Control SOP (Repository and Tool Allowlists)sop
  • Agent Task Brief Worksheet for Project Scopingworksheet
  • Distributed Delivery Pricing Model Guide (Concurrent Agents and Relay Usage)guide
  • Firewall-Free Network Integration Runbooksop
  • Client Data Residency and Compliance Documentation Templatetemplate

Listed by name. These documents are not yet published as individual downloads.