Registering remote runtimes that run your automations in your own infrastructure.
Overview
A Runtime Environment represents a remote runtime — an execution environment outside the UnifyApps cloud (for example, inside your own network) that runs your deployed automations. You register the environment here, associate automations with it, and then export a resource bundle that the remote runtime imports: it contains the deployed automation definitions plus everything they need to run — the connector apps they use, their connections, and the environment's own variable overrides. Each environment carries its own list of key/value environment variables, so the same automation can run with environment-specific values.
Where: Settings › Runtime Environments
Screenshot TODO — Runtime environments
Runtime Environments list
The list is a table of your environments with Name, Domain, Created By, and Last modified By columns. Each row's action menu offers Edit, Export (downloads the environment's resource bundle), and Delete. Clicking a row opens it for editing, and New Runtime Environments starts a new one — before any exist you'll see "No Runtime Environments — You haven't created any runtime environments yet."
Where: Settings › Runtime Environments
Creating or editing a runtime environment
Create Runtime Environment ("Create a new runtime environment") opens a full-page form; editing an existing one opens the same form as Edit Runtime Environment. The environment needs a name — it must be unique across environments — and holds a password, which is stored encrypted and used to secure the environment's exported bundle. The Domain identifies where the remote runtime lives. Saving shows a success message and returns you to the list.
Where: Settings › Runtime Environments › create / edit