PDM

Capabilities ​

Stands and their state ​

Every platform environment is collected into one tree: a cluster, and stands inside it. Each stand shows its state: “Operational”, “Degraded”, “Down” or “Unknown”. Stands can be marked as favorites so they are always at hand. A stand has its own page with its state, its settings and its service addresses.

Learn more: Stands and Stand page.

Stand configuration ​

Stand settings are shown not as a flat list of variables but per application: a row is an application, and inside it are its parameters split into sections. For every parameter you see the platform-wide value and, where one is set, the stand's own value. Edits are not applied immediately: they pile up as a before-and-after list and are applied all at once.

Learn more: Stand configuration.

Application builds and deployments ​

An application can be built straight from PDM: pick a branch, a version or a ready image tag and trigger the build. Everyone sees their own builds; other people's builds require a permission. Every build carries a link to its GitLab pipeline. The build result can be put on a stand right away as the application's new version.

Learn more: Applications, Application actions and Builds.

Releases across many stands at once ​

A release is a single agreed change of settings and versions that is rolled out not to one stand but to many. The release wizard walks you through three steps: what is changing, what to do with stands where a value was overridden by hand, and the final confirmation. A started release stays in the history together with the set of changes it carried.

Learn more: Releases, Creating a release and Release rollout.

Workspaces: watching operations run ​

Every long operation — a settings deployment, a build, a release — runs as a workspace: a sequence of steps with their own statuses, logs and results. Triggering it returns instantly, and from there you follow the operation separately: you can see which step it is on, where it failed and what exactly went wrong. The whole operation is kept, you can come back to it later, and its link can be shared with a colleague.

Learn more: Workspaces and Running and watching.

Availability monitoring ​

Stands are polled regularly, and PDM counts how many of a stand's applications are actually running out of those expected. That gives the current status, uptime over a period as a percentage and a feed of status changes. “Down” and “No data” are kept apart — if the cluster did not answer, that is not counted against the stand as downtime. Availability history is kept for a limited time.

Learn more: Stand monitoring.

Working with an AI agent ​

PDM can be connected to an AI agent — you can then ask it about the state of stands, application configuration, releases and builds, and have it make changes for you. Access is granted through a confirmation in the browser, the agent never receives your password, and it works strictly within your own permissions. Changing operations require an explicit confirmation by a human, and the access you granted can be revoked at any time on the active sessions page.

Learn more: AI agents and Connecting an agent.

You don't see everything at once

Some buttons and sections appear only if you have the matching permissions, and permissions may be granted for individual stands or clusters only. If a button you need is missing, it is most likely a matter of permissions: see Permissions.

What's next ​