authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Infisical vs TestingBot
A side-by-side editorial comparison of Infisical and TestingBot — release velocity, themes, recent moves, and the top alternatives to consider.
Infisical vs TestingBot: at a glance
What is Infisical?
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Infisical ships near-daily across four surfaces — secrets management, PKI and certificate manager, PAM, and KMS. This release adds folder-level RBAC, so permissions can be scoped inside a project rather than only at project and environment level, and gives approvals and change requests their own webhook events. PKI keeps widening: a GCP Certificate Manager sync, Windows and Linux pre-fetch commands for PKI syncs, and certificate renewals exposed so agents can follow them. Project retention limits and Kubernetes managed-identity auth templates round it out, alongside a long run of v3 UI migration work.
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.
Infisical vs TestingBot: editorial side-by-side
Infisical
6.3INFRA · APIS
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
◆ Current state
Infisical ships near-daily across four surfaces — secrets management, PKI and certificate manager, PAM, and KMS. This release adds folder-level RBAC, so permissions can be scoped inside a project rather than only at project and environment level, and gives approvals and change requests their own webhook events. PKI keeps widening: a GCP Certificate Manager sync, Windows and Linux pre-fetch commands for PKI syncs, and certificate renewals exposed so agents can follow them. Project retention limits and Kubernetes managed-identity auth templates round it out, alongside a long run of v3 UI migration work.
◆ Where it's heading
Two threads run underneath the release stream. Consolidation continues — dynamic secrets moved onto a shared provider registry this release, the same pattern that let native integrations enter deprecation in v0.162.22. The second is authorization getting finer rather than broader: folder RBAC, certificate private-key reads scoped to the certificate subject, LDAP bind passwords no longer returned on GET, and approval checks that respect validation rules. The product is being made safe to hand to more people inside one organisation, not just to more organisations.
◆ Prediction
Approval and change-request webhooks are the eventing half of a workflow whose UI shell just moved to v3, so external approval routing — the events feeding a reviewer outside Infisical — is the natural next step. The changelog is a PR list and states no plan.
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 Infisical 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 Infisical or TestingBot.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Infisical alternatives → · See all TestingBot alternatives →
Recent activity from Infisical and TestingBot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoInfisicalFolder-level RBAC lands; PKI syncs to GCP Certificate Manager
- 6d agoInfisicalPAM discovers Postgres accounts; gateway pools get load balancing
- 7d agoInfisicalRoot encryption key rotation lands; cert profiles move into applications
- 7d agoInfisicalPAM gains IAM auth for Postgres; KMS keys get delete protection
- 12d agoInfisicalTwo fixes: identity TLS cert constraints and rotation inputs
- 12d agoInfisicalCertificate manager adds PKCS#12 keystore import
- 22d agoTestingBotVibium browser automation
- 28d agoTestingBotSamsung Galaxy Tab S11 in the real device cloud
- 1mo agoTestingBotEmbeddable build reports for CI
- 1mo agoTestingBotNotifications in the dashboard
- 1mo agoTestingBotChrome 150 and Edge 150
- 1mo agoTestingBotGitHub pull request checks
Frequently asked questions
What is the difference between Infisical and TestingBot?
They serve adjacent needs but don't currently overlap on shipped themes. Infisical is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 Infisical better than TestingBot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Infisical is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 Infisical?
Top Infisical alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Infisical alternatives" section above for the current picks, or visit /alternatives/infisical 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.