Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
Comparison · Infra & APIs
Payload CMS vs TestingBot
A side-by-side editorial comparison of Payload CMS and TestingBot — release velocity, themes, recent moves, and the top alternatives to consider.
Payload CMS vs TestingBot: at a glance
What is Payload CMS?
Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
What is TestingBot?
A browser grid that spent the summer becoming a team product, and is now opening itself to agents.
TestingBot runs a cross-browser and real-device cloud, and the last three months have gone almost entirely into what surrounds a test run rather than the run itself: custom roles enforced identically in dashboard and API, service accounts so pipelines stop borrowing a person's credentials, enforced two-factor authentication, comments with @mentions on failed runs, one-click filing into GitHub, Jira, Trello, Asana or Azure DevOps, and a notification inbox tying it together. The grid work continues underneath — WebRTC streaming for iOS simulators, a rebuilt web inspector, new devices and browser versions on the usual cadence.
Payload CMS vs TestingBot: editorial side-by-side
Payload CMS
6.3INFRA · APIS
Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.
◆ Current state
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
◆ Where it's heading
The 4.0 beta lands every three to five days, and each one is smaller than the last. beta.0 shipped the admin redesign, TanStack support and the new MCP. Later betas covered adapters, Next.js cache components and accessibility, and beta.5 is mostly correctness and supply-chain hygiene, which suggests a release candidate is close.
◆ Prediction
Expect one or two more fix-only betas, then a 4.0 release candidate. The SBOM addition suggests supply-chain artifacts will carry over to stable releases.
TestingBot
5.0INFRA · APIS
A browser grid that spent the summer becoming a team product, and is now opening itself to agents.
◆ Current state
TestingBot runs a cross-browser and real-device cloud, and the last three months have gone almost entirely into what surrounds a test run rather than the run itself: custom roles enforced identically in dashboard and API, service accounts so pipelines stop borrowing a person's credentials, enforced two-factor authentication, comments with @mentions on failed runs, one-click filing into GitHub, Jira, Trello, Asana or Azure DevOps, and a notification inbox tying it together. The grid work continues underneath — WebRTC streaming for iOS simulators, a rebuilt web inspector, new devices and browser versions on the usual cadence.
◆ Where it's heading
Two directions are visible. The platform is being made safe for organisations rather than individuals, which is what roles, service accounts, 2FA and audit-friendly reporting add up to. Alongside it, the grid is being made reachable by software instead of people: an Insights API exposing pass rates and flakiness, embeddable build reports for CI dashboards, GitHub checks on every pull request, and now Vibium's CLI and MCP server pointed straight at the grid over WebDriver BiDi. The AI work so far reads results — failure analysis, documentation questions — while Vibium is the first path where something other than a human-written script drives the browser.
◆ Prediction
Expect the agent-facing path to be developed further, since supporting Vibium's MCP server without extra configuration is a small step from offering a first-party one, and expect the device and browser catalogue to keep rotating on its established cadence.
Alternatives to Payload CMS and TestingBot
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Payload CMS or TestingBot.
NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io
incident.io's agent now runs your team's own tools, with a human approval before any change.
Apache Airflow
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
See all Payload CMS alternatives → · See all TestingBot alternatives →
Recent activity from Payload CMS and TestingBot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoPayload CMSPayload 4.0 beta 5: GraphQL, upload and password-reset fixes
- 7d agoPayload CMSPayload 4.0 beta 4: accessibility fixes, Node 24.22.1 minimum
- 9d agoPayload CMSPayload 4.0 beta 3 adds Next.js cache components support
- 13d agoPayload CMSPayload 4.0 beta 2 moves to stable TanStack Start
- 15d agoPayload CMSPayload 4.0 beta 1: codemod and docs fixes
- 19d agoPayload CMSPayload 4.0 beta: admin redesign, TanStack support, new MCP ⚡
- 2mo agoTestingBotVibium browser automation
- 2mo agoTestingBotSamsung Galaxy Tab S11 in the real device cloud
- 3mo agoTestingBotEmbeddable build reports for CI
- 3mo agoTestingBotNotifications in the dashboard
- 3mo agoTestingBotChrome 150 and Edge 150
- 3mo agoTestingBotGitHub pull request checks
Frequently asked questions
What is the difference between Payload CMS and TestingBot?
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Payload CMS better than TestingBot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Payload CMS?
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.
What are the best alternatives to TestingBot?
Top TestingBot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "TestingBot alternatives" section above for the current picks, or visit /alternatives/testingbot for the full list with editorial commentary on each.