Choosing the Right Riva Deployment Model: Cloud Shared, Cloud Dedicated, or On-Premise

Riva offers three different deployment models to accommodate various organizational needs: 

• Riva Cloud - Shared Tenant
• Riva Cloud - Dedicated Tenant
• Riva On-Premise

Each model provides Riva's advanced server-side CRM to email synchronization, with differences in infrastructure management, data isolation, customization capabilities and compliance support. 

Riva Cloud - Shared Tenant

Riva Cloud - Shared tenant is the standard Software as a Service (SaaS) deployment, hosted on Amazon Web Services (AWS). It's designed for organizations that want a quick setup without the need to manage infrastructure. 

Key Features

• No software installations or maintenance required. 
• Always operate on the latest Riva version. 
• Supports multiple CRM and email platforms, including Office 365, Exchange, and Google.
• Multi-tenant architecture with logical data isolation.  
• Centralized administration for managing synchronization policies. 
• Secure Cloud Architecture. 

Considerations

• The administrator interface has limited support for advanced custom sync options. To apply these configurations, customers need to contact the Riva Cloud team for assistance with customizations.

Riva Cloud - Dedicated Tenant

This model provides a single-tenant environment within Riva Cloud, offering enhanced control and isolation. It is suitable for organizations with stringent security, compliance and performance requirements.

Key Feature

• Data Isolation: Dedicated infrastructure ensures complete separation from other tenants. 
• Enhanced Performance: Resources are allocated solely to your organization, reducing latency and avoiding to "noisy neighbour" effect. 
• Network Security: Customizable network configuration, for example, IP whitelisting. 
• Application-Level Customizations: Greater flexibility to implement application-level changes. 
• Version Control: While Riva manages updates, organizations can coordinate with Riva to defer an update for a valid reason. Note that we won't let the version be more than two releases behind. 

Consideration

• Higher cost compared to the shared tenant model due to dedicated resources.

Riva On-Premise

This model requires installing Riva on your organization's own servers, giving you full control over the environment. It's often the preferred choice for organizations with strict regulatory or compliance requirements.

Key Feature

• Complete control over software updates and configuration.
• Suitable for environments with strict data residency and compliance requirements. 
• Includes Riva Manager for real-time monitoring and management. 
• Riva administrator can access Advanced Options and apply customizations to support Custom Object configurations.

Considerations

• In-House IT Expertise Required: Installation, configuration, and ongoing maintenance must be handled by your internal technical team.

• Customer-Managed Infrastructure: All hardware, networking, and server infrastructure is the responsibility of your organization.

• Increased Operational Overhead: Internal resources are needed for setup, monitoring, backups, and troubleshooting, adding to the day-to-day workload.

• Delayed Access to New Features: Feature updates are released to Riva Cloud customers first. On-premise deployments must be manually updated to receive the latest improvements.

• Complex Setup Process: Deployment can be time-consuming, particularly in environments with strict security controls or hybrid network configurations.

• Limited Support Visibility: Riva Support has reduced access to on-premise environments, which can make advanced troubleshooting more difficult.

• Scaling Limitations: Expanding capacity requires additional hardware and potential architectural changes, which can be costly and time-consuming.

• Disaster Recovery Responsibility: Your organization must implement and maintain its own high availability and disaster recovery solutions.

Comparison Summary