A Runtime Environment represents a remote runtime — an execution environment outside the UnifyApps cloud, such as inside your own network — that runs your deployed automations.
Overview
You register the environment under Settings › Runtime Environments, associate automations with it, and then export a resource bundle that the remote runtime imports. The bundle 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.
Use Cases
Run deployed automations inside your own network rather than in the UnifyApps cloud, for infrastructure or data-residency reasons.
Give the same automation different variable values depending on which remote runtime it's exported to.
Export a self-contained bundle — automation, connector apps, connections, and variables — to a remote runtime in one action.
Maintain multiple named runtime environments, each with its own domain and password, for separate on-premise deployments.
The 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."
Creating or Editing a Runtime Environment
Create Runtime Environment opens a full-page form; editing an existing one opens the same form as Edit Runtime Environment. The environment needs:
Parameter | Description | Example |
|---|---|---|
Name* | Must be unique across environments. | on-prem-eu-runtime |
Password* | Stored encrypted; used to secure the environment's exported bundle. | A password known only to the runtime operator. |
Domain* | Identifies where the remote runtime lives. | runtime.internal.example.com |
Saving shows a success message and returns you to the list.
What Export Produces
Export, available as a row action, downloads the environment's resources so a remote runtime can import and run them. For every automation associated with the environment, the bundle collects the deployed version of the automation, the connector apps and resources its nodes use, the connections those nodes reference (with credentials handled through the platform's encryption), and the environment's environment variables.
Note: an automation that isn't deployed is skipped — only deployed definitions are exported, so deploy your automations before exporting.
Deleting a Runtime Environment
Delete in the row menu asks "Delete Runtime Environment? Are you sure you want to delete the runtime environment '<name>'? This action cannot be undone." Deleting removes the registration on the platform; it doesn't reach into your remote infrastructure.
Notes
Deploy an automation before exporting its runtime environment bundle — undeployed automations are skipped.
Give each runtime environment a unique, identifiable name so operators can tell environments apart at a glance.
Keep the environment's password secure, since it protects the exported bundle's contents.
Set environment-specific variable overrides per runtime environment rather than relying on shared values.
Confirm before deleting a runtime environment — the action cannot be undone on the platform, though it doesn't touch your remote infrastructure.