- If the organization requires publicly accessible and standardized compliance artifacts
- If the procurement process depends on easily accessible public attestations (e.g., SOC 2 Type II, ISO 27001) and detailed security architecture disclosures, DA’s public materials (as accessed) may be insufficient; request the evidence pack during vendor diligence.
- If operational resilience risk is the primary constraint
- If the risk appetite is highly sensitive to third-party outages, the February 2024 DA infrastructure outage is a notable due diligence flag. Organizations may prefer architectures with multi-provider redundancy or a vendor with documented multi-region resilience metrics.
- If transparent, self-serve pricing is required
- DA does not publish clear pricing tiers publicly; organizations that require published rate cards for rapid price discovery may consider vendors with public pricing or standardized SaaS offerings.
- If a cloud-native multi-tenant SaaS core is required by default
- Organizations explicitly pursuing a multi-tenant, cloud-native core with rapid feature iteration and self-service provisioning may find cloud-native entrants more aligned to that model, depending on regulatory posture and implementation constraints.
- Reliability incident
- February 2024: A DA network outage affected multiple client banks, causing internet and mobile banking disruptions and partial degradation before recovery was declared.
- Transparency gaps in public documentation
- Publicly accessible security certifications and detailed compliance documentation were not found in the material accessed for this research.
- No public pricing tiers were identified.
- Roadmap and future capabilities
- No publicly accessible, detailed product roadmap was located in the sources reviewed. Procurement discussions should request roadmap detail and upgrade/release cadence.