Enterprise Control Plane
These guides cover everything you need to work with Enterprise Control Plane (ECP): core concepts, getting started, the day-to-day tools (Compare, Merge, Deploy), monitoring, administration and reference.
Introduction to ECP
What this covers
Enterprise Control Plane (ECP) is the control surface for governed configuration delivery. It centralises tenant management, deployment pipelines, configuration promotion, access control and audit into one place, so delivery teams can move configuration between Fenergo tenants without relying on scattered runbooks or manual handoffs.
The ECP workflow
Configuration typically moves through a deployment pipeline's stages from left to right — for example, Dev → SIT → UAT → Pre-Prod → Prod. You pull configuration into a source tenant, compare it against a target to understand the differences, then either merge selected changes or deploy whole files forward to the next stage. Every action is recorded in the Activity Log for audit.
Which tool do I use?
| Tool | Use it to | Writes changes? |
|---|---|---|
| Compare | Inspect two tenants side by side and see exactly what differs. | No — read-only |
| Merge | Apply selected paths from one tenant's config file into another. | Yes — selective |
| Deploy | Push whole config files from a source tenant to one or more targets. | Yes — full files |
As a rule of thumb: Compare to understand, Merge for surgical changes, Deploy for full promotion.
Prerequisites & access
ECP uses three roles:
- Fenergo Admin — Fenergo staff role with full access across all organisations, environments and settings.
- Admin — manages users and deployment pipelines within their organisation.
- Member — works within the deployment pipelines they've been granted.
Access is granted per deployment pipeline. A new Admin is automatically granted every pipeline in the organisation; a Member starts with none until granted.
Before you can move configuration you'll also need:
- An organisation to hold your deployment pipelines (created by Fenergo on request).
- At least one environment granted to your organisation — this is required when registering tenants, not for promoting configuration between tenants that are already set up.
Core Concepts
A short reference for the building blocks that appear across every ECP feature. Read this once and the rest of the guides will make more sense.
Organisations
An organisation is the top-level container in ECP. It holds deployment pipelines and the users who manage them. Organisations are created by Fenergo — each customer team operates within one, and access to an organisation grants visibility of every deployment pipeline within it.
Admin users can belong to more than one organisation. When an Admin has access to multiple organisations, an organisation switcher appears in the interface, allowing them to move between organisations without signing out. Members belong to a single organisation only and do not see the switcher.
Deployment Pipelines
A Deployment Pipeline is an ordered set of stages (e.g. Dev → SIT → UAT → Pre-Prod → Prod) that tenants are assigned to and promote configuration through, in that order. Deployment Pipelines can be nested into parent/child hierarchies to model more complex promotion paths. Stages carry a colour that appears on badges everywhere the stage is shown.
Tenants
A tenant is a Fenergo tenant registered in ECP, bound to one environment. ECP connects to each tenant using credentials stored against it, and uses that connection whenever it pulls or pushes configuration. A tenant belongs to a deployment pipeline and occupies one stage within it.
Config files
ECP pulls configuration files from each tenant and organises them into parent domains and sub-domains. It stores and works with the latest active version of each file. Files can be refreshed on demand — a refresh queues a background pull from Fenergo and updates the stored content when complete.