Skip to content

Features

Everything a risky change needs, in one platform

Hegemony runs long infrastructure changes as workflows: with approvals, with a record of what ran on every device, and without losing its place when something restarts.

Build workflows

The start form of the Announce service prefix flow, filled in

Visual flow editor

Draw a workflow as a graph of steps, or edit it directly as YAML. Work in a draft, commit it as a new version, and compare versions.

Branches, loops and parallel paths

Decide, repeat and fan out inside one workflow. Loops can run one by one or in parallel.

Reusable flows

Run one flow as a step of another, so common procedures are built once.

Run forms

Design the form an operator fills in to start a run, with checks on every field.

Three ways to start

Start a run by hand, on a schedule, or from another system with an incoming webhook.

Run limits

Limit how many runs of a flow are active at once and how often they may start.

Run them reliably

Live reachability graphs for two edge routers during a maintenance window

Runs that survive restarts

Runs execute on Temporal. They continue after a restart and can wait for days for a maintenance window or a device reload.

Maintenance windows

Start and approve a run ahead of time. It does its work only inside the maintenance window you set.

Approvals

Pause a run until a person approves or rejects it. Pending requests wait in one inbox.

Ready-made steps

SSH commands, network device commands, Ansible, Terraform and OpenTofu, HTTP requests, NetBox, and DNS, HTTP and TLS checks.

Any tool in a container

Run any tool in an isolated container, and limit which network addresses it may reach.

Managed Terraform state

The platform stores, locks, versions and encrypts Terraform and OpenTofu state.

Connectivity monitors

Watch devices in the background during a change, with live tables and graphs.

See and prove what happened

The audit log with run starts and approvals

Live progress

Follow the output of every step while the run is in progress.

Evidence

Keep a record of what actually ran on each device, together with the files a step produced.

Audit log

A record of who did what and when, with filters.

Security and access

The organization switcher with four organizations

Single sign-on and roles

Log in through Keycloak. Six roles separate building, running, approving and auditing. Sensitive actions ask for a fresh sign-in.

Organizations

Keep several teams or customers apart on one installation, each with its own flows, devices and secrets. Copy flows from one to another.

Secrets stay in a secret store

The database keeps only references. Use the bundled OpenBao, HashiCorp Vault or 1Password. Secrets are hidden in step output.

Trusted hosts and certificates

Each organization manages the SSH host keys and the private certificate authorities it trusts.

API tokens

Tokens let scripts and other tools call the API.

Inventory and integrations

The device inventory with devices from a local and a Git source

Inventory

Manage devices and sites in Hegemony, or bring them in from NetBox or a Git repository. Target devices by hand or by a query.

Git

Keep flows and their attached files in Git repositories, and sync them with push and pull.

Configuration Exchange

Export and import the platform configuration as YAML, and back it up to Git on a schedule.

Notifications

Email, Slack, Microsoft Teams, Webex, Discord, Telegram, Pushover and outgoing webhooks.

File repositories

Keep large files on S3-compatible storage.

Plugins

Steps, inventory sources, notification channels and secret stores are plugins, so you can add your own.

Roadmap

Where Hegemony is heading. These items are planned, not built yet, and the list is not a schedule or a commitment.

Device software upgrades

Steps that stage an image, install it, verify the running version, and roll back on failure.

More platforms

Support for more platforms: network devices, servers and other systems.

Windows hosts

Built-in WinRM (Windows Remote Management) support for running commands on Windows hosts.

Short-lived credentials

Credentials issued for one run, such as short-lived SSH certificates and one-time passwords.

Approvals from other tools

Approve or reject a waiting run from ServiceNow, Jira or a chat tool.

More checks

An SNMP check, and more connectivity checks such as TLS handshake, SSH banner and NETCONF.

Workers in separate network zones

Run steps on workers inside a separate network zone, such as a DMZ. The worker connects out to the platform, so the platform needs no inbound connection into the zone.

VM templates for vCenter

Build VMware VM templates in a flow, store them in Hegemony, and let vCenter subscribe to them as a Content Library.

Released as open source under the AGPL-3.0-or-later license. Development is sponsored by Rexonix s.r.o. Contact — [email protected].