Turnkey's most recent disclosed financing was a $12.5M strategic investment announced on May 14, 2026, bringing total funding to over $65M.

Prior to that, Turnkey raised a $30M Series B on June 9, 2025, led by Sequoia Capital, with participation from Bain Capital Crypto, Lightspeed Faction, Galaxy Ventures, Variant, Coinbase Ventures, Wintermute Ventures, Alchemy, Figment Capital, and Mirana Ventures.

Before the Series B, Turnkey raised a $15M Series A on April 23, 2024. The company launched out of stealth on March 21, 2023 with a $7.5M seed round. Total primary equity raised across all rounds stands at over $65M.

Turnkey provides developer infrastructure for wallet creation, private key management, transaction signing, and access control. Instead of having the application handle raw cryptographic keys, it serves as the hardened key layer underneath the product, so developers do not need to build enclave architecture, policy engines, or wallet recovery flows from scratch.

A developer integrating Turnkey creates a parent organization representing the application, then provisions sub-organizations, one per end user or one per business customer, each with its own wallets, authenticators, and policies. When a user signs in with a passkey, email, OAuth login, or biometric, Turnkey maps that authentication event to wallet actions based on rules the developer defines. The user does not interact with a raw private key or seed phrase, they use a wallet embedded in the app.

The policy engine distinguishes Turnkey from simpler wallet SDKs. Before the enclave acts, each signing request is evaluated against developer-defined rules that can constrain recipient address, contract, function selector, chain, transaction value, or approval quorum. That supports consumer onboarding, business wallets with multi-user approval flows, and automated systems where a backend or AI agent needs bounded transaction authority without holding a raw key.

On security, sensitive operations run inside AWS Nitro Enclaves, with signing latency around 50–100ms. Turnkey exposes a security model built around remote attestation, reproducible builds, and its QuorumOS unikernel environment, so customers can cryptographically verify that a legitimate enclave is running the expected software. Turnkey Verifiable Cloud, in private beta as of May 2026, extends this toward a generalized verifiable compute platform for sensitive workflows.

Beyond signing, Turnkey also handles transaction construction, broadcast, nonce management, monitoring, and gas sponsorship on supported EVM chains and Solana, reducing what would otherwise be a multi-vendor operational stack to a single API surface.

Turnkey is a B2B developer infrastructure company that sells a managed control plane for cryptographic key operations. Customers integrate via API and SDK instead of self-hosting, which makes Turnkey's enclave infrastructure, policy runtime, and signing services persistent dependencies inside the customer's product.

Monetization is usage-based and anchored to signatures. The free tier covers 25 signatures per month; self-serve runs at $0.10 per signature; Pro drops to $0.05; and enterprise contracts can reach as low as $0.0015 with custom annual minimums and premium features including SLAs, dedicated support, custom email domains, SMS authentication, and enterprise rate limits. The pricing curve lowers per-unit costs for high-volume customers while keeping adoption costs near zero for developers testing the product.

The cost structure is software-like. Turnkey does not manually approve transactions or manage keys through human operations, the core runtime is policy automation and enclave compute. Fixed costs include cloud and enclave infrastructure, chain integration maintenance, security and attestation engineering, and SDK support. Once those are in place, incremental usage scales more like API traffic than a service business, which is favorable for gross margins relative to custody or compliance-heavy competitors.

Go-to-market follows a standard infrastructure wedge: developers start on the free or self-serve tier, successful products move to higher-volume production, and enterprise controls, support, and broader product modules create upsell. Because Turnkey becomes the system of record for wallet permissions and signing authority inside a customer's application, replacing it would require rebuilding authentication, policy logic, signing paths, and customer-facing recovery flows at the same time, creating switching costs once integration is deep.

Expansion revenue comes from adding use cases on top of the same core primitives. A consumer trading app that starts with embedded wallets can later adopt company wallets for treasury automation, stablecoin payment orchestration, and eventually Verifiable Cloud for compliance-sensitive workflows, increasing revenue per customer without fragmenting Turnkey's engineering investment.

Turnkey competes in a wallet infrastructure market that has consolidated around bundled platforms. The core tension is between Turnkey's infrastructure-primitive positioning and rivals expanding upward into full-service crypto rails.

The clearest competitive shift since 2025 has been vertical integration by larger players acquiring developer-facing wallet infrastructure.

Fireblocks acquired Dynamic in October 2025, combining Dynamic's embedded wallet and onboarding layer with Fireblocks' institutional custody, treasury, and compliance stack. The combined entity can now compete from both directions: enterprise buyers get Dynamic-style developer UX through a Fireblocks procurement relationship, while developers that want Dynamic's experience also get Fireblocks' security and compliance stack. This makes Fireblocks a threat across Turnkey's customer base, particularly where buyers want wallet infrastructure bundled with settlement, tokenization, or regulated custody.

Stripe acquired Privy in July 2025 and now markets the combined Stripe, Bridge, and Privy stack for stablecoin, agent, and cross-border product workflows. For developers already standardizing on Stripe, that bundle makes Privy the default option for embedded wallets, especially in payment-adjacent use cases where wallets are one layer in a broader financial workflow. Turnkey is most exposed in the stablecoin payments segment, where it has been growing fastest.

