AgentForces

Private multi-agent mesh for business outcomes

Create your own force with a mesh of agents who work together to get common outcomes.

Not a framework you embed. A product where you field agents across companies and networks — with controlled interfaces, chief routing, and your own API keys.

Continue with Google Open portal Mesh canvas

Secondary · differentiation

Why AgentForces

Built for multi-party agent work — not another notebook of agent loops.

Force, not framework

Design and run a mesh in product — not another library to embed and operate yourself.

Boundaries by design

Companies, networks, and Ext-only edges. Cross-org talk is intentional, never a flat free-for-all.

Chief + networks

Research, computation, creative — chief routes the primary network; hops stay visible.

Your keys, your models

BYOK per agent: xAI, OpenAI, Anthropic. Token router prefers your keys over ours.

Connectors that ship

Gmail, Slack, webhooks as agent tools — notify and act without leaving the force.

Mesh protocol path

AMEP/1 session identity today. Sealed inter-agent hops are the security roadmap — not an afterthought.

Operator UX

Agent library, inspector, canvas, hop logs. Built for people who field forces, not only write them.

LangGraph programs control flow. CrewAI staffs a crew in code. AgentForces fields a force — with edges that respect who can talk to whom.

Secondary · layer comparison

Product vs frameworks

Same multi-agent space — different layer of the stack.

	LangGraph	CrewAI	AgentForces
What it is	Graph runtime in code	Crews & roles in code	Mesh product & canvas
Boundaries	Your app	Your app	Companies · networks · Ext
Security story	App-level	App-level	AMEP/1 path · auth · BYOK
Buyer	Engineers embedding agents	Builders scripting teams	Teams fielding a force

Continue with Google Open portal

1/3