The work

swarm.cpt-technologies.com

The signed-in console for the cluster: what is running, where each hostname is sent, and a plan before anything changes.

You sign in. The bar shows CPT Swarm, or the signed-in company name when one is set, and the page is the dashboard. The figures are the ones an operator watches: services running, approvals waiting, volumes, containers, whether the swarm is active, and how full the disk is. The side list reaches the intent console, services, certificates, monitoring, tests, notifications, networks, containers, cleanup, and the nodes. An administrator also sees domain routing, policy, secrets, users, and the audit log.

Domain routing is how a hostname becomes a site. The group’s public sites, this one included, are reached that way. Certificates can be issued and renewed for those names, including a renewal for one name or for all of them. On the services screen the tabs are services, workloads, and volumes. An operator can deploy a workload, inspect it, read logs, scale it, restart it, or roll it back. The desired replicas are stored, and the cluster is pulled back to them when a service goes missing or the image drifts.

The intent console is the other way in. A sentence such as “list the services and their replica health” becomes a plan of tool steps, with a risk marked on it. Shadow mode only logs that plan. A review tier waits before a change. Autonomous mode can act on a lower-risk plan, and still stops for a high-risk step. There is a dry run that simulates and leaves the cluster alone. Viewers can browse plans. Only an admin can submit or approve. The address on this card is the one the console is moving to.

Want something in this family? Start a conversation. The price is agreed there, not on a rate card.