Use Zodiac

Zodiac is the operations layer for onchain organizations, built on Safe. Policies control what every actor can do. Simulation shows the result of a transaction before anyone signs. The assets stay in your Safe, under your keys — Zodiac is non-custodial by design.

The four components

Component	What it does
Zodiac App	The interface for onchain operations: connect Safes, define policies, assign members, and coordinate execution. app.zodiac.eco
Policy engine	Enforces permissions onchain with the Roles Modifier. The contract checks every action at execution time — not an offchain service.
Zodiac Pilot	The browser extension. It records actions across dapps, bundles them, simulates the outcome, and executes through your Safe.
Safe	The smart account that holds the assets and executes the transactions.

The path

Four short pages take you from an existing Safe to a delegated, policy-bound operation:

Import a Safe — connect an existing Safe. No contract changes, no migration.
Create a policy — define which actions are allowed, for whom, and under which conditions.
Execute a transaction — build, simulate, and run a transaction within the policy.
Install Pilot — add the browser extension.

Then copy a proven setup from the recipes.

Why teams use it

Simulate before you sign. See the exact token flows and state changes first.
Batch across dapps. Record steps in any interfaces and execute them as one atomic transaction.
Delegate with guardrails. Members execute within the policy, without more signer access. The policy is code, checked onchain, and auditable.
Keep custody. Keys, assets, and control stay with your Safe.

Manage it as code

Teams that prefer version control define the same objects in TypeScript: Safes, policies, members, and permissions as a constellation. See the Developers tab — the Roles quickstart takes about 20 minutes.