GpsGate Server requirements

In case of On-Site installations, these are the requirements that you should take into account before deploying gpsgate.

If you want to know more about the steps of GpsGate Server, read this article.


For larger installations we recommend to use AWS.

Use AWS Aurora as database. It has a lot of very nice features. Real time backup. Easy to scale up.

The Windows instances AWS offers are easy to scale up as your installations grows.

GpsGate 5 can also run parts of the functionality in a cluster. We do not have any public guides (yet) on how to setup and manage a GpsGate cluster. Setup can currently only be done by GpsGate Support. 

Windows Server versions

This guide gives some guidelines on which server hardware and software you should use if you run your own GpsGate Server on your own server. To review a full installation procedure click here.

Estimated transactions

First estimate the number of transactions per second you will have.

30 vehicles with an update once every one minute will give you an average of 0.5 transactions per second.

Depending on how many rules you apply to each application, each transaction will take different amount of computing resources. Below are some estimates given normal usage of GpsGate Server.

Disk usage

Always use reliable disks. Configure your disk to use RAID1 or similar to get a redundant disk.

A typical system uses 0.2 GB per device and year. Please note that you can cleanup or archive old data.

How to not run out of disk space here


GpsGate Server uses very little bandwidth. A transaction is often of less than 0.2 kB.

A user logged into the web interface average about 2 kB/sec.

CPU and memory

GpsGate Server consumes about 150 MB of memory per 100 devices simultaneously online. If you have many users use 4GB and assign 1 or 2 GB memory to MySQL.

GpsGate Server makes good use of multi-core CPU:s. A dual or quad core CPU is recommended.

How to optimize your GpsGate Server performance and user experience!

Windows version

You can install GpsGate Server on any x64 Microsoft's supported version of Windows. For best performance use Windows Server 2008 or 2012. 


Use MySQL 5.5 MySQL will work better with GpsGate Server than MSSQL.
Use MySQL ODBC 5.3.4. This is the only supported version of ODBC driver.

Configuration references

System Small
20 vehicles, update rate 1 minute.
You can use any Windows computer. 

System Medium
500 vehicles, update rate 1 minute.

Windows 2012 R2 or later.
MySQL 5.5 or later.
300 GB RAID1 disks
Dual Core CPU
4 GB ram.

System Large
5000 vehicles,, update rate 1 minute in average.

Windows 2012 R2 or later.
MySQL 5.5 or later.
600 GB RAID1
2 * Quad Core (Xeon) CPU
16GB GB ram.