CopilotKit Raises $27M Series A — AG-UI Protocol Goes Mainstream

Seattle-based CopilotKit on May 5, 2026 announced a $27 million Series A co-led by Glilot Capital, NFX and SignalFire, as Google, Microsoft, Amazon, Oracle, AWS, LangChain and Mastra confirm production support for AG-UI — the open protocol CopilotKit created to connect AI agents to real application user interfaces.

What Happened

CopilotKit, the open-source frontend stack behind the AG-UI agent protocol, said the round consists of $20M in new Series A capital plus a previously unannounced $7M seed, bringing total funding to $27M. The financing was first reported by TechCrunch and GeekWire, with the company simultaneously launching CopilotKit Enterprise Intelligence, a self-hostable bundle for deploying agents inside existing apps. Co-founder and CEO Atai Barkai — previously a media-infrastructure engineer at Meta and a flagship-iOS lead at Doximity — framed the raise as a bet that "agent-native applications" will replace the current generation of standalone chat UIs.

CopilotKit on GitHub — the frontend stack for AI agents and Generative UI, makers of the AG-UI protocol — CopilotKit's GitHub repo — the project has crossed 40,000 stars and reports millions of npm installs per week.

Key Details

Round size and lead: $20M Series A led by Glilot Capital, NFX and SignalFire, plus a $7M seed extension — $27M cumulative.
Headquarters: Seattle, with most of the engineering team based locally.
Open-source traction: The CopilotKit repo on GitHub has more than 40,000 stars and the AG-UI protocol is licensed under MIT.
Named enterprise customers: Deutsche Telekom, DocuSign, Cisco and S&P Global.
AG-UI protocol adopters: Google, Microsoft, Amazon, Oracle, AWS, LangChain, Mastra, PydanticAI, Agno and others — positioning it as a peer to MCP and A2A in the emerging agent stack.
New product: CopilotKit Enterprise Intelligence — a self-hostable runtime that bundles agent observability, generative-UI rendering and RBAC so agents can ship inside regulated apps.

What Developers and Users Are Saying

Developer reaction on Hacker News, r/LocalLLaMA and X has been notably warmer than for most agent funding rounds. Engineers point to AG-UI's narrow scope — it standardises only the agent ↔ UI stream and intentionally leaves agent orchestration to MCP and A2A — as the reason the big platforms were willing to adopt it without political fights. The most upvoted critique is that the agent-protocol space is now crowded (MCP for tool use, A2A for agent-to-agent, AG-UI for UI) and small teams are wondering which to invest in first. CopilotKit's answer in their launch post is that the three protocols compose: MCP gives the agent its tools, A2A connects it to other agents, and AG-UI is how the result reaches the user.

What This Means for Developers

If you are building any product that embeds AI agents inside an application UI — copilots, generative dashboards, in-app assistants — AG-UI is now effectively a default. With Google, Microsoft, AWS and Oracle all shipping AG-UI-compatible runtimes, picking up the protocol today gives you a portable interface layer that should outlast any single vendor's SDK. Practically: if you're on React or Angular, the CopilotKit packages are the fastest path; if you're on a different stack, AG-UI is just a stream of typed events you can implement yourself in a few hundred lines.

The Enterprise Intelligence launch matters specifically for teams in regulated industries who couldn't adopt CopilotKit Cloud — you can now self-host the entire agent runtime inside your VPC.

What's Next

CopilotKit says the new capital will fund engineering hires in Seattle, expanded support for non-React frameworks, and tighter integrations with the AG-UI co-spec partners. Watch for first-party AG-UI shipping inside Google Vertex Agent Builder, Amazon Bedrock AgentCore and Microsoft Copilot Studio later in 2026, and for the protocol to formally graduate into a community-governed spec under the ag-ui-protocol GitHub organisation.

CopilotKit Raises $27M Series A as Google, Microsoft, AWS and Oracle Adopt Its AG-UI Agent Protocol (May 5, 2026)

What Happened

Key Details

What Developers and Users Are Saying

What This Means for Developers

What's Next

Sources