Components
Frontend, gateway, and node responsibilities
HypeSafe has three product components. They work together as one multisig workflow, but each one has a narrow responsibility.
Responsibility Map
| Component | Main job | Does not do |
|---|---|---|
safe-frontend | Human workspace for wallet connection, account management, proposal review, approval signing, and leader execution. | It does not act as the source of truth for task payloads or approval state. |
safe-gateway | Keyless coordination API for sessions, accounts, templates, signing payloads, signature verification, approval tallying, and history. | It does not hold private keys, sign, or take custody. |
safe-node | Optional self-hosted signer and risk-control node for local automated approval and leader execution. | It does not replace gateway verification or bypass the multisig threshold. |
How They Work Together
The frontend and node both use the gateway API. The gateway provides the canonical task view and signing payloads. Signatures submitted by wallets or nodes are verified the same way before they count toward the threshold.
Once enough approvals are collected, the leader executes the multisig action. That can be a human leader in the frontend or a leader node running under local policy.
Why the split matters
The split keeps authority close to the signer. The frontend makes intent visible to humans, the gateway coordinates shared state, and the node lets an operator enforce local policy without asking the gateway to hold keys.