HOME NEWS ARTICLES PODCASTS VIDEOS EVENTS JOBS COMMUNITY TECH DIRECTORY ABOUT US
at Financial Technnology Year
| ? |
1. Maximum Concurrent Users
Number of users who can actively use the system simultaneously without performance degradation
No information available
|
| ? |
2. System Uptime
Percentage of time the system is operational and available to users
No information available
|
|
3. Single Sign-On Support
Integration with enterprise authentication systems
Single Sign-On (SSO) integrations are available for enterprise users.
|
|
|
4. Browser Compatibility
Support for various web browsers and operating systems
Supports major web browsers and operating systems.
|
|
|
5. Performance Optimization
Design focused on speed and responsiveness for complex operations
Performance optimization for speed is a documented competitive advantage.
|
|
|
6. Integration Architecture
Framework for connecting with other systems via APIs or other methods
Integration architecture supports connections via open APIs.
|
|
|
7. Customization Options
Ability to adapt platform to firm-specific needs and workflows
Customization options available for workflows and reports.
|
|
|
8. Update Frequency
Regular delivery of new features and improvements
Regular platform updates and feature releases described in Pershing communications.
|
|
|
9. Scalability
Ability to grow with increasing users, clients, and transaction volume
Scalability highlighted for both small and large enterprise deployments.
|
|
|
10. Disaster Recovery
Robust backup and restoration capabilities in case of system failure
Disaster recovery measures discussed in technical documentation.
|
|
|
11. Multi-Factor Authentication
Enhanced login security requiring multiple verification methods
Multi-factor authentication required for user and client access.
|
|
|
12. Data Security Protocols
Comprehensive safeguards protecting client and firm information
Data security protocols follow industry standards (SOC 2, encryption, etc.).
|
|
|
13. System Reliability
Platform stability and resistance to outages or performance issues
System reliability and uptime are emphasized by Pershing’s platform SLAs.
|
|
|
14. Cloud-Based Architecture
Platform delivered via secure cloud infrastructure rather than on-premises
Cloud-based platform as standard delivery.
|
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, summarised using AI.
If you are the vendor, claim your page