# Standalone Architecture

#### **Overview**

**Standalone Architecture** is a simple and cost‑effective deployment model suitable for non‑critical or moderately critical systems where occasional downtime for maintenance or upgrades is acceptable.

This architecture follows the standard **three‑tier model**, separating the platform into Web, Application, and Database tiers. It is easy to maintain and provides a straightforward starting point for organizations adopting the ONEWEB Platform.

***

#### **Architecture Structure**

In a Standalone Architecture, the ONEWEB Platform is logically divided into three tiers:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fl8uHvdgWAZER2Stpyhye%2F0?alt=media" alt=""><figcaption></figcaption></figure>

* **Web Tier**\
  Handles incoming requests from clients or load balancers. This tier processes static content requests and forwards business logic requests to the Application Tier.
* **Application Tier**\
  Executes application logic using application server middleware. This tier is responsible for processing business rules, workflows, and integrations.
* **Database Tier**\
  Manages data persistence and storage, ensuring data integrity and availability for the application.

This separation allows each tier to focus on its specific responsibility while remaining part of a unified architecture.

***

#### **Deployment Characteristics**

Although the diagram typically shows each tier running on a separate server, **Standalone Architecture is flexible in deployment**.

Depending on available resources and security requirements, organizations may choose to:

* Deploy all three tiers on a **single server** with sufficient capacity
* Separate the Web Tier from the Application and Database tiers
* Deploy each tier on its own server

Additional network controls, such as firewalls, can be introduced between tiers to improve security and performance, though this is not strictly required in a standalone setup.

***

#### **When to Use Standalone Architecture**

Standalone Architecture is a good fit when:

* Simplicity and cost efficiency are priorities
* The system can tolerate planned downtime
* The workload is predictable and moderate
* The environment is used for development, testing, or smaller production systems

For systems requiring higher availability or fault tolerance, alternative architectures such as **High Availability** or **Cloud‑based** deployments may be more appropriate.


---

# 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/overview/platform-architecture/standalone-architecture.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.