# ONEWEB Runtimes

### **Overview**

**ONEWEB Runtimes** are the execution engines of the **ONEWEB Business Application Platform**. They are responsible for translating and running the configurations created by the Designer Studios.

Each Designer Studio has a corresponding Runtime that interprets its design artifacts and executes them in a controlled environment. This separation between design and execution allows applications to be built visually while still running reliably at scale.

***

### **From Design to Execution**

In the ONEWEB Platform, applications are first **designed** using visual tools and then **executed** by the appropriate Runtime.

For example:

* The **App Designer** produces configuration for application structure and behavior
* The **App Runtime** reads these configurations and generates executable web forms
* The generated forms are then hosted and served through a web server

This model ensures that design changes can be translated consistently into runtime behavior without manual intervention.

***

### **Runtime Responsibilities**

ONEWEB Runtimes provide the execution environment for end‑user applications and backend logic. Their responsibilities include:

* Executing application logic and configurations
* Managing user interactions and transactions
* Handling integrations and backend processing
* Ensuring consistent behavior across environments

By standardizing execution through runtimes, ONEWEB reduces variability and operational complexity.

***

### **Page Runtime and Application Packaging**

Most ONEWEB Runtimes provide a runtime environment where applications run directly for end users.\
However, **Page Runtime** follows a slightly different model.

For page‑based applications, the Page Runtime is responsible for:

* Building HTML packages for web applications
* Generating mobile application packages for mobile platforms

These packages are then executed on:

* A web server for browser‑based applications
* The mobile operating system for Android or iOS applications

This approach allows the same page designs to be delivered across different platforms while maintaining a consistent development model.

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

***

### **How Runtimes Fit into the ONEWEB Platform**

Within the ONEWEB conceptual model:

* **Designer Studios** define application structure and behavior
* **AppSpace** manages and coordinates application components
* **Runtimes** execute applications and processes

This layered approach allows ONEWEB to support multiple application types and development styles while maintaining consistency, scalability, and control.


---

# 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/what-is-oneweb/oneweb-concepts/oneweb-runtimes.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.