Product / PolicyKit

Policy decisions that travel with every wallet operation.

PolicyKit turns approval rules, limits, roles, and exceptions into portable decision evidence across wallet providers.

Join design partnersView products
Operating proof: Use PolicyKit when the business rule cannot live inside one provider console or one internal script.
Product console

Rules are modeled as operating state, not buried in provider settings.

Teams can express thresholds, roles, maker-checker flows, and exception handling once, then apply those decisions to every connected wallet provider.

Operating boundary

Customer systemsProduct flowsFinance closeCompliance review
Alloy control planeWalletKitPolicyKitRiskGuardReconFlow
Execution boundaryCustody providersCustomer cloudAudit evidence
Funding narrative

The wedge is custody portability; the expansion is policy portability.

Limits

Amount, asset, destination, team, and provider-level boundaries.

Approvals

Human approval state and quorum evidence before release.

Exceptions

Reason-coded overrides with audit context and expiry.

Evidence

Proof the buyer can inspect.

Every route keeps Alloy's public story grounded in operating records, custody boundaries, and right-sized modules.

Decision receiptsEach approval outcome is attached to the operation record.
Provider-neutral rulesRules are designed above Fireblocks, BitGo, Copper, Safe, Alloy Mesh, and self-hosted stacks.
Human overrideEscalations stay visible instead of disappearing into chat or tickets.
Next step

Bring your current provider stack.

We will map the first workflow Alloy should stabilize, the custody boundary, and the modules that create evidence.

Join design partners

Prefer email? hello@alloy.build