ExecLayer

One control plane. Every automation.

ExecLayer runs on your infrastructure. Schedule, approve and watch Python scripts and workflows from one plane, while the workers that execute them stay on your servers.

Request a demo Explore ExecLayer

Your infrastructureControl plane and workers stay inside the organisation
Approved versionsDevelopment, UAT and Production, promoted on purpose
A record of every runVersion, worker, authoriser, status, output and log

control plane · illustrative

Illustrative runs. No live system is connected.

Scripts do not become a system on their own.

The failure is usually not the script. It is that nobody can see which copy ran, on which server, or who allowed it.

Scattered scripts

Automations live in personal folders and shared drives. The copy on a server is not the copy someone just edited.

Cron with no owner

A schedule fires on a machine. When it fails, the only signal is a missed file or a quiet log.

Servers that do not share a view

Each machine runs its own jobs. There is no queue, no assignment and no single place that shows what is running.

Manual recovery

A failed job waits for a person to notice, find the right version and start it again by hand.

A control plane, and workers on your servers.

Administration stays in one place. Execution stays on the machines you choose. A worker runs only an approved package.

The control plane is a Go service, a PostgreSQL database and a Vue interface. Operators edit scripts in the browser, schedule work, queue it, keep versions and secrets, and read the monitoring view.

Workers installed on your servers execute the authorised package locally. The plane assigns work, records status and keeps policy. It does not replace the servers where the business data already lives.

Tell us which automations you need under one plane. We reply with whether ExecLayer fits the installation.

Request a demo

What the plane governs.

A script becomes a versioned package. The plane decides when it runs, where it runs, and what is kept afterwards.

Schedule and trigger

Run on a schedule or from an event. The queue holds the work until a worker is assigned.

Workers

Add workers across servers. A failure on one worker stays on that worker. The plane still shows the status.

Versions and approval

Each published script version is immutable. Production receives only a version someone promoted.

Workflows

Chain steps, map the output of one step into the next, retry a failure, or cancel a run that should stop.

History and logs

See what ran, when, on which version, and whether it succeeded. Open the log for that run.

Roles and secrets

Role-based access for the people who edit, approve and operate. Secrets stay encrypted on the installation.

Failure analysis and controlled agent runs are planned for a later release. They are not part of ExecLayer today.

The boundary stays yours.

ExecLayer is licensed onto the customer's infrastructure. Business data, execution and operational control remain inside that boundary.

On premises

The control plane is installed for the client. It is not a shared cloud tenancy for the automations.

Who may act

Roles limit who can edit a package, promote a version, cancel a run or read a log.

Secrets

Credentials the automations need are encrypted on the installation, not pasted into the script.

Audit

The record shows the version, the authoriser, the worker, the status and the outputs. That is the trail for a review.

Licensed where you run it.

One control-plane installation for the client. Environments and workers are part of that installation. A provider can publish packages without taking the infrastructure.

01Install the plane
The licensed control plane goes into the client's environment, with its database and management interface.
02Separate the environments
Development, UAT and Production each keep their own approved version.
03Place the workers
Workers go on the servers that should execute the packages, and report status back to the plane.
04Publish, then promote
A provider ships an approved package. The client promotes it. The provider does not take ownership of the data.

Built for teams that already run critical automations.

The licence is enterprise software: a control plane per client, then the environments and workers that client needs.

Enterprise IT

One plane for the automations the department already depends on, with a record of each run.

Automation providers

Agencies and managed service providers publish and maintain approved packages across client installations.

Banking and finance

For institutions that need the execution and the data to stay inside their own infrastructure.

Healthcare

For organisations that cannot send operational data to a shared automation cloud.

Other operators

Any business with enough critical automations that cron and shared folders are no longer enough.

Questions

Before you request a demo.

Where does ExecLayer run?

On the customer's own infrastructure. The control plane and the workers stay inside the organisation, with the data and the execution environments.

What does it execute?

Approved Python scripts, business automations and workflows. A provider packages a version. The customer promotes it before production.

How do Development, UAT and Production stay apart?

Each environment has its own approved version. A version moves forward only through a controlled promotion.

What is recorded for a run?

The version that ran, when it ran, which worker ran it, who authorised it, the status, the outputs and the log.

Can a provider manage automations for a client?

Yes. The provider publishes and maintains approved packages. The client keeps the installation, the workers and the data.

Are AI agents included?

No. The platform is shaped so failure analysis and controlled agent runs can be added later. They are not in this release.