Category comparison

Cloudflare Agents vs an app-agent backend

Use Cloudflare Agents when you want to build and deploy stateful agents on Cloudflare infrastructure. Use General Augment when the app needs a governed product-agent backend with stable app users, memory, tools, approvals, channels, usage, traces, and customer-owned connector policy.

Start building Learn the category

Use Cloudflare Agents when

Your team wants agent runtime infrastructure on Cloudflare.
You need stateful agents, WebSockets, scheduling, or long-running agent patterns.
Your engineering team will shape the agent harness and product integration.

Use General Augment when

Your app needs a managed agent backend above runtime primitives.
You need project-scoped identity, memory, governed tools, approvals, channels, usage, and traces.
You want private hosts, sandboxes, or provider accounts exposed as narrow approved actions.

Decision table

Compare the layer, not just the feature list.

Decision area

Cloudflare Agents

General Augment

Runtime

Cloudflare Agents gives stateful infrastructure, real-time connections, scheduling, and long-running patterns.

General Augment gives the product-facing backend layer that apps integrate with.

Harness

Cloudflare gives primitives and examples; your team shapes the harness and app semantics.

General Augment packages project, user, memory, tool, approval, channel, usage, and trace semantics.

Private capacity

Cloudflare can host runtime and sandbox-style workloads.

General Augment can govern customer-owned capacity through connectors without owning every execution host.

Architecture fit

Where the categories fit together.

Cloudflare Agents can be a runtime substrate. General Augment is the app-agent backend layer that coordinates product identity, governed tools, memory, approvals, channels, usage, and traces.

Runtime plus product backend

Existing app
  -> General Augment /v1/responses
  -> governed capability
  -> Cloudflare Agent or Worker
  -> approved result and trace evidence

Sources checked

Cloudflare Agents docs Cloudflare long-running agents

Migration path

Start where you are. Add the agent backend when the product needs it.

01
Use Cloudflare Agents for stateful runtime needs or agent infrastructure on Cloudflare.
02
Use General Augment when the product needs a managed app-agent backend that works across app surfaces.
03
Expose Cloudflare-hosted agent capabilities as governed tools if they should sit behind app-user policy.
04
Keep app auth, billing, UX, permissions, and source of truth in the product.

Specific examples

Cloudflare-hosted worker

A Cloudflare Agent can run a long-lived task while General Augment governs when the product assistant may start or inspect it.

Customer-facing app agent

General Augment gives the app team one backend route for user memory, governed tools, approvals, channels, usage, and traces.

Private connector model

Customer-owned hosts can expose narrow actions while General Augment controls the model-facing surface.

When not to use General Augment

Use the smaller tool when the smaller tool is enough.

Use Cloudflare Agents directly when your core need is Cloudflare-native stateful agent runtime.

Use Cloudflare Agents directly when you want to own harness design, storage, channel semantics, and product integration.

Use General Augment when the repeated app-agent backend surface becomes more important than runtime primitives.

FAQ

Does General Augment replace Cloudflare Agents?

No. Cloudflare Agents is useful runtime infrastructure. General Augment is useful when an existing app needs the managed backend around agent turns.

Can Cloudflare Agents sit behind General Augment?

Yes. A Cloudflare Agent or Worker can expose a bounded capability that General Augment governs as a tool or connector action.

Which should I use first?

Use Cloudflare Agents first if runtime placement is the main decision. Use General Augment first if app-user identity, memory, tools, approvals, channels, usage, and traces are the main decision.