ClamAV
Eight CVEs in one August batch — ClamAV's parser surface is the whole story.
A side-by-side editorial comparison of Infisical and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
Infisical is growing past secrets management into PAM, PKI and an agent credential proxy.
Infisical ships a fast GitHub release train — six versions in two weeks, each bundling dozens of merged PRs. The work splits cleanly into four product lines that no longer look like one: core secrets management, a privileged access manager gaining account types, a certificate authority stack, and an agent proxy that brokers credentials to services on a caller's behalf. A parallel UI migration is moving settings screens onto v3 components, and a caching pass has pushed trusted-IP allowlists, KMS material and org membership into Redis.
Retool is turning its app builder into a branched, multi-threaded agent workspace.
The current window is almost entirely about making the AI app builder controllable. A Building context setting lets teams pin instructions that apply across every app, multiple agent threads can now run on a single branch, and BYOK AI token usage is exposed through both an API endpoint and the Usage Analytics page. Alongside that, self-hosted operations get an admin onboarding hub with an Action Center and a mandatory one-time permissions database migration from 4.31 onward.
Infisical ships a fast GitHub release train — six versions in two weeks, each bundling dozens of merged PRs. The work splits cleanly into four product lines that no longer look like one: core secrets management, a privileged access manager gaining account types, a certificate authority stack, and an agent proxy that brokers credentials to services on a caller's behalf. A parallel UI migration is moving settings screens onto v3 components, and a caching pass has pushed trusted-IP allowlists, KMS material and org membership into Redis.
Each of the four lines is widening by connector rather than by rearchitecture: PAM picked up Redis accounts with browser access and connection tests across the remaining account types; rotation now covers Azure app credentials, LDAP, and Cloudflare API tokens and R2 keys; PKI added SCEP for Microsoft Intune and ADCS validation for external authorities. The agent proxy is the line to watch — it gained per-service last-used timestamps, adoption telemetry, a Google Workspace template, and the ability for user tokens to report proxied-service usage, which is the instrumentation you build before you price something. Machine identity is being hardened in parallel with expiry alerts and policy-template creation flows.
The adoption telemetry and last-used tracking around proxied services point to the agent proxy being packaged as its own thing; expect more prebuilt service templates alongside it.
The current window is almost entirely about making the AI app builder controllable. A Building context setting lets teams pin instructions that apply across every app, multiple agent threads can now run on a single branch, and BYOK AI token usage is exposed through both an API endpoint and the Usage Analytics page. Alongside that, self-hosted operations get an admin onboarding hub with an Action Center and a mandatory one-time permissions database migration from 4.31 onward.
Retool is treating agent-built apps like code: branches, parallel threads of work on the same branch, and shared standing instructions that behave like project configuration. The BYOK token endpoint points the same way, giving admins a way to attribute and cap model spend as agent usage becomes routine rather than experimental. The self-hosted items are the operational tax on that pace, with the permissions migration acting as a hard gate on the upgrade path.
The branch-and-thread model suggests the next steps are review and merge workflows for agent-authored changes, and finer-grained BYOK controls now that usage is measurable. The entries show the primitives but not a stated plan, so the sequencing is unclear.
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 Retool.
Eight CVEs in one August batch — ClamAV's parser surface is the whole story.
WorkOS is making agents first-class principals and taking custody of the tokens they act with.
Render swaps static keys for federated identity and opens its control plane to coding agents.
Tailnets become API-provisioned resources while Tailscale hardens SSH and thins the control plane.
Resend is turning an email API into something other people build products on.
Render is quietly becoming the credential broker between your services and AI providers.
See all Infisical alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Infisical and Retool are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Infisical and Retool are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Retool alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Retool alternatives" section above for the current picks, or visit /alternatives/retool for the full list with editorial commentary on each.