On-premise system requirements
This guide details the mandatory hardware, software, and database specifications required to host and run our platform reliably on your local infrastructure.
Twinzo 3D application minimum requirements OS:
iOS - version 12.0
Android version 9.0
Windows 10.0
macOS devices with chip M1, M2
Twinzo Cloud Server - tCloud
Running Virtual Machines
OS
Ubuntu Server 24.04 LTS and newer
Docker
Multiple Hosts(recommended):
App server:
2xCPU: 2GHz @ 8Core
RAM: 8GB
DISK: 500GB SSD
1GBit ethernet
Services server:
4xCPU: 2GHz @ 16Core
RAM: 16GB
DISK: 500GB SSD
1GBit ethernet
Running services
Running services are part of twinzo installation. However, system can use already existing services from shared infrastructure if desired. There must be assured connectivity between twinzo instance and shared infrastructure service. Additional twinzo configuration is required to point to custom shared service endpoints.
Services list:
MSSQL 2025 Express
InfluxDB 2.8
Mosquitto MQTT Broker
Redis/Valkey
.NET 10
Nginx [Optional]
Other requirements
remotely accessible VPN: OpenVPN/IPSec/SSTP/BarracudaVPN,WireGuard,Forticlient…
Access docker registries:
dockerhub
registry.twinzo.eu
SSH access to VMs to manage twinzo app
For sending email support, client must provide one of the following credentials
SMTP
Azure Communication Service
Sendgrid
On-premise deployment and access to resources by the Twinzo team must be done via VPN. Access to infrastructure via remote desktop or other alternatives is not possible. The client must be able to provide VPN access to the on-premises network. The only alternative accepted is whitelisting the twinzo office IP address to access the resources.
On-premise instances do not support following functionality:
Automatic 3D model processing(manual upload of 3D model required)
DNS & SSL
If Twinzo is accessed via DNS name:
Customer must provide:
DNS records
Valid SSL certificates
DNS resolution must work:
Inside the local network
Through VPN connections
SSL certificate management and renewal are the customer's responsibility unless agreed otherwise.
NTP (Required)
All systems must have access to a reliable NTP source:
Twinzo servers
RTLS infrastructure
tConnect mobile devices
Incorrect time synchronization may cause data inconsistencies and notification issues.
Twinzo Portal (Web Reporting)
Works On-Premise
Dashboards
Reporting
Analytics
Historical data
Real-time monitoring
Asset tracking
Requirements
Access to Twinzo Portal via HTTP/HTTPS
Ports 80 and 443 available
Google fonts and resources:
tViewer (3D Application)
Works On-Premise
3D visualization
Real-time tracking
Heatmaps
Historical playback
Push Notifications
Push notifications are available only when:
tViewer is installed from:
Apple App Store
Google Play Store
Mobile device has internet access to Apple/Google notification services
Mobile device can reach the on-premise Twinzo environment (local network or VPN)
Without these conditions, push notifications cannot be delivered or displayed.
tConnect (Mobile Application)
Works On-Premise
Material requests
Workflow execution
Barcode scanning
Data collection
Logistics operations
Requirements
Access to Twinzo APIs
Access to MQTT broker (if used)
NTP synchronization
Android device
Internet Requirements
Fully Functional Without Internet
tViewer 3D visualization
tConnect workflows
Requires Internet
Web Portal
Mobile push notifications (Apple / Google services)
Mobile application updates
Schema