:::meta author=Docs-Team updated=2026-09-03 tags=service-detail,overview,controls,settings
:::
:::breadcrumb Docs > User Guide > Service Detail
:::
:::reading-time
:::
Opening a service leads to its workspace: a slim toolbar, a live control bar, and five tabs that cover everything a running service needs. The page adapts to your permissions — an owner sees all five tabs, while a share recipient sees only the tabs the share grants. This page covers the layout, the live controls, the Overview tab, and the Settings tab; deploys, logs, and the shell each have their own page.
:::toc
:::
Layout and navigation
The top toolbar has a Services button that returns to the list, a Refresh now icon, and the auto-refresh selector with intervals from 2s up to 60s plus Disable auto-refresh. On desktop, a sticky left sidebar lists the tabs in order — Overview, Create deploy, Logs, Settings, Shell — under a summary of the service: name, host, status chip, selected deploy, deploy and volume counts, and the network. On mobile, the same summary collapses into a sticky header, and the round Service sections button in the bottom corner opens a drawer with the five tabs.
:::note
The tab is called Create deploy in the desktop sidebar and Deploys on mobile — same place, same functionality. This guide calls it the Deploys tab.
:::
The live control bar
GlobalServiceControls sits above the tab content and is always visible, on every tab. The identity block shows the service name, its host in monospace with copy buttons, and the status chip. The action row:
| Button | Behavior |
| --- | --- |
| Start | Requests a start. Requires a selected deploy; disabled while the service is busy |
| Rebuild | Rebuilds from the selected deploy. For databases the button is Rebuild DB, and with the force option Rebuild DB (wipe volume) |
| Force cancel | Appears only while a deploy is in progress — stops it immediately and removes intermediate containers/images |
| Stop | Requests a stop |
| Check status | Probes the runtime directly and refreshes the CPU/RAM meters |
| Open | Opens the service URL in a new tab. Disabled for databases, which are not opened in a browser |
The meters on the right show CPU and RAM as live percentage bars with the same green/amber/red thresholds used everywhere. Info chips summarize Deploys: N, Volumes: N, Network: name, Selected: deploy, and the service kind (DB · postgres or App · node).
:::danger
Database services offer a Force re-initialize checkbox. Arming it turns the next Rebuild DB into a destructive operation that wipes the data volume and reinitializes the database from scratch — all data is lost. It exists to recover databases stuck in a restart loop; leave it off for normal rebuilds, which preserve data.
:::
Overview tab
The Overview is the service's identity card, and everything on it is read-only with copy buttons where useful:
• Service details — name, service name (the Docker identifier), host, status, Running as a Yes/No chip, selected deploy with version, created and updated timestamps.
• Database credentials — appears for database platforms (PostgreSQL, MySQL/MariaDB, MongoDB, Redis, Oracle). Sensitive values are masked by default and revealed with a show/hide toggle; each row is copyable. The card includes the Connection string in a monospace block and collapsible connection examples.
• Plan — name, platform, CPU, RAM, storage, and the hourly price.
• Network — name and CIDR when present.
:::warning
Credential visibility is enforced by the server. Share recipients without the View DB credentials rule see an error card instead of secrets — the values never reach an unauthorized browser.
:::
Settings tab