Environments and machines
Switch between stages and servers; the list is edited inside the app itself.
Product
Reaper
One screen instead of SSH, systemctl and a dozen tabs
Shipped
The challenge
What the client faced
The task the client came with and why it could not be solved before.
A backend of dozens of services and hundreds of concurrent processes is operated from a terminal: to see what failed and restart the right instance an engineer assembles the picture from SSH sessions, systemctl and logs across several machines. That takes minutes an incident does not have.
Mechanics
What is inside
The mechanics the product is built from.
Services and processes
Status, memory use, uptime and instance count; start, stop, restart and add an instance in one click.
Logs in real time
A stream for the selected process and a combined Live Log across every service in the environment.
Data and policies
Point edits to entities with change tracking, and allow or deny switches per route: without database access.
Bulk operations
Update and restart every service in an environment with progress and confirmation.
Pipeline
From data to action
From data on the servers to a one-click action: what happens in between.
-
01
An agent on the servers
The Reaper agent runs on the machines of an environment: it is the source of data about services and processes and the channel for control commands.
-
02
The panel builds the picture
Reaper shows environments and machines, a list of services with the number of running processes, memory use and uptime.
-
03
The engineer sees the problem
Live status updates and a Live Log across every service at once: a failed process is visible without logging into the machine.
-
04
An action on a specific process
Start, stop, restart or add an instance: for the chosen process and instance, not for the whole server.
-
05
The command goes through the agent
Processes are managed by systemd: the same mechanism the environment already uses.
-
06
Bulk operations with confirmation
Updating and restarting every service comes with progress and confirmation: one service first, then the rest.
Where it sits
Where it sits
Reaper does not replace the infrastructure; it manages it through the existing mechanisms.
Environment infrastructure
What it manages
Service processes under systemd, the route list and KV storage in Consul, the environment host API, code repositories.
Reaper
Web panel
Processes, logs, access policies, entity data and bulk operations in one window.
Engineer's workstation
Browser
No separate client to install: light and dark themes, interface in Russian.
Outcome
What changes on a shift
What changes on a shift.
One screen instead of a set of tools
Processes, logs, policies, data, bulk operations and code updates: in a single interface.
Speed of reaction
Statuses and logs update in real time, and an action takes one click.
Less risk
Destructive operations require confirmation and run against a specific process and instance, not the whole server.
No direct access to the infrastructure
Editing data and policies, updating services: without SSH and without connecting to the database.
A transparent picture of load
Instance count, memory use and uptime per process are visible on one screen.
Laid out for daily work
Scrolling is local inside panels rather than the whole page: dense screens for shifts and releases.
Technology
What it is built on
The platform, the stack and the devices the product runs on.
Technologies
- systemd
- Consul
- Bitbucket
Platforms
- Web
Links
Where to look
The product website and the materials about it.
Live demo
Demo access is provided on request.
Need a product like this under your brand?
We will deploy it white-label, tune the processes and onboard your team.