Lower adoption risk
Customers can keep current providers and keys while evaluating Alloy's value in product, compliance, finance, and support workflows.
Trust boundary
Alloy is the operating layer above your wallet providers, not a new custodian.
WalletKit phase one is intentionally non-custodial from Alloy's perspective. It standardizes transaction state, policy evidence, reconciliation, and audit workflows above the providers you already use.
In brief: Keep your providers and keys. Move the operating model into Alloy.
What Alloy does
Own the workflow and evidence layer.
Alloy should become the system where product, engineering, compliance, finance, and support agree on wallet operations semantics.
- Connect to existing providers and discover their capabilities.
- Normalize wallet, address, balance, and transaction objects.
- Run policy and risk checks before provider submission.
- Normalize events and support replay.
- Produce reconciliation records and audit evidence.
- Preserve provider-specific escape hatches and raw payloads.
What Alloy does not do in phase one
Do not confuse the control plane with custody or signing.
The first release is not asking customers to transfer trust in keys or live-funds routing to Alloy.
Not a custodian — Alloy does not take possession or control of customer funds.
Not Alloy-controlled signing — signing and custody remain with the underlying provider in phase one.
Not automatic multi-provider routing — phase one preserves control and evidence before introducing deeper execution logic.
Not full accounting replacement — Alloy exports normalized records into existing finance and operations systems.
Why this boundary matters
Phase one should earn trust before it asks for more.
The fastest way to prove value is to reduce provider-specific operating debt while leaving custody with the systems the customer already trusts.
Faster proof of value
Canonical state, replay, reconciliation, and audit evidence are useful before any provider migration or signing change.
Cleaner future expansion
If Alloy becomes trusted as the control plane first, deeper execution surfaces later become a product choice rather than a leap of faith.
Readiness signals
Who should book a meeting now.
The best current fit is a team with one provider already live and real workflow pain outside that provider's console.
- Adding a second provider or preparing a migration.
- Needing policy and audit evidence outside provider-native tooling.
- Reconciling transactions and balances across providers or chains.
- Trying to keep customer-facing state stable while provider logic changes underneath.
Current status
Trust means being explicit about what is live, validating, and planned.
Alloy should talk about design-partner validation and product scope precisely rather than implying bank-grade breadth before it exists.
- Live narrative: provider-neutral wallet operations control plane, non-custodial boundary, WalletKit-first platform story.
- Validating now: second-provider workflows, policy evidence, event replay, reconciliation exports, and first-call design-partner fit.
- Future scope: broader provider coverage, deeper execution surfaces, private deployment demands, and later AI-agent expansion.
Next step
Bring the real workflow you need to keep stable.
The best conversation is a workflow mapping session: provider objects, transaction states, approvals, webhook behavior, reconciliation, audit evidence, and what breaks when provider assumptions leak into your systems.
Request demo
Need the product surface too? Visit WalletKit or the comparison page.