Turnkey policy engine for wallets
Turnkey
Turnkey is selling a transaction authorization layer, not just wallet creation. A simple embedded wallet SDK mostly helps an app generate keys and hide seed phrases behind passkeys or social login. Turnkey adds a rules engine in front of signing, so the app can decide exactly who can move funds, where funds can go, which contract calls are allowed, and when extra approvals are required. That makes it usable for consumer wallets, team treasuries, and AI agents with narrowly scoped permissions.
-
The product model is organization based. Developers create a parent organization for the app, then sub organizations for each user or customer, each with its own users, authenticators, wallets, and policies. That structure lets one app run many isolated wallets with different permission sets instead of one global key system.
-
Turnkey policies are evaluated on every request, with deny winning over allow by default. Policies can check approvers and transaction conditions, such as a specific destination address, before the enclave signs. Root quorum can override policies, which makes the system look more like enterprise access control than a retail wallet wrapper.
-
The broader market is moving this way, but mostly from two ends. Privy and Dynamic now offer fine grained embedded wallet policies for app developers, while Fireblocks built policy engines for institutional treasury and approval workflows. Turnkey sits between them, bringing enterprise style controls into API first wallets aimed at consumer apps and automated agents.
The next step is wallets becoming programmable permission containers for software, not just accounts for people. As more apps give backends and AI systems authority to pay, trade, or interact onchain, the winning wallet infrastructure will be the one that can prove exactly what each actor is allowed to do before any signature happens.