Products / All modules

A modular control plane for wallet operations.

Alloy starts with WalletKit and expands into policy, risk, reconciliation, compliance, key orchestration, treasury, and token operations without forcing teams into one custody provider.

Funding-ready thesis: Alloy is not a bundled custodian. It is the provider-neutral operating layer that lets teams adopt only the modules they need while keeping custody strategy portable.
Platform map

Eight modules. One operating model.

WalletKit is the first adoption path. The adjacent modules show how Alloy becomes the system of control across wallet operations.

Launch module

WalletKit

Provider-neutral wallet operations across Fireblocks, BitGo, Copper, Safe, Alloy Mesh, and self-hosted stacks.

Explore
PolicyKit

PolicyKit

Approval rules, role controls, limits, exceptions, and evidence trails.

RiskGuard

RiskGuard

Pre-sign simulation, risk scoring, and transaction decision support.

ReconFlow

ReconFlow

Ledger-ready reconciliation, exports, evidence, and exception handling.

ShieldOS

ShieldOS

KYT, AML, transaction screening, and compliance evidence.

Key control

VaultCore

Signing authorization and key lifecycle orchestration for customer-controlled environments.

Treasury

TreasuryAI

Policy-bounded treasury recommendations, approvals, reporting, and movement controls.

Token ops

TokenForge

Token lifecycle operations, roles, policy gates, distribution controls, and audit trails.

How the modules fit together

Start with WalletKit, then add controls when the workflow demands them.

A funding-facing product hub should make the wedge obvious: customer teams can solve provider portability first, then add policy, risk, reconciliation, and compliance without changing their custody provider.

How the modules fit together

Payment appsBank portalsAI agents
Alloy control plane WalletKitPolicyKitRiskGuardReconFlow
FireblocksBitGoCopperSafe / self-hosted
Audit evidenceFinance exportsCompliance cases
Proof posture

Map your first Alloy module.

Tell us your current provider stack and the workflow you want to control first.

Non-custodial boundary Alloy never holds private keys or customer funds. Providers and customer-controlled stacks keep custody.
Provider-neutral posture Business workflows stay stable even when provider APIs, webhooks, and reporting differ.
Right-sized adoption Teams can start with one module and expand only where operations, audit, or compliance demand it.