Integrations
One adapter network above custody, wallets, ledgers, and review systems.
Alloy’s integration story is provider-neutral: normalize wallet providers, preserve escape hatches, and connect downstream evidence to finance, risk, and compliance workflows.
Status language: Target, planned, and validating labels avoid over-claiming while showing the intended adapter architecture.
Decision matrix
Coverage is described by capability, not by invented partnership claims.
Operating boundary
Customer systemsProduct flowsFinance closeCompliance review
Alloy control planeWalletKitPolicyKitRiskGuardReconFlow
Execution boundaryCustody providersCustomer cloudAudit evidence
Lifecycle
Adapters should expose what they can and cannot do.
Alloy normalizes common operating state while keeping provider-specific capabilities visible for engineering teams.
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