| Capacity planning | - Duration is 4–6 weeks, subject to the agreed evaluation plan.
- Workload and environment boundaries are defined in the pilot scope.
- Production capacity, availability, and operating terms are quoted separately.
| - Sizing is based on workload discovery and agreed architecture.
- Operations, deployment footprint, and support scope are defined in the quote.
- Capacity figures and service commitments are not assumed by the package name.
| - Sizing and environments are tailored to the discovered workload.
- Resilience, recovery, and support expectations are explicitly documented.
- No throughput or availability commitment exists unless stated in the executed agreement.
| - Capacity and topology are designed for the approved institutional requirements.
- Hosting, resilience, recovery, and operational duties are contractually scoped.
- No specific jurisdiction, certification, throughput, or service level is implied by this package name.
|
|---|
| Included | - Evaluation environment and agreed network configuration.
- Technical discovery and a documented evaluation scope.
- Guided validation of selected banking controls and integration paths.
- Review of findings, dependencies, and production considerations.
- Pilot is evaluation-only and carries no production service commitment.
| - Production network and native asset configuration.
- Account, wallet, and operation restriction capabilities, subject to the agreed configuration.
- Governance workflows and documented responsibility boundaries.
- Explorer and standard interface scope agreed during discovery.
- Security and operational planning for the selected deployment.
- Formal production quote and executed agreement required.
| - All core production platform capabilities.
- Expanded deployment and operations scope as agreed.
- Coordination planning for institutional identity, key management, monitoring, and integrations.
- Governance and change planning for the agreed institutional operating model.
- Optional services are scoped and priced in the formal quote.
- Formal production quote and executed agreement required.
| - All core production platform capabilities.
- Deployment boundary and administrative responsibilities defined for the institution.
- Architecture, governance, and operational scope established through technical and commercial discovery.
- Potential customer-managed or institution-specific components subject to feasibility and agreement.
- Third-party products and integrations are separately assessed; prebuilt integration is not implied.
- Formal production quote and executed agreement required.
|
|---|
