Skip to content
Independent thinking. Connected delivery.
UAE Australia Company Client access ↗
Emerge Digital
Explore Emerge
Book a conversation →

Cloudflare OS connectors

A Gatekeeper is the Worker that sits between a Cloudflare OS agent and one external system — wrapping its API, narrowing what the agent can reach, logging every read, and holding every write for a person to approve.

Cloudflare ships Gatekeepers for the systems you would expect. It does not ship them for regional or self-hosted tools, and since the project is not accepting outside code contribution, those live in other people's repositories by design. These are ours, with the detail that only comes from having built them.

A gatekeeper in front of a system Cloudflare OS does not ship Edge path from a Cloudflare OS agent through a custom gatekeeper to a system with an approval queue. Cloudflare OS agent → Gatekeeper → Auth model → API shape → Observer → Approval queue EDGE Cloudflare OSagent Gatekeeper WORKERS Auth model API shape ORIGIN Observer Approval queue Cloudflare OSagent Gatekeeper Auth model API shape Observer Approval queue
  1. Cloudflare OS agent
  2. Gatekeeper
  3. Auth model
  4. API shape
  5. Observer
  6. Approval queue

Edge path from a Cloudflare OS agent through a custom gatekeeper to a system with an approval queue.

Illustrative connector pattern. Auth, API shape and observer choices are in each article.

Considering Cloudflare OS itself?

We deployed it in its first week and wrote up what the licence permits, which pieces are still in beta, why upstream contributions are closed, and the setup details the README leaves out.

Every connector listed as published points at working, Apache-2.0 code. Emerge Digital is not affiliated with or endorsed by Cloudflare.

Your Emerge companion

AI thinking. Human expertise.

A good place to start

What could we
build together?

Explore an idea, shape a project, or get help from our team. We’ll find the right next step with you.

Explore solutions at your own pace ↗