---
title: "System Requirements"
slug: "system-requirements"
updated: 2026-08-11T14:11:21Z
published: 2026-08-11T14:11:21Z
canonical: "knowledge.curiositysoftware.ie/system-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.curiositysoftware.ie/llms.txt
> Use this file to discover all available pages before exploring further.

# System Requirements

This article covers Pre-requisites for installing the Curiosity Platform on a Linux & Windows environment.

## **1 - Ensure Pre-Requisites are Complete**

Please ensure that all the pre-requisites are complete prior to installation

### **1.1 Linux System Requirements:**

- 64-bit edition of Linux OS which conforms to [Docker software requirements](https://docs.docker.com/desktop/install/linux-install/), or [Podman](https://podman.io/docs/installation).
- Minimum **16 vCPUs** when deployed on a virtual machine
- vCPUs must be **dedicated (not oversubscribed)** for production workloads
- Minimum 16GB Ram (32GB Recommended)
- Minimum 80GB Hard Drive **FREE** space
- Port 9092 open for inbound communication.
- Port 80 open for inbound communication if using HTTP
- Port 443 open for inbound communication if using HTTPS

Please note: ARM Chip architecture is not supported.

### 1.2 Windows System Requirements:

- **Windows Server** Windows Server 2013 Enterprise 64-bit (minimum) / Windows Server 2025 Enterprise 64-bit (recommended)
- **64bit Processor** (i5 minimum – Intel Core i7 recommended)
- Minimum **32GB Ram**
- Minimum **80GB Hard Drive** space
- If using **Database Generation** functionality, these additional requirements apply:
  - **Port 8091** (configurable) open for inbound communication (both on the network level and on the Windows Firewall)
  - A fully-qualified domain name (**FQDN**) for the Windows Server machine to be accessed from browsers on the user machines
  - (Optional) If the platform instance uses **HTTPS**, an **SSL certificate** for the Windows Server machine as well. If one is not provided, a self-signed certificate will be automatically used instead, resulting in users having to accept using it in the browser.
- (Optional) **Ports 8081-8085** open for **inbound communication** (both on the network level and on the Windows Firewall). **Only** if utilising additional VIP servers
- (Optional) **Ports** for **outbound communication** (both on the network level and on the Windows Firewall) to any external application that VIP needs to connect to (e.g. Databases). This depends on the use case.

**Please Note:** ARM Chip architecture is not supported.

---

### 1.3 Software Requirements Met

**Windows Server Machine:**

- [.Net Framework 4.8](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net48)
  - If using **Database Generation** functionality, the **Developer Pack** must be used.
  - Otherwise, the **Runtime** is enough.
- .[NET 9](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-9.0.309-windows-x64-installer) (formerly .NET Core)
- [Java 8](https://www.java.com/en/download/manual.jsp) / [Java 21](https://www.oracle.com/uk/java/technologies/downloads/#java21)

**User Machine:**

- Internet Browser (Google Chrome recommended)

---

### 1.4 Copy File to Windows Machine

VIP installation file downloaded from link provided by Curiosity.

---

### Common Blockers

We commonly see the below issues during installation.

By completing the checklist above, these blockers will be avoided:

1. Environment not provisioned
2. Insufficient space
3. Ports not open
4. Installation files not downloaded prior to the meeting