System Requirements for GINESYS ERP (On Premise)
System Requirements
There are changes in the system requirements for running Ginesys ERP 12.25.0 on premise. Please note the following requirements carefully. The requirements were drafted after evaluating changes in the hardware and software in the last few years. It is important to upgrade the hardware and operating systems periodically so that you continue to get the best performance from your Ginesys ERP system with less business disruptions and increased security.
Initially, there might be an system alert / warning that your system does not meet the minimum system requirement criteria. In future, operations will be blocked if the system does not meet the minimum requirements.
Component | Server Minimum (Dedicated Ginesys ERP Server) | Workstation Minimum |
Processor | Quad-core x64 architecture 2.8 GHz CPU | Dual-core x64 / x86 architecture 2.0 GHz CPU |
Memory | 8 GB RAM | 8 GB RAM |
HDD space | 200 GB or more of available hard disk space | 50 GB or more available hard disk space |
HDD count | Minimum 2 same capacity HDD (for backups) | 1 |
HDD Type | SSD NOTE: HDD will cause derated performance | SSD NOTE: HDD will cause derated performance |
UPS | Online UPS with 30 minutes backup | Offline UPS with 15 minutes minimum backup |
Operating System | Windows Server 2019 or above | Windows 10 or above |
Internet | 50 Mbps or above Broadband NOTE: Good and stable internet speed is a critical requirement for functioning of Ginesys ERP on prem. If you are sharing the broadband for regular browsing and/or other applications, please make sure that Ginesys has enough free bandwidth (50Mbps+) at any time. | No direct internet connection required for Ginesys |
Database, Third Party and other Software Components
Component | Description |
|---|---|
Oracle Database Server 12c | Oracle Database 12.1.0.2 is required for Ginesys ERP |
SQL Server 2022 Express Edition (or above) | If you are having retail operations and run Ginesys POS in your stores then please note that from Ginesys POS v2.25.0 onwards, the database server requirements have been changed to SQL Server 2022 Express Edition or above. In case of a database or system crash in any store, you would need to run the Ginesys POS Recovery tool in the HO to recover the store. This is a DR (Disaster Recovery) tool for Ginesys POS. To perform disaster recovery of a POS store from HO you would require a local SQL Server Database in HO. You should install SQL Server 2022 Express Edition in your HO infrastructure for recovering any POS database, should the need occur. Even if any store was running a lower version of SQL Server, e.g. 2008 or 2012 or 2016 before the crash you should take the time to install SQL Server 2022 during recovery and restore the database in SQL Server 2022 or above only. NOTE: If your store data size exceeds 10GB we recommend that you switch to SQL Server 2022 Standard Edition which is a licensed edition from Microsoft. |
Microsoft .NET Framework 4.7.2 | Required to run the current version of Ginesys ERP runs on .NET framework 4.7.2 Now Microsoft .NET Framework 4.7.2 is a must have. |
Microsoft .NET 8 Hosting Bundle (Refer Microsoft .NET Core Support Policy) | Ginesys ERP requires .NET 8 Hosting Bundle. Install via Ginesys AutoUpdate or download directly from NOTE: Please note that to keep in sync with the support policies with the base frameworks and components for Ginesys POS, we will be updating our application system requirements from time to time. For example, the “End of Support” for the .NET 8 framework is November 10, 2026. Hence we will be updating our system requirements on or before the said date to have the application run on the latest supported framework. |
Important
Above requirements are the minimum requirements for a 3-5 user typical workload.
Actual requirements may vary based on your product configuration, work load and backup requirements.
Running GINESYS on less than minimum system configuration will have adverse effects on performance.
Desktop operating systems (e.g. Windows 7, Windows 10, Windows 11) are strictly not supported on Ginesys ERP Server.
Operating system service packs and updates as released by Microsoft from time to time should be updated on systems on a regular basis
Anti-Virus and Network Security software if installed on the server will have to be configured and maintained by you so that necessary communications to and from GINESYS Server is allowed. GINESYS support if anticipates that any issue is being caused by such third party software may request the client to uninstall the concerned software while working on the ticket.
Always keep antivirus definitions updated. There has been quite a few occurrences where an erroneous update by Anti Virus providers has cause disruption in Ginesys ERP operations, the same was corrected in a subsequent version of the Anti Virus update.
Specified bandwidth is the minimum bandwidth required for Ginesys operation like Live Sync, Auto Update, API and Webhook Integrations etc.
List of Outbound Communication Ports
Following is a list of internet communication that happens from the Ginesys ERP server. Please review them carefully and have them allowed / configured in your firewall and also include them in your IT and System / Internet Policy for maintenance. Any disruption in inward or outward communication will affect one or more functionality of the ERP.
Outbound Communication | |
|---|---|
| 1 | Ginesys Web DB (SQL Server). The endpoint is different for every installation. Your WebDB endpoint will be shared with you by the Ginesys Cloud Infrastructure team. |
| 2 | GSL Licensing Server
|
| 3 | GSL Patch Update Server (FTP) |
| 4 | GSL Patch Update Server (HTTP)
|
| 5 | EaseMyGST portal
|
| 6 | GST-Taxilla portal
|
| 7 | EMR service
|
Inbound Communication - Opening up Ginesys APIs in your Firewall
If you are using Ginesys APIs for any integration purposes, e.g. if your Ginesys ERP instance is connected to Browntape or Zwing or any other integration scenario which would require calling an API on the ERP application instance then you should take note of the following. This is a generic guide as the actual implementation would vary based on your security policies, hardware and software in place to control the security plane of your IT deployments.
Implement a Firewall device. There are plenty of good security organizations like SonicWall, Fortigate, Sophos, Cisco etc. who have this type of solution
Decide which port to allow access. Port 80 or Port 443 (https) are the most common ports. Ideally you should install a security certificate and use 443 for https communication
Create rules in the Firewall to route incoming API calls to the application server.
Implement a “Deny All” policy. It is safer to start with a “Deny All” policy and then start adding the “Allow” rules on your Firewall.