The server area is split between provider-level infrastructure and application-level resources.
The list page should stay focused on provider VPS inventory. App runtime details belong behind each server where deployments, domains, databases, and backups can be managed with enough context.
Server list
The /dashboard/servers page should behave like an inventory table.
Recommended columns:
| Column | Source |
|---|---|
| Server | Local record with customer and role |
| IP address | Provider public IPv4 |
| Status | Local sync state and provider lifecycle |
| Expiration date | Billing and renewal context |
| Actions | Renew, manage, and overflow actions |
The server list should not include explanatory API panels on the right side. The user came to inspect and manage infrastructure, so the table should be the main surface.
Server detail
The server detail page should expose sections that can actually be managed through the connected systems:
| Section | System |
|---|---|
| Overview | Local record plus provider facts |
| Applications | Coolify |
| Databases | Coolify |
| Domains and TLS | Coolify plus DNS provider |
| Deployments | Coolify |
| Backups | Coolify or backup provider |
| Access and firewall | Provider plus OS automation |
| Provider server | Hetzner or Netcup |
| Server settings | Local dashboard configuration |
Avoid generic hosting-menu items that do not match the Techservice stack.