---
title: "Server-Side Execution"
slug: "server-side-execution"
tags: ["module-builder"]
status: "update"
updated: 2026-10-19T16:56:14Z
published: 2026-10-19T16:56:14Z
canonical: "docs.unqork.io/server-side-execution"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Server-Side Execution

Server-side execution occurs when a module runs on Unqork's server instead of in the end-user's browser. This approach is a best practice for application security, because it keeps sensitive logic and data out of the browser where end-users could inspect it.

To configure a server-side execution, use the **Execute Module** API call available in [Unqork's API documentation](https://developers.unqork.io/#operation/executeModule).

## Why Server-Side Execution Is More Secure

When an API call runs in the browser, any end-user can open the DevTools Console and potentially inject malware or access private information. Running modules server-side prevents this.

Running internal API calls, like Get Submissions, Create Submission, or Update Submission, in server-side modules provides the following benefits:

- **Speed**: API calls run on a remote server, which takes the load off the browser.
- **Security**:  cannot access private information through the DevTools Console.
- **Easier Debugging**: Creating modular API modules produces a smaller, cleaner codebase when troubleshooting.

## Organizing Applications with API Modules

It is best practice to organize applications so that each API is represented by its own module. For example, an application might have a Create Submissions module, an Update Submissions module, and a Get Submissions module. When calling these API modules with remote executes, treat them the same way as an external API.

For instance, an API module that sends email reminders might include a **Plug-In** component that uses the SendGrid API. A separate front-end module uses another **Plug-In** component to make a remote execute call to the SendGrid module, which triggers the email.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-05-18 | Initial publication. Content migrated from Common Troubleshooting Strategies. |
| 2026-10-15 | Corrected "server-side execute" to "server-side execution", replaced em dashes with commas, fixed the Service Logs link, and added See Also descriptions. |

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

Includes the Short Answer component, Long Answer component, Select Boxes, Radio component, Dropdown, Number component and Single Checkbox.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

The DevTools Console helps you securely store, build, test, and deploy your software.

Malware is software designed to disrupt, damage, or gain access to a computer system.

A definition