Dashboard & Access
One control surface around standard Kubernetes.
Use the Asergo Dashboard to see platform status, upgrades, logs, metrics, DNS, storage, invoices, and tickets — while your team still deploys through standard Kubernetes workflows.
Three ways in.
The dashboard, standard Kubernetes access, and direct engineer contact. Each path serves a different need. All three are available from day one.
Asergo Dashboard
The managed layer, visible
A web console that surfaces everything Asergo manages: cluster health, node status, scheduled upgrades, operational logs, metrics, DNS records, storage, invoices, and support tickets. One place to see what is running and what is changing.
Kubernetes access
Standard tools, no wrapper
Your team deploys with kubectl, Helm, Argo, or whatever Kubernetes tooling it already uses. RBAC-scoped credentials, namespace isolation, and standard API access. The platform does not intercept or alter Kubernetes behaviour.
Direct engineer access
Email an engineer, not a ticket queue
When something needs attention at the platform layer, you contact the engineers who built and operate your cluster. No support tiers, no ticket routing. The same people who provision the hardware answer the email.
Inside the Dashboard
What you see when you log in.
The dashboard consolidates the operational surface into a single web console. Every section reflects live state — not a cached snapshot.
Cluster health
Node status, control-plane state, and resource allocation at a glance.
Upgrade timeline
See upcoming Kubernetes and OS upgrades, approve scheduling, track rollout.
Centralised logs
Search pod and node logs. Filter by namespace, time, or severity.
Metrics
CPU, memory, disk, and network across nodes. Historical trends and current load.
DNS management
Add, edit, and remove DNS records for your applications from one interface.
Storage and backups
Volume status, backup schedules, and restore history.
Invoices
Monthly invoices, line items, and billing history. One fixed price, visible.
Support tickets
Open, track, and resolve requests. History stays attached to your cluster.
Kubernetes Access
Your team uses Kubernetes the way it already knows how.
RBAC-scoped credentials. Namespace isolation. Standard API. No proprietary abstraction layer between your manifests and the scheduler. The tools your CI/CD pipeline already uses work without modification.
kubectl
Full API access with RBAC-scoped kubeconfig
Helm
Charts deploy the same way as any other cluster
Registry integration
Cluster is pre-authenticated to the private Harbor registry
Ingress
Standard ingress controllers, TLS termination included
RBAC
Namespace-scoped access, OIDC-backed identity
CI/CD
GitHub Actions, GitLab CI, Argo CD — bring your pipeline
The dashboard does not replace Kubernetes or hide it behind a proprietary wrapper. It makes the managed layer visible.
Your team deploys through standard Kubernetes. The dashboard shows what Asergo manages underneath — hardware state, upgrade schedules, operational logs, and the things your team should not need to build tooling for.
Your infrastructure backlog, handled.
From first conversation to running cluster, typically five working days. Fixed monthly price, dedicated hardware, engineers you can reach.