Privy, Coinbase CDP, and Crossmint compete by offering wallet creation plus onboarding, recovery, smart accounts, payments, compliance, and fiat rails in a single package.

Coinbase CDP is a serious threat because it bundles wallet infrastructure into Coinbase's broader distribution and compliance stack, with onramps, swaps, smart accounts, and gas sponsorship available under one billing relationship. For regulated fintechs or developers building on Base, CDP can be sufficient on wallet security while winning on brand trust and adjacent services. Turnkey's counter is ecosystem neutrality: it does not channel builders into one platform's roadmap, which matters most to customers that want to keep auth, account abstraction, payments, and compliance decisions modular.

Crossmint competes by going broader, combining wallets with onramps, exchanges, transfers, and a regulatory wrapper that includes MiCA authorization as of January 2026. That makes Crossmint a material threat in EU-facing stablecoin and fintech deployments, where procurement increasingly favors a single regulated vendor over a best-of-breed stack.

Magic and Web3Auth remain relevant at the lower end of the market, where teams buy embedded wallets primarily as an onboarding feature rather than as security infrastructure. Magic highlights 53M+ wallets and 200K developers, with a value proposition centered on the fastest path to embedded wallet UX rather than on signing infrastructure. These players pressure Turnkey among teams that lack cryptography depth or prioritize time-to-ship over policy control.

Sequence occupies a similar niche in gaming, with embedded wallets designed around social and guest login, native game UX, and Unity and Unreal engine integrations. For studios prioritizing game-native flows, Sequence's domain specificity can be more compelling than Turnkey's generalized infrastructure. Openfort is an emerging open-source and self-hostable threat, explicitly selling against vendor lock-in with an open-source key-management component, a meaningful alternative for security or compliance teams that prefer operational sovereignty over SaaS assurance.

Turnkey's expansion logic is moving from a narrow wallet signing layer into a broader secure execution and control plane for workflows where cryptographic assurance matters, including stablecoin payments, AI-agent finance, and, over time, general-purpose verifiable compute.

The stablecoin payments market is the nearest TAM expansion vector, with stablecoin market capitalization reaching $317B in April 2026, up more than 50% since early 2025, and B2B settlement as the lead growth segment.

Turnkey's payment orchestration product, partnerships with Mural Pay, Flutterwave, and Lightspark, and its $100B+ stablecoin volume milestone target infrastructure spend from PSPs, cross-border platforms, treasury software vendors, and fintechs that want programmable stablecoin accounts without building key management themselves. The same market dynamic is driving consolidation, including Stripe's acquisition of Bridge, Ripple's acquisition of Rail, Mastercard's acquisition of BVNK, and Kraken's acquisition of Reap. Fintechs assembling stablecoin stacks as modular best-of-breed layers fit the customer profile Turnkey is targeting.

Agentic wallets are emerging as a distinct product category as AI systems need bounded transaction authority rather than retail wallet UX. Turnkey's policy engine, API-native access, and sub-100ms signing fit the requirement that an agent can act autonomously within tightly scoped rules without holding a raw private key.

The opportunity is to provide signing, permissions, and audit infrastructure for machine actors across AI-agent frameworks, API marketplaces, and trading infrastructure. Turnkey is already publishing around agent identity standards like ERC-8004 and x402, placing it closer to the protocol layer of agentic commerce than a wallet SDK. If autonomous software becomes a durable category for financial transactions, the policy-controlled delegation model Turnkey already ships maps to that control plane.

Turnkey Verifiable Cloud, in private beta as of May 2026, expands the addressable market from crypto-native wallet infrastructure into high-trust workflows that benefit from attested secure execution, including transaction processing, compliance workflows, attested data services, privacy-preserving computation, and multi-step financial orchestration.

Verifiability is becoming a procurement requirement rather than a differentiator in regulated fintech, institutional stablecoin systems, and AI-agent accountability frameworks. By turning remote attestation, reproducible builds, and cryptographic proofs into a platform product, Turnkey can target infrastructure spend from buyers that need provable controls rather than vendor assurances, a wedge that supports enterprise pricing and opens distribution beyond the crypto-native developer base.

Security concentration: Turnkey's value proposition depends on the integrity of its enclave-based signing infrastructure, so a serious exploit, outage, or credibility issue in its attestation and verifiability stack would damage product trust, weaken the enterprise pipeline, and erode the case for Verifiable Cloud across every vertical it serves.

Bundling pressure: As Stripe absorbs Privy, Fireblocks absorbs Dynamic, and Coinbase CDP bundles wallets with onramps and smart accounts, Turnkey faces the risk of being reduced to a component vendor while larger platforms own the customer relationship through bundled go-to-market, particularly in the stablecoin payments segment where its growth is fastest and where buyers increasingly favor single-vendor regulated stacks.

Payments compliance creep: Turnkey's expansion into stablecoin treasury, cross-border settlement, and fintech infrastructure pushes it into workflows where counterparties have rising expectations around custody models, jurisdictional requirements, and failure handling, increasing regulatory and operational surface area faster than the company's infrastructure-primitive positioning is designed to absorb.