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 execute, use the Execute Module API call available in Unqork's API documentation.

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 — such as Get submissions, Create , 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: Bad actors 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.