Skip to main content

Recommended Hardware & OS Specs

Minimum and recommended specs for running Virifi’s Solution Proposal across test, development, and production environments.

Updated over 8 months ago

Overview

This guide outlines the recommended hardware and software environments for deploying Virifi’s Solution Proposal. These specs ensure optimal performance, security, and compliance during implementation, demo, and live operation phases.


Minimum System Requirements

Component

Specification

CPU

Dual-core, 2.0 GHz or higher

RAM

4 GB

Disk

50 GB SSD

OS

Ubuntu 20.04+ / Windows Server 2019+ / macOS 12+

Network

Stable internet connection (2 Mbps or higher)

Runtime

Java 11+, .NET 6.0+, Docker Engine (optional)

Security Modules

SoftHSM or simulated HSM configuration

Suitable for demo environments, SDK testing, and API exploration.


Recommended Production Environment

Component

Specification

CPU

Quad-core, 2.4 GHz or higher

RAM

8–16 GB

Disk

100 GB SSD/NVMe

OS

Ubuntu Server 22.04 LTS / Windows Server 2022

Network

Secure, redundant connectivity with firewall/NAT traversal

HSM

Cloud HSM (e.g., Securosys), On-Prem HSM (iShield, YubiHSM)

Other

Hardware-backed secure storage, audit logging, TLS termination



Developer/Integration Workstation

For integration engineers and testers:

  • OS: Windows 11 / Ubuntu 22.04 / macOS Ventura

  • Tools: XCA, OpenSC, YubiKey Manager, Postman, Docker Desktop

  • Browsers: Chrome, Firefox, Safari (for Web SDK tests)

  • Hardware: Optional FIDO2 device (YubiKey 5 FIPS), test token or smartcard


Security Considerations

All HSM and signature operations should be executed:

  • On machines with secure boot and disk encryption

  • With admin rights limited to system maintainers

  • Within isolated containers or VMs in cloud deployments


Optional Tooling

  • Docker Compose for local signature microservice orchestration

  • Elastic Stack or Splunk for log visualization

  • SonarQube (for code quality review if self-hosting components)

  • HashiCorp Vault or Azure Key Vault (for key wrapping/testing)

Did this answer your question?