# Microflow Server (Standalone Server Mode)

When using **Standalone Server Mode**, a Microflow is deployed and executed as a **service running on the Microflow Server Runtime**.\
In this mode, the Microflow is **activated directly on the server** and exposed as a **REST‑based service**, allowing external systems and applications to invoke it through standard HTTP APIs.

Unlike Embedded Mode, there is **no separate deployment file** (such as a JAR copied into another application). The Microflow becomes live and accessible immediately once it is activated on the Microflow Server.

***

### Key Characteristics

In **Microflow Server mode**:

* Microflows are hosted on a **standalone runtime server**
* Each Microflow is exposed as a **REST API**
* Consumers interact with Microflows over **HTTP**
* The Microflow runs independently of consuming applications
* Scaling and lifecycle management are handled by the server runtime

This makes the Microflow Server suitable for **service‑oriented and microservices‑based architectures**.

***

### How Microflow Server Works

1. The Microflow is designed and validated in **Microflow Designer**
2. It is exported or activated in **Standalone Server mode**
3. The Microflow is deployed to the **Microflow Runtime Server**
4. The system exposes the Microflow as a **REST endpoint**
5. External systems can invoke the Microflow using REST APIs

Once activated, the Microflow behaves like a standard backend service.

***

### When to Use Microflow Server Mode

Standalone Server Mode is recommended when:

* The Microflow must be accessed by **multiple applications**
* External systems need to call the integration via **REST APIs**
* Loose coupling between systems is required
* Independent scalability and deployment are important
* The integration acts as a shared backend service

Typical use cases include:

* System‑to‑system integration
* Backend services for web or mobile applications
* Microservices implementations
* Centralized integration hubs

***

### Access and Invocation

In Microflow Server mode:

* Each Microflow has a REST endpoint
* Requests and responses use standard data formats (such as JSON)
* Authentication, authorization, and monitoring can be enforced at the server level

This ensures that Microflows can be safely and reliably consumed by external services.

***

### Microflow Server vs Embedded Mode

| Aspect       | Embedded Microflow   | Microflow Server              |
| ------------ | -------------------- | ----------------------------- |
| Deployment   | Embedded in Java app | Deployed on standalone server |
| Access       | Java API             | REST API                      |
| Runtime      | Host application JVM | Dedicated Microflow Runtime   |
| Scalability  | Tied to host app     | Independently scalable        |
| Architecture | Library‑style        | Service‑oriented              |

***

### Summary

The **Microflow Server** enables Microflows to run as **standalone REST services**, making them accessible to external systems without embedding them into another application.

Using Microflow Server mode, ONEWEB allows developers to:

* Expose Microflows as REST APIs
* Build service‑oriented integrations
* Share Microflow logic across multiple systems
* Scale and manage integrations independently

This mode is ideal for building **enterprise‑grade, reusable, and scalable integration services** using ONEWEB Microflow.


---

# 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/building-apps/integrations/develop-integration-with-oneweb-microflow/start-with-microflow-in-oneweb/export-your-microflow/microflow-server-standalone-server-mode.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.