DNSimple
DNSimple's origin name servers answer a quarter faster at p90 after erldns work
Comparison · Infra & APIs
Currents vs runc
A side-by-side editorial comparison of Currents and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Currents vs runc: at a glance
What is Currents?
Currents lists itself in the Claude and ChatGPT/Codex plugin directories.
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API. On November 3 it appeared in the Claude and ChatGPT/Codex plugin directories, so users connect from the listing without typing a server URL.
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
Currents vs runc: editorial side-by-side
Currents
6.3INFRA · APIS
Currents lists itself in the Claude and ChatGPT/Codex plugin directories.
◆ Current state
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API. On November 3 it appeared in the Claude and ChatGPT/Codex plugin directories, so users connect from the listing without typing a server URL.
◆ Where it's heading
The agent-access stack is built; Currents is now working on distribution. Plugin directory listings put the OAuth MCP server in front of users inside the agents themselves, while the October Project Overview serves people reading the dashboard.
◆ Prediction
Expect more agent-directory listings or deeper Claude Code and Codex workflows built on the trace API.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Alternatives to Currents and runc
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 Currents or runc.
Scalar
Scalar's November 5 releases give each API document its own authentication settings
Algolia
Algolia's AI Assist now writes merchandising rules from a plain-language request
SoftEther VPN
SoftEther returns after 16 months with Windows ARM64 support and a pile of fixes.
Jaeger
Jaeger 2.23 lets people and agents query traces in SQL.
Parse Server
Parse Server 9.11.1 alphas close two beforeSave advisories, one a server crash.
See all Currents alternatives → · See all runc alternatives →
Recent activity from Currents and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoCurrents[New] Connect Currents from the Claude and ChatGPT/Codex plugin directories
- 18d agoCurrents[Improved] A better GitHub run comment
- 18d agoCurrents[New] Project Overview
- 23d agoCurrents[New] Trace API for agents ⚡
- 1mo agoCurrents[New] Run attachments
- 1mo agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoCurrents[New] Remote MCP Server with OAuth
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
Frequently asked questions
What is the difference between Currents and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Currents is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Currents better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Currents is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Currents?
Top Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.
What are the best alternatives to runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.