System Requirements
Minimum hardware, software, and network requirements for Revenue Recovery
The Revenue Recovery platform requires specific hardware, software, and network configurations to operate effectively. This guide outlines the minimum requirements and recommendations for both SaaS and On-Premise deployment models.
Deployment Model Overview
Revenue Recovery can be deployed in two distinct models, each with different infrastructure requirements and management responsibilities. The table below summarizes the key differences between deployment models.
| Component | SaaS Model | On-Premises Model |
|---|---|---|
| Cloud Services Layer | Managed by [Ai]levate | Managed by [Ai]levate |
| Database Storage | Managed by [Ai]levate | Customer managed (Elasticsearch 8.19.1+) |
| AI Compute Layer | Managed by [Ai]levate | Customer managed (Tenstorrent hardware) |
| Relay Service VM | Customer managed | Customer managed |
| Infrastructure & Security | Managed by [Ai]levate | Customer managed |
| EHR Connectivity | Customer configured | Customer configured |
| Identity Integration | Customer configured | Customer configured |
Infrastructure Requirements by Deployment Model
Relay Virtual Machine
The Relay Service VM is required for both SaaS and On-Premises deployments to facilitate secure communication between your EHR system and the Revenue Recovery platform.
| Requirement | Specification |
|---|---|
| CPU | 4 vCPU cores minimum |
| Memory | 16GB RAM minimum |
| Storage | 100GB SSD minimum |
| Operating System | Ubuntu 24.04 LTS |
| Kernel Version | 5.15 or higher |
| systemd Version | 249 or higher |
| Container Runtime | containerd 1.6+ |
Tenstorrent AI Warehouse
The Tenstorrent AI Warehouse provides AI compute capabilities for all Revenue Recovery deployments. For SaaS customers, [Ai]levate manages the hardware in our colocation facility. For On-Premises customers, the hardware is managed at the customer's site or their colocation facility.
| Component | Specification | SaaS | On-Premises |
|---|---|---|---|
| Hardware Model | Tenstorrent TT-LoudBox | Required (Managed by [Ai]levate) | Required (Customer managed) |
| AI Cards | 4x Wormhole™ n300s (8 Tensix processors) | Required (Managed by [Ai]levate) | Required (Customer managed) |
| AI Memory Pool | 96GB dedicated | Required (Managed by [Ai]levate) | Required (Customer managed) |
| CPUs | Dual Intel Xeon 4309Y (2.8–3.6 GHz) | Required (Managed by [Ai]levate) | Required (Customer managed) |
| System RAM | 512GB | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Networking | QSFP-DD high-speed connectivity | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Form Factor | 4U rack-mounted | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Power | Dual redundant power supplies | Required (Managed by [Ai]levate) | Required (Customer managed) |
Elasticsearch Cluster
An Elasticsearch cluster is required for all Revenue Recovery deployments to provide data storage and search capabilities. For SaaS customers, [Ai]levate deploys and manages the cluster. For On-Premises customers, the cluster is deployed and managed at the customer's site or their colocation facility.
| Requirement | Specification | SaaS | On-Premises |
|---|---|---|---|
| Version | Elasticsearch 8.19.1 or higher | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Cluster Size | Minimum 3 nodes (production) | Required (Managed by [Ai]levate) | Required (Customer managed) |
| CPU per Node | 8 cores minimum | Required (Managed by [Ai]levate) | Required (Customer managed) |
| RAM per Node | 32GB minimum (16GB heap) | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Storage per Node | 1TB minimum, SSD recommended | Required (Managed by [Ai]levate) | Required (Customer managed) |
| JVM Version | Version 17 or higher | Required (Managed by [Ai]levate) | Required (Customer managed) |
| Network | Connectivity between cluster nodes | Required (Managed by [Ai]levate) | Required (Customer managed) |
Network Requirements
Network connectivity requirements apply to both deployment models, though the specific endpoints and configurations may vary.
| Requirement | Specification | SaaS | On-Premises |
|---|---|---|---|
| HTTPS Outbound | Port 443 access | Required | Required |
| DNS Resolution | Cloud services endpoints | Required | Required |
| Database Connectivity | Relay to EHR database | Required | Required |
| Internal Ports | Service communication | Standard ports | Standard ports |
| Network Security Groups | Firewall configuration | Required | Required |
| Private Networking | VPN/private connectivity support | Supported | Supported |
| Virtual Network Integration | VNet/VPC integration | Supported | Supported |
| Web Application Firewall | WAF protection | Recommended | Recommended |
Cloud Services Layer
For all Revenue Recovery deployments, [Ai]levate deploys and manages the complete cloud infrastructure, including platform management, security, and compliance controls.
| Feature | Description | SaaS | On-Premises |
|---|---|---|---|
| Platform Management | Automated upgrades, scaling, monitoring | Managed by [Ai]levate | Managed by [Ai]levate |
| Elastic Datastore | Dedicated per-customer database | Managed by [Ai]levate | Managed by [Ai]levate |
| Encryption at Rest | Enterprise-grade data encryption | Managed by [Ai]levate | Managed by [Ai]levate |
| BYOK Support | Bring Your Own Key encryption | Optional customer configuration | Optional customer configuration |
| Geo-Redundancy | Multi-region data replication | Available on request | Available on request |
| Backup & Recovery | Automated snapshots and restoration | Managed by [Ai]levate | Managed by [Ai]levate |
| Security & Compliance | Built-in security controls and auditing | Managed by [Ai]levate | Managed by [Ai]levate |
Operational Requirements
High Availability Recommendations
| Consideration | SaaS | On-Premises |
|---|---|---|
| Multi-Zone Deployment | Included | Recommended |
| Redundant Infrastructure | Included | Customer responsibility |
| Distributed Architecture | Included | Customer responsibility |
| Failover Capability | Automated | Customer configured |
Backup and Recovery
| Capability | SaaS | On-Premises |
|---|---|---|
| Automated Backups | Included | Customer responsibility |
| Snapshot Scheduling | Managed by [Ai]levate | Customer configured |
| Geo-Redundant Storage | Available | Recommended |
| Recovery Procedures | Managed by [Ai]levate | Customer responsibility |
Monitoring and Observability
| Component | SaaS | On-Premises |
|---|---|---|
| Infrastructure Monitoring | Managed by [Ai]levate | Customer responsibility |
| Log Aggregation | Managed by [Ai]levate | Customer responsibility |
| Application Performance Monitoring | Managed by [Ai]levate | Customer responsibility |
| Alerting and Notifications | Configured by [Ai]levate | Customer configured |
Updated about 1 month ago