# Prerequisites & System Requirements Before getting started with **ONEWEB**, ensure that the following prerequisites and system requirements are met.\ This section helps confirm that your environment and access are ready before proceeding with installation or application development. *** ### User Access & Permissions To work with ONEWEB, you need: * A valid **ONEWEB user account** * Appropriate **roles and permissions** assigned by a system administrator Depending on your role, access may include: * AppSpace * Designer Studios * Runtime environments > User and access management is typically handled through ONEWEB IAM services and should be configured before users begin working on the platform. *** ### ONEWEB Environment Availability ONEWEB must be deployed and running in at least one environment before you begin. Supported deployment environments include: * **Standalone Architecture** * **High Availability Architecture** * **Cloud or Container‑based Architecture** The platform may be hosted: * On‑premises * In a private or public cloud * Using container orchestration platforms such as Kubernetes > Detailed deployment and architecture options are covered in the **Platform Architecture** section. *** ### Client‑Side System Requirements To access and use ONEWEB design and management tools, users require: * A modern **web browser** (for AppSpace and Designer Studios) * Network connectivity to the ONEWEB platform endpoint ONEWEB is primarily browser‑based, and no local development frameworks or SDKs are required for standard application design activities. *** ### Server‑Side System Requirements (High‑Level) ONEWEB is an enterprise application platform designed to run on **Java EE‑based infrastructure** and modern cloud environments. At a high level, the platform requires: * An application server environment capable of running ONEWEB runtimes * Database services for persistent data storage * Network infrastructure that allows communication between platform components Depending on the deployment model, these components may run: * On a single server * Across multiple servers * As containerized services > Detailed server sizing, OS requirements, and infrastructure configuration are covered in the **Installation & Configuration** section. *** ### Core Platform Services Readiness Before proceeding, the following ONEWEB platform services should be available and operational: * **AppSpace** for application creation and lifecycle management * **Designer Studios** for UI, process, and integration design * **Runtime services** for executing applications and logic * **Database services** for application and platform data These services may be deployed as dedicated servers or shared services, depending on architecture choices. *** ### Environment Separation (Recommended) For enterprise usage, it is recommended to maintain separate environments for different stages of the application lifecycle: * **Testing / Development Environment** * **Production Environment** * **Disaster Recovery Environment** (optional but recommended) This separation supports controlled promotion, risk reduction, and business continuity. *** ### What Is *Not* Required to Start To avoid confusion, the following are **not required** at this stage: * Writing custom code * Local installation of development frameworks * Deep knowledge of ONEWEB platform internals * Production‑grade deployment readiness ONEWEB is designed to allow users to start quickly using visual and low‑code tools. --- # 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/oneweb-platform-th/getting-started/prerequisites-and-system-requirements.md?ask= ``` 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.