# Storage Sizing

Storage sizing is an important part of planning a ONEWEB installation, as disk usage directly impacts system stability, performance, and long‑term scalability.

ONEWEB storage requirements are determined by **three main platform components**:

* Web Server
* Application Server
* Database Server

The following guidelines provide **minimum baseline estimates** for storage planning.

***

**Web Server Storage**

The Web Server is responsible for serving static content and handling incoming requests.

* **Minimum disk space:** **2 GB**
* Actual disk usage depends on the selected web server software

> For more accurate sizing, refer to the official documentation of the web server being used.

***

**Application Server Storage**

The Application Server storage requirement consists of **two parts**:

**1. Application Server Middleware**

* Disk usage depends on the application server product
* **Minimum recommended disk space:** **5 GB**

> For accurate sizing, refer to the official documentation of the selected application server.

**2. ONEWEB Binary**

The ONEWEB binary runs on the Application Server and includes:

* App Designer and App Runtime
* Process Designer and Process Runtime
* Page Designer and Page Runtime
* Microflow Designer and Microflow Runtime
* AppSpace and supporting platform components
* **Minimum disk space required:** **2 GB**

***

**Database Server Storage**

ONEWEB requires a **relational database** to store both platform configuration data and application transaction data.

Database storage consists of the following parts:

**1. Database Software**

* **Minimum disk space:** **2 GB**
* Actual requirement depends on the selected database product

> Always verify software requirements with the official database vendor documentation.

**2. ONEWEB Platform Data**

* **Minimum disk space required:** **200 MB**
* Stores ONEWEB configuration and metadata

**3. Application Transaction Data**

* Disk usage depends on application behavior and usage
* Influenced by:
  * Number of users
  * Transaction volume
  * Data retention policy

Transaction data storage should be planned carefully, as it typically grows over time.

***

**Important Considerations**

The storage values listed above represent **minimum baseline requirements**.\
For more accurate storage sizing, consider:

* Expected transaction volume and growth rate
* Data retention and archival policies
* Log and monitoring data storage
* Backup and recovery requirements
* Environment type (Development, Testing, Production)

Production environments usually require significantly more storage than development or testing environments.

***

**Architectural Alignment**

Storage sizing decisions should align with:

* Selected deployment architecture (Standalone, High Availability, Cloud)
* Database design and schema separation
* Backup, recovery, and disaster recovery strategy

Proper storage planning helps prevent future scalability and performance issues.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/getting-started/installation-guide/plan-your-oneweb-installation/sizing-consideration/storage-sizing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.