Cyberbank Digital
from Technisys
| ? |
1. Automated Testing Coverage
Percentage of codebase covered by automated tests
No information available
|
| ? |
2. Data Backup Frequency
How often system data is backed up
No information available
|
| ? |
3. Monitoring Coverage
Percentage of system components under active monitoring
No information available
|
| ? |
4. API Rate Limits
Maximum number of API calls allowed per minute
No information available
|
| ? |
5. Database Performance
Speed of database queries and transactions
No information available
|
|
6. Microservices Architecture
Use of modular, independently deployable services
Core architecture is defined as microservices-based for modularity and scalability.
|
|
|
7. Multi-region Deployment
Platform operation across multiple geographic regions for redundancy
Multi-region deployment for resilience and latency management is included by design.
|
|
|
8. Cloud-based Architecture
Whether the platform uses cloud infrastructure versus on-premises
Cloud-native and cloud-agnostic architecture is emphasized throughout product literature.
|
|
|
9. Backward Compatibility
Whether updates maintain compatibility with older devices and OS versions
Backward and cross-device compatibility is referenced in digital banking platform documentation.
|
|
| ? |
10. Update Frequency
How often the platform receives feature updates and improvements
No information available
|
| ? |
11. Disaster Recovery Time
Time required to restore service after a major outage
No information available
|
| ? |
12. Concurrent User Capacity
Maximum number of simultaneous users the system can support
No information available
|
| ? |
13. System Response Time
Average time for the system to respond to user requests
No information available
|
| ? |
14. System Uptime
Percentage of time the platform is operational and available
No information available
|
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Please log in to see this information. (Why do we ask this?)
Publicly available data.
If you are the vendor, claim your page