Buyer guide
Custody portability
How to evaluate provider lock-in, transaction state, policy evidence, and reconciliation before a second provider becomes urgent.
Best for: CTOs, product leads, compliance, finance
Open guideResources
Evaluate wallet operations before provider lock-in hardens.
Use these guides to map custody portability, WalletKit workflow shape, provider state, policy evidence, reconciliation, and audit boundaries in plain operational terms.
Funding-ready proof: The resource hub connects Alloy's product story to real buyer questions without implying customer logos, public certifications, or finished capabilities that are still design-partner scoped.
Guides
Start with the operating question.
Workflow guide
WalletKit workflows
A practical map for turning provider events, approvals, risk checks, and finance close into one WalletKit operating record.
Best for: Payments, operations, engineering
Open guideEvaluation routes
Move from reading to decision support.
Each route answers a different buyer question while preserving Alloy's non-custodial and provider-neutral boundary.
Product proof
Start with the WalletKit console view, adapter status, transaction state, and non-custodial boundary.
Open routeBuyer triggers
Route by second-provider, stablecoin launch, bank controls, agent authority, or reconciliation pain.
Open routeDecision support
Compare bundled custody platforms, embedded wallet APIs, orchestration tools, and Alloy.
Open routeDeveloper path
Review API shape, docs, webhook semantics, and sandbox/design-partner access.
Open routeNext step
Bring one workflow, provider stack, and trigger.
Alloy can map where WalletKit should normalize state first and which adjacent modules create reviewable proof.
Join design partners
Useful inputs: current provider, second-provider trigger, approval flow, webhooks, and close process.