Environments

An Environment is the runtime location where workflows are executed.

Workflows are created and managed inside the SolutionEngine interface, but they do not execute there. Execution always happens inside an Environment. This separation allows the platform to manage multiple runtime locations while keeping design and deployment centralized.

An Environment runs as a Docker container. Any machine capable of running Docker can act as an Environment.

Typical examples include:

• A local development machine
• A cloud virtual server (such as an AWS EC2 instance or similar VPS)
• An on-premise server inside a private network
• A small edge device such as a Raspberry Pi
• An accelerated device such as a Jetson Nano

The platform does not restrict the hardware. The only requirement is that the machine can run Docker and reach the configured API endpoint.

Creating an Environment

Before installation, you must create an Environment entry inside your project.

When you create it:

• A unique ENV_ID is generated.
• This identifier binds a running agent to that specific Environment.
• The platform uses this identifier to know which workflows should be synchronized to that machine.

Each machine must have its own unique ENV_ID.

Do not reuse the same ENV_ID across multiple machines.

Installing the Environment Agent

After creating the Environment, the platform provides a Docker command similar to the following:

docker run -d \
  --name solutionengine_agent \
  --restart unless-stopped \
  --pull always \
  -e CLOUD_API_URL=https://api.solutionengine.io \
  -e ENV_ID=ENV_ID \
  kasunk/solutionengine_agent:latest