· investment-strategies  · 2 min read

RWX's $12M Series A: Why Hyde Park Backed CI Built for Coding Agents

Hyde Park Venture Partners led RWX's $12M Series A as CI becomes the bottleneck — Honeycomb, Verkada, and nCino need validation that keeps up with AI-written code.

When an agent writes a change in five minutes, a ten-minute CI run is no longer “acceptable overhead.” It is two-thirds of the loop. That is the problem RWX raised against — a $12 million Series A led by Hyde Park Venture Partners on August 4, 2026.

Deal snapshot

FieldDetail
Amount$12M Series A
LeadHyde Park Venture Partners
ParticipantsQuiet, The O.H.I.O. Fund, R1, DV
AngelsKohsuke Kawaguchi (Jenkins), Bryan Johnson, Theo Browne
HQ / foundersDan Manges (CEO; ex-Braintree CTO, Root co-founder) & Tommy

Who uses the product — and why

RWX sells a dev cloud for build, test, and deploy — purpose-built for AI-driven engineering rather than retrofitted from human-paced CI.

Named customers include:

  • Honeycomb — cited content-based caching so CI stops rerunning unchanged work as AI volume spikes.
  • Verkada, nCino (NASDAQ: NCNO), Coalesce — teams migrating from GitHub Actions-era pipelines.

Differentiator that matters operationally: agents talk CLI, not PR webhooks. RWX can run sandboxes, full CI, and preview deploys without a git commit — the interface agents already prefer.

Why now

Pre-AI, redundant CI was annoying. Post-AI, agent fleets multiply job volume. The bottleneck moved from writing code to validating it. Founders with Root/Braintree scars built RWX around caching graphs and OCI-compatible containers that finish fast enough that humans — and Claude — sometimes distrust the green check.

Why Hyde Park leads (portfolio fit)

Hyde Park Venture Partners is Chicago-based, early-stage, and thesis-aligned on AI + software with mid-continent roots. Leading a Series A for developer infrastructure matches how they underwrite first/second institutional rounds — ShipBob and G2 sit in the same “operators who know the workflow” pattern.

Likely reasons RWX chose Hyde Park:

  1. Stage fit — Series A check without forcing a growth-equity process.
  2. Midwest / operator network — The O.H.I.O. Fund and Root alumni gravity reinforce the syndicate.
  3. Conviction on infra, not chatbots — HPVP’s AI software focus fits “picks and shovels for agent engineering.”

Competitive map

ToolDefault assumption
GitHub ActionsUbiquitous; designed for human PR cadence
Buildkite / CircleCIStrong CI; less agent-native story
RWXAgent-first execution + content-based caching

When not to bet this way

  • GitHub ships agent-native CI that closes the speed gap.
  • Teams refuse to leave Actions for compliance / marketplace inertia.
  • Caching wins prove brittle on monorepos with weak hermeticity.

Practical takeaway

Founders: Sell minutes saved × agent runs per day — not “AI CI” as a vibe.
Investors: The durable asset is the execution substrate (cache graph + CLI), not a prettier YAML UI.

Sources

  1. RWX blog: https://www.rwx.com/blog/series-a
  2. VentureBeat: https://venturebeat.com/business/rwx-raises-12m-series-a-to-scale-the-dev-cloud-for-ai-driven-engineering

Frequently Asked Questions

Common questions about this topic

Back to Blog

Related Posts

View All Posts »