Limits
Amount, asset, destination, team, and provider-level boundaries.
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.
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
Policy inputsRoleAmountAssetCounterparty
PolicyKit decision layerLimitsApprovalsExceptionsReceipts
Execution boundaryWalletKitCustody providersCustomer wallets
Evidence outputsApproval trailDenial reasonAudit record
Funding narrative
The wedge is custody portability; the expansion is policy portability.
Approvals
Human approval state and quorum evidence before release.
Exceptions
Reason-coded overrides with audit context and expiry.
Provider fit
Provider-specific constraints remain visible when a rule cannot be applied uniformly.
Decision lifecycle
Every decision should be understandable after the fact.
Classify
Tag the operation by asset, amount, destination, user, team, corridor, and provider.
Evaluate
Apply role, limit, jurisdiction, approval, and exception rules before provider submission.
Escalate
Route unclear or high-risk operations to humans with the context needed to decide.
Attach
Store the policy outcome with the WalletKit transaction record for audit and replay.
Evidence
Proof the buyer can inspect.
Every route keeps Alloy's public story grounded in operating records, custody boundaries, and right-sized modules.
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