This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Requirements for Orbit 3DM Publisher

This page describes the hardware requirements for Orbit's server products, Orbit 3DM Publisher, and Orbit 3DM Feature Extraction.

Smart Choices

There are no special hardware requirements for Orbit Mapping solutions. However, make smart choices in relation to

  • the number of concurrent users
  • the volume of data to be hosted
  • the expected performance

Operating System

For more about Windows, Linux, and Java requirements, see System Requirements.

Windows Server only, virtual machines or physical hardware.
For Linux installation, contact

Computing Power

Minimum: 64 Bit OS, 8 GB ram, Quad-core.

Graphics Card

No requirements, the Orbit server doesn't use GPU processing.

Server Disks & Disk-space

No special requirements.
An Orbit Server installation is about 500MB, preferably installed on a dedicated partition. Reserve 10 to 50 GB free disk space.

Storage & File Access

The Orbit Service requires resource access.
Data can be stored on local or network-attached physical storage (NAS) drives or in the cloud. Orbit provides cloud storage drivers for Microsoft Azure and Amazon S3 blob storage accounts.
To support other cloud storage providers, please contact

Special attention is required to manage and organize the huge volume of mapping resources, see Requirements for Orbit 3DM Desktop Products.


For 3DM Publisher only, Web Client to Server connection.

For data hosting the Server upload and Client download speed needs to be taken into account.
Minimum server upload/download speed of 50 Mbps.

Web Client-Server communication requires a single port to operate.
The default configuration is set to port 1111. Port 80 or 443 are supported, well as the use of a Proxy server.

Network Speed

This is an informative table to indicate the impact of the internet and LAN network speed.

Network speed Copy time
Unit Gbps Mbps Kbps kB/s 5MB 100MB
1kb 1 *10-6 1*10-3 1 0.125 680 min 13 600 min
100kb 0.0008 0.8 800 100 51.2 sec 17 min
1mb 0.001 1 1 000 125 41 seconds 13 min
100mb 0.1 100 100 000 12 500 0.41 sec 8.2 sec
1gb 1 1 000 1 000 0000 125 000 0.041 sec 0.82 sec

Network speed units are expressed in Bits per second, not in Bytes. In the rightmost column, the equivalent copy time is calculated for e.g. a full-resolution panorama image file. Note, this is in ideal conditions if the entire network capacity is available.

Internet Access

Online access to the Orbit License Service is required, see Orbit Online License Activation.

Web Server

The Orbit Server includes a Web Server supporting Http (Https) and Ws (Wss) communication.
For direct Server-WebClient communication, there is no need to install additional services like Microsoft's Internet Information Service, Apache or others.


Additional configurations and conditions must be met to set up secured communication. A Java KeyStore file derived from the Authorization Certificate is required.

Certificate submitting and KeyStore file creation must be completed by the company's IT team or hosting partner prior to re-configuring the Orbit Web Server from Http into Https. For more information, see


Use of proxy is supported, not mandatory. Ensure correct transfer of all HTTP/HTTPS and Ws/Wss communication!
Depending on your corporate IT procedures use of port forwarding or (reverse) proxy may be advised or required. However direct communication with the Orbit Service will always be fastest.
Setup and management of firewall, port forwarding or proxy server, and server domain name belong to the responsibility of the company's IT team or hosting partner. For more information, see

Domain Name

We highly recommend the use of a domain name to refer to the Orbit server.
For more information, see Wikipedia Domain Name System.

Installation Schemes

The Orbit 3DM Publisher can be installed as an individual setup, directly accessible (1) or behind a proxy or firewall (2).
A load balancer can be used to configure multiple Orbit 3DM Publisher setups. A multi-setup can use a shared storage (3) or each instance can have its own private storage (4). Orbit 3DM Publisher instances and connecting storage must be kept synchronized. Load balancing software is not provided by Orbit.

Last modified:: 2023/07/05 10:45