Skip to content
Tabfleet logo

Tabfleet

Runs isolated cloud browsers that agents drive over MCP, REST or CDP, with signed live-view links for watching sessions.

At a glanceswept 2026-10-13

74 installs/mo

Established

Price
Price not read
Activity
Actively maintainedrelease 11 days ago · site updated 3 weeks ago
Company
Dalton Solutions, LLCprivacy policy
Runs as
APISDK
Your datawhat they publish, each line with its page · read 2026-10-14

These are Tabfleet's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

How a program reaches itfound, not claimed · read 2026-10-14

MCP server details →

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 Tabfleet?

    Runs isolated cloud browsers that agents drive over MCP, REST or CDP, with signed live-view links for watching sessions. It is listed in the Atlas under Developer tools and made by Dalton Solutions, LLC.

  • Do people use Tabfleet?

    Established: 74 installs/mo (npm).

  • Is Tabfleet still maintained?

    Actively maintained: release 11 days ago · site updated 3 weeks ago.

  • Who owns Tabfleet?

    Tabfleet is run by Dalton Solutions, LLC, per its privacy policy (2026-10-14).

  • Does Tabfleet give refunds?

    In its own words (terms of service, 2026-10-14): “Within 14 days of purchase, email support@tabfleet.com to request a refund of unused purchased minutes.”

  • What are alternatives to Tabfleet?

    In Developer tools, by use: Cloudflare, TestMu AI (Formerly LambdaTest), Ollama, TinyFish, Vercel, Testsigma Agentic Test Automation Tool.

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.