Get in touch

Your Safe multisigs, private and verified.

Kagi is the control plane for your Safes, on your own infrastructure. Pending transactions stay private until you choose to publish them, and each one is re-checked against the chain before anyone signs.

Treasury0xd9b9…Fb0C 3 of 5 to signPrivate network

Queue

Private to your network·not published

Needs your signature 1

Ethereum #419Next Pause Lending PoolPrivateProposed by Bruno Silva 0 of 3 signed now

Waiting on others 3

Base #92Next Send 250,000 USDC to PayrollYou signed·Waiting on 2 more 1 of 3 signed 3 h
Arbitrum #78Next Replace owner Frank Moreau with Erin ParkOwner changeWaiting on 1 more 2 of 3 signed 1 d
Ethereum #420After #419 Enable Delay module, 24 h cooldownModule changeProposed by Chiara Rossi 1 of 3 signed 2 d
Illustrative example. Names, addresses and hashes are not real.

Works with the Safes you already have. No migration, no new contracts.

  • Safe 1.3.0 and later
  • Ethereum
  • Gnosis
  • Base
  • Arbitrum
  • Optimism

Features

Everything Safe can do, without the exposure.

Funds stay in the Safes you already hold, under the same custody. Kagi gives your team a private, verified way to operate them.

A private queue

Proposals and signatures stay inside your network. Your team sees the queue; the public doesn't. Publishing to Safe's service is always a deliberate step.

Checked before every signature

Kagi re-reads the Safe at a pinned block, recomputes the hash and refuses known attack patterns. Then owners compare the full hash on their devices.

The wallets you already use

Owners sign full typed data in the browser, with their usual browser or hardware wallet. No files to pass around. Contract owners sign on-chain.

Simulation on your node

See balance changes, events and any change to owners or modules before anyone signs. No third-party simulator. If a simulation can't run, Kagi says so. It never shows a pass.

Independent of any vendor

No vendor account and no hosted backend. Kagi keeps working as long as your infrastructure does, whatever happens to anyone else's interface.

Policy controls, built on Safe Coming

Safe's Roles, Delay and guards can already express freezers and risk stewards. Kagi will help you set them up, read them in plain language and test them before they go live.

How it works

Three things you already own.

Kagi sits between your team and the chain, and trusts neither itself nor any RPC for integrity. Every value is checked where it matters: against the chain, and on the signer's device.

  1. Your infrastructure

    One binary in an environment you control, inside your private network or behind HTTPS with passkey sign-in. It holds pending transactions and signatures, never owner keys.

  2. Your node

    Owners, balances, nonces and history are read from your own RPC at a pinned block, and simulations run there too. A chain without a node shows as unread, never as empty.

  3. Your wallet

    Owners sign with the wallet they already use, on their own device. The hash it shows is the hash Kagi computed from the chain.

OptionalSafe's Transaction Service. Import your pending transactions when you switch over. Publish to it only when you choose.

Security

Trust nothing in the middle.

The largest multisig losses began with a compromised interface and a hash nobody could check. Kagi assumes every layer in between can be wrong, itself included, and checks each value against the chain and the signer's device.

  1. 01

    Verified at a pinned block

    Before any signature, Kagi re-reads the Safe and recomputes the hash from the decoded call. Status is derived from the chain, never stored.

  2. 02

    Full values, never truncated

    Addresses, hashes and calldata appear in full on every review and signing screen, grouped the way your device shows them.

  3. 03

    Hard blocks, not hints

    Delegatecall to unknown code, gas-refund tricks and a second transaction at an already-signed nonce are refused outright.

  4. 04

    No calls home

    No telemetry and no third-party requests at runtime. Kagi talks only to the nodes and services you configure. When a check can't run, it stops and says why.

  5. 05

    Agents propose, owners sign

    Automations and agent keys can draft and review transactions. Only owners sign.

  6. 06

    A second opinion

    The Kagi CLI re-checks the same values on a separate machine, with a hardware wallet, for Safes that need it.

Who it's for

For teams that move real value.

Built for the moments when a pending transaction is sensitive in itself: an emergency pause, a treasury move, a change of owners.

EthereumPause Lending Pool#419

Protocols and DAOs

Pause a pool, rotate a key or ship an upgrade without announcing it in a public queue first.

BaseSend 250,000 USDC to Payroll#92

Treasuries

Payments, rebalancing and grants in plain language, with exact amounts, a shared address book and one view across chains.

ArbitrumAdd owner Erin Park#78

Institutions and funds

Runs inside your perimeter, keeps an append-only record of every proposal and signature, and alerts you when a guard or module changes.

Keep your Safes in your control.

Tell us how your team runs its Safes. We'll help you set Kagi up on your own infrastructure.