Author: Eric Vasbinder
Overview
The standard architecture for the Vista ERP cloud consists of the following components:
The "D1" box: A combined Vista server containing: Vista database, Vista Attachments Database, Vista Application, a Crystal Reports engine, and User Profiles.
The "D2" box: The Vista Web (formerly Keystyle or HFF) application and web server, along with the VRL reverse proxy server installed on the D2 box (since May 2026).
(LEGACY STANDARD ARCHITECTURE CUSTOMRS ONLY) - Separate "VRL" box: The reverse proxy server that enables Vista Remote Link to provide HTTPS based conductivity for Vista rich clients into the Vista database when hosted in our cloud
The "MS1" or "TS1" box: The Azure Virtual Desktop (AVD) or RDP Terminal Services box. For use when end users need lower latency access to the Vista client itself when connecting from connections with substandard latencies above 30-40ms, such as satellite internet (e.g. Starlink).
As you can see, based on the above architectural description, though the environment is architected effectively for small to medium-size customers, larger customers may find that the "D1" box can be overwhelmed if subjected to substantively large queries, batch processing, or simultaneous activity. Over 90% of our customer base will never experience issues with standard architecture.
However, for those customers whose Vista activity level necessitates it, enterprise architecture provides significantly more horsepower and scale to accommodate those needs.
For more details on Enterprise Architecture (EA), please see the following Cloud FAQ article: Enterprise Architecture - Vista
Please reach out to your Trimble ESB, Support, or Account management teams for a copy of our Architectural Diagram if needed. Please note that this requires a mutual NDA, which most customers have as part of their customer contracts with Trimble.
Standard Architecture, though suitably powerful for most of our customers, can sometimes see performance degredation when handling large volumes of concurrent users (e.g. above 150-200) or when handling batch processes involving over 100k-200k items, and tables with millions of records.
Though some of these items, especially historical data in very large tables like HQMA, can be purged to increase performance, as customers grow organically or acquire new operating units, the sheer volume of activity may become apparent as performance degredation.
If that occurs, one option that might be recommended is to join the Enterprise Solution Bundle (ESB) program at the Bronze tier or higher. This way, you can scale your environment horizontally to make use of Enterprise Architecture.
changelog
Tuesday, 16 June 2026 at 03:34PM:
Initial posting