Design partner
Workflow mapping
Early access
For teams validating one provider-neutral wallet operations workflow.
- Provider and workflow map
- WalletKit fit review
- Control boundary notes
- Implementation sequence
Pricing
Start with the workflow, then add the modules that prove control.
Alloy packaging is being validated with design partners. The intended model is modular and right-sized: begin with WalletKit or a workflow map, then attach policy, risk, reconciliation, and compliance controls when they create operating proof.
Stage note: Pricing is not a public rate card yet. We are using design-partner conversations to validate the right package, deployment boundary, and success metric.
Packages
Three ways to start.
Recommended start
WalletKit wedge
Custom
For teams with a live provider and a concrete second-provider, audit, or reconciliation trigger.
- WalletKit operating records
- Provider state normalization
- Policy and risk attachment points
- Finance evidence path
Expansion
Control-plane modules
Custom
For regulated teams adding policy, risk, reconciliation, compliance, or authority controls.
- Module sequence review
- Customer-controlled deployment boundary
- Audit and evidence design
- Architecture review
Buyer questions
The right commercial shape depends on control-plane scope.
For now, Alloy conversations should answer which workflow is urgent, which provider boundary is real, and which module turns that pain into reviewable evidence.
Is there a free tier?
During design-partner validation, Alloy is focused on workflow fit rather than a self-serve free tier.
Do I need to move custody?
No. Alloy is non-custodial and sits above customer-approved wallet and custody infrastructure.
Can we start with one module?
Yes. The intended adoption path starts with WalletKit or one urgent workflow, then adds modules as the operating model matures.
Scope map
A good package maps to evidence, not seat count alone.
Pricing conversations should make the operating surface precise enough for both a design partner and an investor diligence reader.
Workflow trigger
Second provider, migration, close pain, compliance audit, bank procurement, or AI-agent authority.
Control boundary
Which custody providers, customer systems, roles, approvals, and downstream evidence stores stay in scope.
Module sequence
WalletKit first when provider state is the wedge; PolicyKit, RiskGuard, ReconFlow, ShieldOS, VaultCore, TreasuryAI, or TokenForge attach when proof requires them.
Success metric
One measurable operating outcome: fewer manual close exceptions, clearer approval evidence, cleaner provider migration path, or faster workflow review.