# How Raven works

> Where each part of Raven runs, what crosses between them, and why your keys never leave your browser unlocked.

Source: https://ravenwallet.pro/docs/how-it-works

## In one picture

Raven has three places. Your browser holds your keys and does the signing. Raven’s server signs you in, keeps a locked copy of your vault and passes things on. Outside are Solana itself and the services Raven uses for swaps and private moves.

- The page (what you see and tap) → sign in → Sign-in (Google or email)
- Key worker (keys, plans, signing) → signed → Network relay (reads and sends) → sent → Solana (the chain)
- Vault (locked, this device) → locked → Vault copy (locked, cannot open)
- Swap check (every route) ← route ← Swap relay (asks for routes) ← route ← Jupiter (routes and prices)
- Order check (before paying) ← order ← Order relay (in Raven’s name) ← order ← Husher (private orders)
- AI rules (decide each ask) ← ask ← AI relay (carries asks) ← ask ← Your AI (Claude, ChatGPT, Cursor)

Keys exist unlocked in one place only, the key worker. What leaves your browser is locked or already signed, and what comes back is checked there before it counts.

## Your browser

Everything that matters happens here.

- **The page** is what you see: your wallets, the moves, the reviews. It never holds a key.
- **The key worker** is a separate, walled-off part of the same tab. Your keys live only inside it while Raven is unlocked. It builds each transaction from a plan, checks it and signs it.
- **The vault** is your keys and settings, locked, kept in the browser’s own storage.

## Raven’s server

The server does the jobs a browser cannot do alone, and none of them needs a key.

| Part | What it does |
|---|---|
| Sign-in | Finds your account with Google or your email and a proof made from your password |
| Vault copy | Keeps the same locked vault, so it opens on your other devices |
| Network relay | Passes reads and signed transactions to Solana |
| Swap relay | Asks Jupiter for a route and hands it back to be checked |
| Order relay | Places private orders with Husher in Raven’s name |
| AI relay | Carries asks from an AI you connected to your open Raven |

## The life of a move

1. **You plan it.** Pick the move, the wallets and the amounts.
2. **Your browser works it out.** The key worker turns the plan into transactions from your balances right now.
3. **You review it.** Every amount, wallet and fee, before anything signs.
4. **It is tried first.** Each transaction is run against the chain without being sent.
5. **It is signed and sent.** The key worker signs; the network relay passes the signed bytes to Solana.
6. **It is followed.** Raven watches each transaction until it lands, then writes the receipt.

## Under the hood

- **One way in for keys**: The page and the key worker talk in short, named requests. The page gets back addresses, numbers and previews, never a key. The worker will not sign a transaction handed to it; it builds its own from a plan. The one exception is a site’s request in [Raven for Chrome](https://ravenwallet.pro/docs/chrome), after its checks.
- **Signed means final**: A signed transaction cannot be changed without breaking its signature, so the relay can pass it on but cannot alter it.
- **Nothing to steal on the server**: The server holds a vault it cannot open, a sign-in proof that is not your password, and, only with an AI connected, your wallet list. See [What our server sees](https://ravenwallet.pro/docs/server).
- **Checked on the way back**: Swap routes and private orders come back through the server and are checked in your browser before anything is paid. See [Checks before you sign](https://ravenwallet.pro/docs/checks).