Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI / ML platform teams + agent developers + enterprise infrastructure teams running production stateful agent workloads today have been either (a) running agents on raw Kubernetes with hand-rolled session management + state persistence + autoscaling (high maintenance burden, slow session activation, no oversubscription), (b) adopting a single-vendor agent platform (LangGraph Cloud, CrewAI Ent
Who should use it
Who should skip it
Consider Google Agent Substrate: Apache-2.0 Kubernetes-Native Agent Scheduler with 30x+ Oversubscription (702*, 250 Actors / 8 Pods Demo) lower priority if you already have a working solution in this category.
About this signal
Google Agent Substrate: Apache-2.0 Kubernetes-Native Agent Scheduler with 30x+ Oversubscription (702*, 250 Actors / 8 Pods Demo) is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on AUTOFILL_NOW. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Google Agent Substrate: Apache-2.0 Kubernetes-Native Agent Scheduler with 30x+ Oversubscription (702*, 250 Actors / 8 Pods Demo) leads on novelty (9.0) and workflow potential (8.7); its lowest signal is maturity (6.3), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Google Agent Substrate: Apache-2.0 Kubernetes-Native Agent Scheduler with 30x+ Oversubscription (702*, 250 Actors / 8 Pods Demo) a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 702* repo is at active maintenance but the consumer SHOULD note the README explicitly says `This is not an officially supported Google product. This project is not eligible for the Google Open Source Software Vulnerability Rewards Program`; the consumer SHOULD note the production deployment requires a Kubernetes cluster + gVisor; the consumer SHOULD review the actor-to-worker assignment policy before production; the consumer SHOULD review the full-state snapshot persistence storage backend before production.