Skip to content
NFLTR logo

NFLTR

Distributes Claude code agents across your machines to run tasks in parallel where data lives.

Developer toolsCLIAgentsFor developers
nfltr.xyz ↗Launched on Product Hunt · 2026-09-30
At a glanceswept 2026-10-07

31 linking domains

Emerging

For
Developers running Claude code agents across multiple machines for distributed tasks.
Price
Price not readpricing page, read 2026-09-30 ↗
Activity
Actively maintainedsite updated 8 days ago
Company
Domain since 2026domain registered
Runs as
CLI
AlternativesSet it up for my teamIs NFLTR yours? Claim the card →
What people do with itread off nfltr.xyz on 2026-09-30
  • Run Claude agents in parallel across laptops, VMs, and servers
  • Investigate and fix production incidents on remote machines
  • Triage test failures overnight across multiple QA environments
The companyeach fact with its source · read 2026-09-30
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-11

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Developer tools tools →

Questions this page answers
  • What is NFLTR?

    Distributes Claude code agents across your machines to run tasks in parallel where data lives. It is listed in the Atlas under Developer tools.

  • Who is NFLTR for?

    Developers running Claude code agents across multiple machines for distributed tasks.

  • Do people use NFLTR?

    Emerging.

  • Is NFLTR still maintained?

    Actively maintained: site updated 8 days ago.

  • What are alternatives to NFLTR?

    In Developer tools, by use: Cloudflare, JetBrains, Ollama, Augment Code, CircleCI, The Content Repurpose Revolution.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.