Compare control
Who can change the rules?
Hardware protects execution. Control depends on who can change permissions, approve software, and stop access. See how Lit and other providers handle each decision.
Wallet infrastructure
Private compute & AI
How we make these comparisons
Published by Lit Protocol. Reviewed September 16, 2026. We compare operator powers using primary documentation and identified source snapshots. Our conclusions are architectural assessments, not security audits, exploit findings, or legal classifications of custody.
Wallets and confidential containers
The wallet comparisons cover Chipotle in ChainSecured mode. A customer-controlled wallet administers account permissions on Base, and the attested runtime enforces them. They do not cover Lit’s legacy MPC network or API-mode accounts. Inspect the permission check.
The compute comparisons cover Docker containers with on-chain approval of code and network policy. They do not use the wallet account or Lit Actions API as the AI deployment interface. Read the AI deployment guide.
On-chain governance
Lit separates deployment from approval. The key-management system checks attested measurements against contract rules before releasing runtime keys. An operator cannot authorize new code simply by deploying it. Previously approved releases remain allowed until revoked. Runtime governance.
Account permissions and protocol upgrades have separate authorization rules. Chipotle’s account contracts support upgrades, so a review should examine both the permission checks and how those checks can change. These comparisons describe the method; deployment-specific approval policies are evaluated separately. Upgrade source; verification guide.
Evidence and limits
We distinguish hardware protection from release authority, and permission to sign from the ability to recover without a provider. All deployments retain dependencies on software correctness, hardware trust roots, and availability. Lit also depends on chain state and key infrastructure. An omitted feature in a document is not proof that a product lacks it.
A SOC 2 report evaluates organizational controls; attestation provides evidence of a measured runtime. Neither alone establishes that approved code is safe. SOC 2 scope; attestation.
Contact Lit to confirm model and hardware support for your application. These comparisons do not benchmark throughput or latency. Each AI deployment needs its own rules for code, credentials, and outputs.