The verifiable integration layer for finance.

Deploy software verifiably to compute and sign across DeFi, centralized exchanges, and more.

$400M+ secured·1.6M+ wallets·$135M+ volume
READ
Any source. APIs, oracles, any chain.
DECIDE & SIGN
Your policy runs in confidential hardware. Keys sign only what it allows.
SETTLE
Any chain. EVM, Solana, Bitcoin, Cosmos.
Building on Lit
RelayEmblem VaultBeacon ProtocolTriaGeniusGVNR
Don’t trust. Verify.

Other wallet providers say non-custodial.Lit proves non-custodial.

Does your provider prove it?

Blind

Keys are generated and used only inside sealed TEEs. No operator, including Lit, can see or extract them.

Bound

A key’s authority is on-chain state on Base. It signs only what an immutable, content-addressed policy permits. Code, not an admin switch.

Verifiable

Every signature is a hardware-attested record, hardened by Proof of Cloud. Confirm the exact code running in the enclave.

There is no trusted operator. We run the network, but we can’t silently change what it runs — every upgrade is whitelisted on-chain by a multisig, open on Base.

Confidential compute

Run any workload no one can see in.

Signing is just the start. Spin up a confidential microVM and run any code inside the same attested hardware that guards the keys. Your logic and data stay private from every operator — and every run leaves hardware-backed proof of exactly what ran.

  • Any workload, not just signing
  • Private from every operator, including us
  • Hardware-attested: prove what ran

Live with design partners — onboarding is hands-on for now.

confidential microVM sealed
$ run ./settlement-engine
booting Intel TDX enclave
loading code · hash measured on-chain
inputs sealed · no operator can read
running your workload
✓ attested · proof of exactly what ran
Managed, not locked in

We run the infrastructure. You just start.

No managed sandbox to lock you in. Deploy in your own cloud or on-premise — your infrastructure, your keys, your governance — with the same attested guarantees wherever it runs.

Prefer to run it yourself?
AWS
Google Cloud
On-prem
What it looks like

One file. Reads, computes, signs across chains.

A Lit Action is JavaScript that runs inside the network’s TEE. Deploy it once. Sign with a wallet bound to the action code itself, or with one you control through your own on-chain governance.

rebalance.action.ts
// Inside a Lit Action — runs in a chain-secured TEE

// Read off-chain
const price = await fetch(
  "https://api.coinbase.com/v2/prices/ETH-USD/spot"
).then(r => r.json());

// Read on-chain (Base)
const base = new ethers.providers.JsonRpcProvider(BASE_RPC);
const vault = new ethers.Contract(vaultAddress, vaultAbi, base);
const ratio = await vault.currentRatio();

// Decide, then sign + broadcast on Arbitrum
if (Number(price.data.amount) * Number(ratio) < threshold) {
  const pk = await Lit.Actions.getLitActionPrivateKey();
  const arb = new ethers.providers.JsonRpcProvider(ARB_RPC);
  const wallet = new ethers.Wallet(pk, arb);
  const hook = new ethers.Contract(hookAddress, hookAbi, wallet);
  const tx = await hook.rebalance();
  Lit.Actions.setResponse({ response: tx.hash });
}
Encrypted hardware, governed on-chain

Speed of a backend, trust of a contract.

Your code runs in hardware, so it moves at backend speed. Its authority lives on-chain: smart contracts on Base decide which keys it can use and which code is allowed to run, with every change auditable on Basescan and impossible for any one party to push alone.

Latency
Sub-second signing
Auditability
Code hash on-chain
Pricing
$0.01/sec, less on annual plans
Surface
Any HTTP, any chain

Read. Compute. Write.
Anywhere.

One programmable runtime for everything that has to happen between an event and a signed action.