Who This Signal Is For: CTOs, VP Engineering, Tech Leads, and Senior Engineers at companies between $1M and $50M ARR actively managing developer velocity, agent deployment security, and the infrastructure cost implications of the shift from chat-based to long-running agentic workflows.
Google shipped Antigravity and Managed Agents API at Google I/O 2026 the same week Anthropic demonstrated on-premises sandboxes and MCP tunnels at Code with Claude London. Two platforms. Same enterprise Engineering buyer. Same week. Different approaches to the same infrastructure category.¹
Both removed the security objection that has been blocking enterprise agent deployment. Both removed the capacity constraints that were stalling enterprise workloads. The two reasons CTOs have been using to defer the agentic infrastructure decision are gone simultaneously, which means the decision itself has arrived.
Relve rates this 85/100, a high signal for CTOs and Engineering leaders actively managing developer velocity, agent deployment security, and the infrastructure cost implications of the shift from chat-based to long-running agentic workflows.
Home-grown LangChain orchestration is now the most expensive option on the table. The question is not whether to move to managed agent infrastructure. It is which platform to move to, and whether the Engineering team has a written position before the sprint in which the default choice gets made.
Antigravity and Claude Code are not the only decisions this week created. The same announcements also changed how founders are weighing vendor lock-in across the entire stack. The series also covers Marketing, Operations, and Creatives.
The Agentic Developer Stack Just Got Two Competing Blueprints in the Same Week
For three years, the developer toolchain moved in one direction: AI assistance getting closer to the code. GitHub Copilot completed lines. Cursor completed files. Claude Code completed functions and then whole modules.
That trajectory hit a different kind of inflection this week. The question is no longer how much of the code AI can write. It is whether the agent infrastructure running underneath the tools is something Engineering builds itself or something it rents from a platform.
Google and Anthropic answered that question from opposite directions simultaneously. Google’s answer at I/O was Antigravity, a consolidated agentic developer platform, alongside Managed Agents API, which replaces home-grown LangChain orchestration at significant cost.²
Anthropic’s answer at Code with Claude SF was Claude Managed Agents in public beta, with multi-agent orchestration, outcomes tracking, and dreaming memory that persists context across sessions without re-initialisation.³
The London event added the piece that has been blocking enterprise deployment for most of the past year. Anthropic demonstrated sandboxed on-premises agents, running entirely on customer infrastructure with zero internet exposure, and MCP tunnels that let agents query internal systems without touching the public internet.⁴
The security baseline that CTOs have been using to defer agent deployment has changed. The objection is now a solved problem, not a reason to wait.
Anthropic’s compute partnership with SpaceX brings roughly 300MW and 220,000 GPUs online, doubling Claude Code rate limits and removing peak-hour caps that were stalling enterprise workloads.⁵
Google’s 8th-gen TPU delivers approximately 1,500 tokens per second on Flash at around 2x performance per watt versus its predecessor, with roughly 80 percent better cost-performance for inference workloads.⁶
The competitive field Engineering teams must now position against spans four distinct approaches:
- Antigravity: Google’s consolidated agentic developer platform, bundled with the $100 Ultra subscription and $100 in API credits. Scope confirmed from I/O 2026; verify exact boundaries against blog.google before any commercial commitment²
- Claude Code: Anthropic’s agentic coding environment, updated at Code with Claude SF with remote continuation, chapters, inline comments, auto-mode, and worktrees for isolated branch work⁷
- GitHub Copilot Workspace: Microsoft’s existing agentic dev environment, now competing directly with both new entrants on the same enterprise buyer
- Cursor: the independent AI-native IDE that built the category both platforms are now entering
On r/LocalLLaMA, engineers tracking the announcements flagged the same concern independently: the question is not which platform writes better code. It is which platform gives Engineering teams the observability, governance, and agent memory infrastructure to run production workloads reliably.
Posts from the r/LocalLLaMA community on Reddit
Fiona Fung of Anthropic put the shift directly at Code with Claude London: the bottleneck for Engineering teams has moved from writing code to reviewing and designing. That framing holds regardless of which platform a team chooses.⁴
CTOs Now Have Three Infrastructure Decisions That Cannot Be Deferred
Here is a scenario playing out in Engineering teams right now. A senior engineer proposes migrating the team’s agent orchestration layer from LangChain to a managed alternative. The CTO agrees in principle. The sprint ends. The migration stays on the backlog.
Six months later, LangChain is still running, the maintenance overhead has grown, and two engineers are spending four hours a week keeping it stable instead of building product. That is not a discipline problem. It is an infrastructure decision that was never written down.
Both Google and Anthropic shipped managed alternatives this week that change the cost calculation on every sprint that passes without a documented position. For CTOs, this creates three specific decisions that compound in cost the longer they stay undocumented.
| Dimension | Before Google I/O + Code with Claude | After Google I/O + Code with Claude |
|---|---|---|
| Agent orchestration | Home-grown LangChain or custom tooling carrying 4+ hours weekly maintenance overhead per engineer | Managed Agents API (Google) or Claude Managed Agents (Anthropic) replace home-grown orchestration with platform-maintained infrastructure |
| On-premises security | Agents require internet access to function, a valid blocker for regulated industries and enterprise security requirements | MCP tunnels and on-prem sandboxes keep agents inside corporate boundary, security objection is now a configuration choice |
| Context persistence | Agent session ends, context is lost, next session restarts from scratch adding re-initialisation cost to every long-running workflow | Claude dreaming memory persists context across sessions automatically, re-initialisation overhead eliminated for Anthropic-stack deployments |
| Developer platform | Cursor and GitHub Copilot Workspace as the primary agentic developer tools, no Google-native alternative at this capability level | Antigravity enters as Google’s consolidated answer, Engineering teams on Google Cloud now have a native agentic dev platform option |
| Compute capacity | Rate limits and peak-hour caps stalling enterprise Claude workloads, 80x demand surge outpacing available capacity⁵ | SpaceX partnership: doubled Claude Code rate limits, peak-hour caps removed, capacity ceiling gone for enterprise workloads |
Decision 1 – Managed Agents: Build Your Own or Use Platform Infrastructure
The honest cost of home-grown orchestration is not the build cost. It is the maintenance cost that accumulates every quarter after the build. A LangChain-based orchestration layer that took four weeks to build now takes two engineers half a day each week to keep stable, patch for dependency conflicts, and update when the underlying models change.
At a fully-loaded engineering cost of $100 to $150 per hour, that is $3,000 to $4,500 per month before any feature work is counted. Both platforms now offer a managed alternative that removes that overhead entirely.
Google’s Managed Agents API handles orchestration at the platform level.² Anthropic’s Claude Managed Agents adds two capabilities home-grown orchestration cannot replicate: outcomes tracking, which lets Engineering define what agent success looks like rather than monitoring raw outputs manually, and dreaming memory, which persists context across sessions so long-running workflows do not restart from zero each time.³
The practical workflow for evaluating the switch:
- Identify one current home-grown orchestration workflow that runs at least weekly
- Map its maintenance overhead in engineer-hours per sprint for the last three sprints
- Run a 30-day pilot on Managed Agents API or Claude Managed Agents against the same workflow
- Measure four numbers: maintenance hours saved, error rate, outcome reliability score, and engineer time freed per sprint
- Use the $100 Antigravity API credits bundled with the Google Ultra subscription to run the Google side of the pilot at zero additional cost
Multi-agent orchestration, where large tasks are broken into agent teams running in parallel, is now available on both platforms. Engineering teams that have been deferring agent architecture decisions because single-agent workflows were too limited now have a different set of constraints to work with.³
The agent deployment timelines that were taking months to build and stabilise are compressing. The decision is now about which managed infrastructure Engineering deploys on, not whether to deploy at all.
Decision 2 – Security Architecture: MCP Tunnels and On-Premises Sandboxes
The most common reason CTOs have been deferring agent deployment is not cost. It is the security review that comes back with the same finding every time: agents require internet access to function, and the security team will not approve internet-exposed agents on production data. That objection is now removable.
Anthropic demonstrated two specific configurations at Code with Claude London that change the security architecture options available to enterprise Engineering teams.⁴ On-premises sandboxes run agents entirely on customer infrastructure with no internet exposure at any point in the workflow.
MCP tunnels let agents query internal systems including databases, CRMs, ERPs, and internal APIs without requiring a single outbound internet connection. This directly unblocks Engineering teams in regulated industries that have been waiting on a security-compliant deployment path:
- Financial services teams blocked from using cloud-hosted agents on trading or client data workflows
- Healthcare Engineering teams where patient data cannot leave the corporate network under any configuration
- Enterprise Engineering teams with ISO 27001 or SOC 2 requirements that precluded internet-exposed agent infrastructure
- Government and defence-adjacent Engineering teams where network boundaries are a hard contractual requirement
The compliance checklist before deployment:
- Confirm which agent workflows touch regulated data before selecting between on-prem sandbox and MCP tunnel configuration
- Document which internal systems MCP tunnels will connect to and confirm access controls before the first connection
- Verify on-prem sandbox configuration meets existing security policy before presenting it to the security team
- Legal must confirm the data governance policy covers agent-generated outputs before any agent touches production data
- Run a security audit on the first pilot before expanding to additional workflows regardless of initial results
- MCP tunnels and on-prem sandboxes remove the security objection but do not replace the governance policy.
- An agent that can access internal systems without internet exposure still needs a documented policy covering which systems it can query, what it can do with the output, and who reviews agent actions before they execute on production data.
- Build the policy before the pilot, not after the first incident.⁴
Decision 3 – Agentic Developer Platform: Antigravity vs Claude Code vs Current Stack
Every Engineering team currently using Cursor or GitHub Copilot Workspace as its primary agentic development tool now has two new entrants targeting the same workflow. The evaluation is not straightforward because the platforms approach the problem differently.
Antigravity is Google’s consolidated answer to the agentic developer platform question, bundled with the $100 Google Ultra subscription including $100 in API credits. Verify the precise scope against blog.google before any commercial commitment.² Claude Code at Code with Claude SF shipped seven specific enhancements: remote continuation, chapters and table of contents, inline comments, auto-mode for safe autonomous execution, and worktrees for isolated branch work.⁷
The bottleneck shift Fiona Fung named at Code with Claude London is the most important framing for this decision.⁴ When the bottleneck moves from writing code to reviewing and designing, the evaluation criteria for a developer platform change entirely.
The question is no longer which tool writes the most code per hour. It is which tool gives Engineering the review infrastructure, the observability, and the governance controls to run agent-generated code safely in production.
How to benchmark the two platforms against each other in 30 days:
- Pick one new service being built from scratch as the pilot, not an existing codebase with accumulated context
- Run one engineer on Antigravity and one on Claude Code in parallel for one full sprint
- Measure three numbers: pull requests per sprint, review time per pull request, and time from specification to first deployment
- At sprint end, Engineering lead scores both outputs on review burden: how much human judgment was required to get agent-generated code to production-ready state
- Document the written platform position before the sprint review ends
If your Engineering team is already standardised on Google Cloud infrastructure, Antigravity has a distribution and integration advantage the benchmark may not fully capture.
Factor in the toolchain integration cost of switching when comparing the pilot results.²
ROI and Cost Model for Engineering Leaders
The ROI case for this week’s announcements sits in three places: orchestration cost reduction, compute capacity recovery, and inference cost renegotiation. Each has a different time horizon and a different person who needs to act on it.
Orchestration cost reduction is immediate. If a team is running home-grown LangChain orchestration at two engineers spending four hours each per week on maintenance, the fully-loaded cost at $100 to $150 per hour is $3,000 to $4,500 per month. A 30-day pilot on either managed platform produces the comparison number.
Compute capacity recovery is also immediate for teams that have been hitting Claude rate limits or peak-hour caps. The SpaceX partnership removed those constraints this week.⁵ Engineering teams that were scheduling agent workloads around peak hours or batching jobs to stay within limits can stop doing that now.
Inference cost renegotiation is a Q3 decision. Google’s 8th-gen TPU delivers roughly 80 percent better cost-performance for inference workloads.⁶ For Engineering teams running significant Vertex AI inference spend, that number changes the contract renegotiation conversation with Google Cloud before the next renewal.
Direct cost savings to model:
- Home-grown orchestration maintenance hours eliminated: engineer-hours per sprint x fully-loaded hourly rate x 52 weeks
- Peak-hour scheduling overhead eliminated: hours per week spent batching and scheduling around capacity limits x fully-loaded hourly rate
- Inference cost reduction: current Vertex AI monthly spend x 80 percent cost-performance improvement x contract renegotiation timeline
- Developer velocity gain: pilot output in pull requests per sprint vs current baseline x fully-loaded daily engineering cost
Costs to subtract:
- Google Ultra subscription: $100 per seat per month for Engineering and Product team members using Antigravity
- Claude Enterprise or API cost: usage-based, model against pilot workload volume before committing
- Security architecture review: Legal and Security team time to confirm MCP tunnel or on-prem sandbox configuration
- Migration cost: engineer-hours to migrate one home-grown orchestration workflow to managed infrastructure during the pilot sprint
The break-even calculation most Engineering leaders miss: the $100 Google Ultra subscription cost is recovered in less than one week of orchestration maintenance overhead elimination for a two-engineer team. The pilot cost is effectively zero when the $100 Antigravity API credits are applied against it.
For teams modelling the longer-term infrastructure economics, the inference economics shift that arrived earlier this year gives the full cost-performance context before any Vertex AI contract conversation begins.
The Part Most Engineering Leaders Are Getting Wrong
Most coverage of this week’s announcements focuses on which platform is better: Antigravity or Claude Code, Google or Anthropic, managed orchestration or home-grown. That framing misses the more important shift. The more useful read is that both platforms moved simultaneously because they are targeting the same enterprise Engineering buyer, and both know the window to become the default stack is this quarter.
The strongest data point from the week: Dario Amodei at Code with Claude SF reported Anthropic tracking toward $30B in annual run-rate revenue, and predicted that billion-dollar companies will be built on AI agents within the next few years.³ That is not a product announcement. It is a signal about how much compute infrastructure Anthropic is prepared to fund to become the default Engineering stack.
Most Engineering leaders are optimising for developer velocity. The metric that matters more at scale is decision fidelity, how accurately a verbal architecture decision in a standup translates into tracked, reviewable, auditable work. Both managed agent platforms change that metric more than they change raw code output per engineer.
Three things most Engineering leaders are not accounting for:
- The agent observability gap. Neither Google’s nor Anthropic’s announcements this week cover agent observability in detail. Engineering teams deploying production agent workloads need monitoring dashboards for session success rates, token usage per workflow, error rates, and agent action logs. That infrastructure does not come with the platform. Engineering must build it independently before the first production deployment.
- The outcomes tracking skill gap. Anthropic’s outcomes tracking feature lets Engineering define success criteria for agents. Most Engineering teams have never written an agent success criterion. The feature exists. The skill to use it does not yet exist at most companies. Teams that invest in that skill before deploying will govern agent behaviour at scale. Teams that skip it will monitor raw outputs manually, which is what they were doing before managed agents existed.
- The vendor default risk. The tool the Engineering team starts using this sprint becomes the default infrastructure in 12 months unless someone documents a deliberate position before the first commit. Both Google and Anthropic are pricing their platforms to make the default choice easy. That is not generosity. It is lock-in strategy. A written vendor position before the sprint ends is worth significantly more than a migration plan written 12 months later.
Engineering teams that deploy managed agent infrastructure without a written observability plan, a defined outcomes tracking framework, and a documented vendor position are not moving faster. They are creating technical debt in a category where reversing course is significantly more expensive than getting the position right the first time.⁴
Engineering leaders evaluating which platform to build on should also understand how inference economics are shifting before committing to any infrastructure contract. The compute cost model changes the vendor decision at scale in ways the pilot benchmark will not capture.
What Engineering Leaders Should Do This Quarter
One security decision before anything else starts, one pilot once the architecture is confirmed, one platform benchmark before the quarter ends. Mapped across the next 90 days.
No pilot starts before this decision is made in writing. The security architecture choice determines which platform configuration is viable for your Engineering team’s specific data and compliance requirements. Getting it wrong after a pilot has already run is significantly more expensive than making it before.
The decision covers five questions that must have written answers before any agent touches production data:
- Which agent workflows will Engineering run in the next 90 days, and which of those touch regulated or sensitive data?
- Does the data sensitivity require on-prem sandbox deployment, MCP tunnel configuration, or is standard cloud-hosted agent infrastructure acceptable?
- Which internal systems will agents need to query, and what access controls need to be confirmed before the first MCP tunnel connection?
- What does Legal need to confirm about agent-generated outputs before any agent executes on production data?
- Who in Engineering owns the governance policy for agent actions, and what is the review process before an agent action executes?
Get the security architecture decision in writing before the pilot starts. A governance policy retrofitted after the first production agent deployment costs significantly more in remediation time than a policy written before the first commit. Assign one person to own this before the end of the current sprint.
Once the security architecture decision is documented, pick one internal workflow that currently runs on home-grown LangChain orchestration and pilot it on managed infrastructure for 30 days. The pilot tests one specific question: does managed infrastructure reduce maintenance overhead without reducing reliability?
The pilot structure:
- Pick one workflow that runs at least weekly and has a measurable output, not a new workflow being built from scratch
- Run Managed Agents API or Claude Managed Agents on that workflow for 30 days alongside the current LangChain version
- Use the $100 Antigravity API credits bundled with the Google Ultra subscription for the Google side at zero additional cost
- Measure four numbers at the end of 30 days: maintenance hours saved per sprint, error rate comparison, outcome reliability score, and engineer time freed
- Do not expand to additional workflows until the pilot output has been reviewed and the security audit on the first workflow has been completed
Measure These
Maintenance hours saved per sprint vs LangChain baseline
Error rate: managed vs home-grown over same 30-day period
Outcome reliability: did the agent complete the workflow successfully each run
Engineer time freed: hours previously spent on orchestration maintenance now available for product work
Ignore These in the Pilot
Raw code output volume: not the relevant metric for managed orchestration
Feature parity between platforms: evaluate after reliability is confirmed
Cost comparison at pilot scale: model at production volume, not pilot volume
Platform preference from individual engineers: the decision is infrastructure, not IDE preference
Run the pilot on internal workflows only. Do not include customer-facing workflows, external stakeholder calls, or any workflow touching customer data in the initial pilot. Expand only after the security audit on the first workflow is complete and the governance policy has been confirmed by Legal.
The pilot tests managed orchestration. This benchmark tests developer platform choice. Pick one new service being built from scratch and run one engineer on Antigravity and one on Claude Code in parallel for one full sprint. The output is a written platform position, not a preference conversation.
The benchmark structure:
- Pick one new service with a clear specification, not an existing codebase with accumulated context and tribal knowledge
- Run one engineer on Antigravity and one on Claude Code in parallel for one full sprint
- Measure three numbers: pull requests per sprint, review time per pull request, and time from specification to first deployment
- At sprint end, Engineering lead scores both outputs on review burden: how much human judgment was required to get agent-generated code to production-ready state
- Factor in toolchain integration cost if Engineering is standardised on Google Cloud: Antigravity has a distribution advantage the benchmark metrics alone will not capture
- Document the written platform position before the sprint review ends, covering which platform Engineering defaults to for the next 12 months and what benchmarks would trigger a reassessment
A platform position written after the Engineering team has already standardised on one tool is a post-rationalisation, not a decision. The sprint in which the benchmark runs is the last moment the position can be written without a migration cost already embedded in the codebase. Write it before the sprint review ends.
Document your agentic infrastructure position before the end of this quarter, or spend the next 12 months unwinding a vendor dependency that was never deliberately chosen.
Key Takeaways
Both Google and Anthropic removed the two objections Engineering teams were using to defer agent deployment: security and capacity. Those objections are gone. The infrastructure decision is what remains.
GitHub Copilot Workspace and Cursor now compete against two platforms with significantly more infrastructure and distribution than either had a month ago. The category that Cursor built is now the category Google and Anthropic are entering at scale.
Write the security architecture decision before the end of this month. Everything else follows from that one question answered in writing before the first agent touches production data.
References
¹ Google, “Google I/O 2026 Developer Highlights,” May 2026.
³ Anthropic Blog, “Code with Claude San Francisco Announcements,” May 6, 2026.
⁴ Anthropic Blog, “Code with Claude London – On-Premises Sandboxes and MCP Tunnels,” May 19, 2026.
⁵ Relve, “SpaceX Compute Partnership – Doubled Rate Limits, Peak-Hour Caps Removed,” May 2026.
⁶ Google Cloud Blog, “8th-Gen TPU – TPU 8t and TPU 8i Performance,” April 2026.
⁷ Anthropic Blog, “Claude Code Enhancements – Remote Continuation, Auto-Mode, Worktrees,” May 2026.
