Enterprise agreements
An agreement built around your deployment.
Align the commercial arrangement with how your business plans to deploy and operate WalletD. Discuss licensing, delivery, support and customization together so ownership and costs are clear.
Discuss your requirements01
Define the license scope
Write down how the software will be used, by which entities and in which environments. Flexible terms still need a clear written scope.
- Confirm permitted use, environments and organizational coverage.
- Clarify rights for custom work and third-party dependencies.
- Agree renewal, termination and transition provisions.
02
Make service responsibilities explicit
Separate software rights from the work required to deploy and maintain the system. Each engagement should identify included services and exclusions.
- Specify deployment and integration deliverables.
- Document support coverage and change-request handling.
- Identify customer-side infrastructure and provider costs.
03
Prepare a useful commercial brief
A concrete brief helps the team prepare a relevant proposal. Include enough operational detail to expose assumptions early.
- Describe your use case, expected workload and launch stages.
- Share hosting preferences, providers and customization requirements.
- Identify procurement, security and compliance review requirements.
Questions to settle before you start.
Are license prices published?
Contact the team for a proposal based on your deployment and service requirements. This page does not imply a fixed price or that every service is included.
Does flexible licensing mean source-code ownership?
Source access, ownership and redistribution rights must be explicitly agreed. Do not assume these rights from a hosting option or customization engagement.