Connect your providers
Plug in Fireblocks, BitGo, Copper, or Safe. Alloy maps their objects into one model — no migration required.
Non-custodial · Provider-neutral · API-first
The control plane above your wallet providers.
One layer above Fireblocks, BitGo, Copper, and Safe for operations, policy, risk, reconciliation, and compliance — without moving custody.
Zero custody risk 5+ providers supported 8 modular components Audit-ready from day one
Alloy Console Control plane
Providers
Transactions
Policy
Risk
Audit
Provider operations
One operating model for accounts, signing, transaction state, controls, and reconciliation.
FireblocksConnected
BitGoConnected
Safe / EVMConnected
Transaction operationsLast 24h
USDC payout batch
Fireblocks intent normalized
Approved Fireblocks intent normalized
Provider failover test
BitGo route requires review
Review BitGo route requires review
Architecture
One layer above your custody providers.
Your providers handle signing and key management. Alloy adds the operating layer — without touching private keys.
Alloy Control Plane Non-custodial Operations · Policy · Risk · Reconciliation · Audit
+ Self-hosted wallets Alloy never holds private keys. Your providers keep custody.
0 keys heldAlloy never takes custody of private keys or customer funds
5+ providersFireblocks, BitGo, Copper, Safe, and self-hosted wallets in one model
8 modulesWalletKit, PolicyKit, RiskGuard, ShieldOS, ReconFlow, and more
API-firstEvery operation is a deterministic API call with structured evidence
The layer above
Your wallet provider solves signing. Who solves everything else?
Adding a second provider, running a compliance review, or closing the books exposes it: every wallet object, approval trail, webhook, and ledger export is locked to one provider's model. Alloy is the operating layer above.
What breaks after provider one
Vendor lock-inSwitching providers means rewriting business processes, not just swapping an API.
Audit gapsPolicy decisions and approval evidence are trapped inside one provider's console.
Reconciliation painFinance teams stitch together CSVs, support tickets, and manual spreadsheets every close.
Compliance riskNo single source of truth for what controls applied before a transaction moved.
Operating model
Keep your providers. Add the layer above.
Provider-specific APIs stay available. Alloy adds the shared operating layer for engineering, risk, compliance, and finance.
Run one operating model
Every team — engineering, compliance, finance, support — sees the same wallets, transactions, and evidence.
Add controls as you grow
Layer on policy, risk scoring, reconciliation, and audit modules. Switch or add providers without touching business logic.
Who needs this first
Built for teams that already move real money.
If you manage custody providers, answer to auditors, and close the books every month — Alloy is for you.
Stablecoin payment fintechs
Add a second provider, expand to new geographies, or fix reconciliation — without rebuilding your operating model from scratch.
Explore solution →Banks and institutions
Keep custody with approved providers. Get vendor-risk control, governance evidence, and audit trails independent of any single platform.
Explore solution →AI-agent builders
Give autonomous agents bounded spending authority, real-time risk checks, and auditable receipts — across any wallet provider.
Explore solution →Why Alloy
What sits above the custody layer?
Every provider solves signing. None of them solve running multiple providers, satisfying auditors, and closing the books. Alloy does.
No vendor lock-in
Switch or add providers without rewriting business processes. One model works across Fireblocks, BitGo, Copper, Safe, and self-hosted stacks.
Zero custody risk
Alloy never touches private keys. Your providers keep custody — you get a clean regulatory boundary and simpler compliance.
Pay for what you use
Start with WalletKit alone. Add policy, risk, reconciliation, or compliance modules only when your operations need them.
Audit-ready from day one
Every operation produces structured evidence — policy decisions, approval chains, and reconciliation artifacts. Built for compliance teams, not just engineers.
FAQ
Common questions.
Does Alloy custody funds?▼
No. Alloy is non-custodial software. Customers keep custody with their providers or self-hosted stack. Alloy never holds private keys — that clean separation is by design.
Which providers does WalletKit target first?▼
The initial set is Fireblocks, BitGo, Copper, and Safe or self-hosted EVM wallets. Broader provider support expands based on customer demand.
How is Alloy different from buying one bundled custody platform?▼
Alloy is the provider-neutral operating layer above wallet and custody providers. One bundled platform locks you in. Alloy gives you portability, normalized state, policy evidence, and reconciliation across every provider you run.
What does "non-custodial control plane" mean?▼
A control plane normalizes how you manage operations — wallet objects, transaction state, approvals, policy, and audit trails — without ever holding the underlying assets. Think of it as the operating system for wallet operations, not the vault.
Can I add a second custody provider without re-architecting?▼
That is the core use case. WalletKit normalizes wallet and transaction objects across providers. Adding a second or third provider is a configuration change, not a business-process rewrite.
How does Alloy handle compliance and audit evidence?▼
Every operation produces structured evidence: policy decisions, risk scores, approval chains, and reconciliation artifacts. ShieldOS adds KYT, AML screening, and compliance reporting as a module you activate when needed.
Ready to simplify your digital asset operations?
Tell us your provider stack and what's breaking. We'll map how Alloy fits above it.
✓ No custody risk ✓ API-first integration ✓ Works with your existing stack
Prefer email? hello@alloy.build