[ SHORT ANSWER ]
Turnkey is the stronger embedded wallet infrastructure: verifiable TEE signing, a granular policy engine, and the throughput to provision wallets per end user at scale. Choose 1Claw when the wallets belong to autonomous agents and you want the governance layer included — simulation, spend caps, approval routing, and the agent's API credentials in the same policy model.
This is the wallets-side view of the same trade covered in the agent signing comparison. If you are provisioning wallets for many end users, Turnkey is built for that shape. If you are governing a smaller number of agents that act continuously, 1Claw's per-agent guardrails are the better fit.
[ COMPARISON ]
1Claw vs Turnkey
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 Turnkey when
- You are provisioning wallets for a large end-user base.
- Verifiable TEE attestation per signature is a customer-facing requirement.
- You want the infrastructure primitive and will build your own policy layer.
Use 1Claw when
- The wallets belong to agents rather than users.
- You want guardrails, simulation, and approvals included.
- You need agent credentials and wallets under one audit trail.
[ MIGRATION ]
Moving over in three steps
Most teams keep Turnkey for what it is good at and add 1Claw for the agent layer.
- 1Import existing key material with Key Import, or provision new per-agent keys.
- 2Recreate your Turnkey policies as 1Claw guardrails and approval policies.
- 3Verify in shadow mode before switching enforcement on.
[ FAQ ]
Common questions
How many wallets does 1Claw support?
10 on Free, 10,000 on Pro, 250,000 on Team. If you need more than that at consumer scale, Turnkey is the better fit.
Is this the same as the agent signing comparison?
It is the same vendor viewed from the wallets angle. See the Turnkey agent signing page for the signing-specific view.
Does 1Claw support sub-organisations?
Yes — hierarchical orgs with cryptographic isolation, 10 on Pro and 50 on Team.
[ 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.