[ SHORT ANSWER ]
Workers Secrets is the right choice for values your Worker code needs directly — it is free, encrypted at rest, and requires no additional service. It is the wrong shape when an LLM agent runs inside that Worker, because a bound secret is readable by the whole isolate, including the agent and anything a prompt injection persuades it to output.
This is the same structural issue as .env, moved to the edge. There is no per-agent identity, no path scoping, and no record of which agent read what. 1Claw's Free tier is enough to move agent-facing credentials out of the binding; Execution Intents, which remove the read entirely, start at Pro.
[ COMPARISON ]
1Claw vs Cloudflare Workers Secrets
Capability by capability. A dash means partial or qualified support — read the note.
[ WHEN TO USE ]
Which one is right for you
Most of these are not either/or. Where the competitor is the better answer, we say so.
Use Cloudflare Workers Secrets when
- Your Worker is deterministic code with no LLM in the loop.
- Latency budget rules out an outbound call to fetch a credential.
- The secret is low-value and easy to rotate.
Use 1Claw when
- An LLM agent runs inside the Worker and could be steered into leaking the binding.
- You need per-agent policy and an audit trail of reads.
- You want outbound calls made server-side so the value never enters the isolate.
[ MIGRATION ]
Moving over in three steps
Most teams keep Cloudflare Workers Secrets for what it is good at and add 1Claw for the agent layer.
- 1Move agent-facing values from wrangler secrets into a 1Claw vault at scoped paths.
- 2Give the Worker's agent its own 1Claw agent identity with a deny-by-default policy.
- 3Convert the agent's outbound fetches to Execution Intents HTTP bindings.
[ FAQ ]
Common questions
Does adding 1Claw hurt Worker latency?
It adds a network round trip that a local binding does not have. For agent-facing credentials that is usually an acceptable trade for scoping and auditability; for hot-path values with no LLM involved, keep the binding.
Can I use 1Claw from a Worker?
Yes, via the SDK or a plain HTTPS call to the Vault API.
What about Cloudflare AI Gateway?
That is a different layer — model routing and caching. See the Cloudflare AI Gateway comparison for how it relates to Shroud.
[ RELATED ]
Other comparisons
[ FREE TIER ] 3 vaults · 50 secrets · 2 agents · 100 signatures/mo
Give agents access, not copies
Store the credential once, scope it per agent, and let the agent act without ever holding it.