Dashboard

The Oblien dashboard provides a visual interface for managing VMs, monitoring usage, and configuring your account.

Access it at oblien.com/dashboard.

VM list

The main dashboard page shows all your VMs with:

Status indicator - Ready, Paused, Hibernated, Stopped and operation progress such as Hibernating or Resuming
Quick actions - Start, stop, restart, delete
Resource summary - CPU, memory, disk allocation
Image - Base image used
Uptime - How long the VM has been running

Create a VM

Click Create VM
Select an image (e.g., oblien/node:24, oblien/python:3.13)
Configure resources (CPU, memory, disk)
Set mode (permanent or temporary)
Optionally set a startup command, environment variables, and network rules
Click Create

The modal shows real-time quota validation - you'll see warnings if your resource selections exceed your plan limits.

Filtering and search

Filter by status: Running, Stopped, Paused, All
Search by VM name or ID
Sort by creation date, name, or status

VM detail

Click any VM to open its detail view with multiple tabs:

Overview

Current status and uptime
Resource allocation (CPU, memory, disk)
Network configuration
Quick action buttons
A namespace link that opens the VM's namespace

See who changed the VM, when, and the outcome. Filter by action, actor, outcome or time. Audit history is available during preparation and while stopped. The Audit item in the dashboard sidebar shows history across your VMs, including VMs that have been deleted. See Audit history.

Terminal

A full browser-based terminal connected to the VM via WebSocket. Features:

Scrollback buffer - Scroll through previous output
Search - Find text in terminal history (Ctrl+Shift+F)
Resize - Terminal adapts to your browser window
Reconnect - Auto-reconnects on connection loss
Terminal history - Set retained output and browser scrollback limits, or clear output without stopping the shell

Logs

View VM logs in real-time:

Boot logs - VM startup and initialization
Command logs - Output from startup commands
Workload logs - Per-process logs for managed workloads

Logs stream via SSE (Server-Sent Events) and update in real-time.

Each workload's log viewer includes Log retention and Clear stored logs. The default is up to 20 MiB and 7 days per workload. Clearing deletes retained output while the process continues running. The browser keeps a bounded recent tail; pause disconnects the viewer, and resume loads the retained history. See workload log controls.

Metrics

Live monitoring charts showing:

CPU usage - Percentage over time
Memory usage - MB used vs allocated
Disk I/O - Read/write throughput
Network - Inbound/outbound traffic

Metrics update via SSE streaming for real-time visibility.

Files

Browse and manage the VM filesystem:

Navigate directories
View file contents
Upload files (base64 encoded)
Check disk usage

Network

Configure networking from the UI:

Toggle internet access
Manage firewall rules (ingress/egress)
Expose ports for public access
View preview URLs

SSH

Enable or disable SSH access:

Toggle SSH on/off
Set authentication method (password or key)
View connection command
Copy SSH details to clipboard

Workloads

Manage long-running processes:

View active workloads
Start/stop individual processes
View per-workload logs
Monitor workload status

Snapshots

Use the power controls to choose how a VM stops:

Pause freezes execution and keeps RAM allocated. Resume continues the same process.
Hibernate saves RAM and virtual-device state to disk, then releases the running process and memory. It shows Hibernating, then Hibernated. Resume restores the saved session.
Stop shuts down the VM. Start performs a new boot from its persistent writable disk.

Hibernate uses the existing snapshot API. It is disabled when the runtime cannot safely save memory, including nested KVMs such as the current Mac image. Hover over the disabled control for the reason. Progress persists across a dashboard refresh.

Disk archives are separate backups available through the Snapshots & Archives API.

Pages

The VM's Pages tab lists static Pages exported from that VM. Choose Create Page to export a build output folder with the VM already selected. Exporting requires a running VM; existing Pages stay available after it stops. The VM owner manages these deployments.

The same tab includes Pages created through the API or SDK. Cards show the namespace, source VM, status, public URL, and creation/update dates. Open a Page for its Deployment overview, Domain & SSL, Analytics, and optional Path rules, or use Refresh to check for new deployments. Details remain inside the source machine. If that machine has been deleted, open the retained Page from Routes. There is no separate Pages sidebar entry. See Pages.

Routes and analytics

Routes lists every registered public hostname owned by your account: VM URLs and ports, static Pages, edge proxies, and tunnels. Filter by resource type, status or namespace, or search by hostname. Disabled routes and routes with no recorded traffic remain in the inventory.

Each hostname opens its own Analytics, with an overview, selectable time range and live request log. Root domains and www aliases are separate hostnames. The Page, VM or tunnel link opens the resource that owns the route. Existing Edge Proxy hostnames remain in the inventory, but Edge Proxy management is available through the SDK or API rather than a dashboard screen. Old /dashboard/analytics links redirect to this view.

Route-list traffic counters cover recorded history. In the detailed view, overview cards and the chart use the selected range; country data covers at most the last 24 hours, and recent requests are the latest captured records.

Usage

Usage separates spending from resource allocations:

Account credit balance shows the wallet balance and links to Add credits.
Credit spending shows recorded deductions over 7, 30 or 90 days, with an optional namespace filter. Expand Show spending breakdown for paginated namespace/service rows. The total includes every matching record, not just the visible page. Deductions include usage and prepaid purchases; refunds, top-ups and cash invoices are separate in the credit ledger and Payments screens.
Account VM allocations shows owned VM counts, per-VM maximums and both running and owned resource pools. These are allocated CPU, RAM and disk, not actual utilization. Open a VM for live metrics.
Account edge usage shows traffic for its actual billing period and active Page and tunnel counts. A custom-domain alias does not use another resource slot. Expand the namespace breakdown to inspect its resources.
Usage discounts shows the current UTC month's cap savings and prepaid coverage using the backend's billing comparison.

The spending namespace/period controls apply only to credit spending. Resource limits remain account-wide, and edge traffic and cap savings show their own periods. Namespace policies may impose lower limits; open Namespaces to inspect them. Unlimited and not-included allowances are labeled explicitly. If a read fails, its section shows a retry control instead of a zero balance or an empty inventory.

Pages, Routes and account billing views use your personal account. Shared VM access does not grant access to the owner's account-wide Pages, route traffic or wallet data.

View your Client ID
Rotate your Client Secret
View API key creation date

Credits

Monitor your credit balance and purchase additional credits from the dashboard. See the Pricing page for plan allowances and credit packages.

Notifications

Configure alerting preferences:

Low credit balance alerts
VM status change notifications
Usage threshold warnings

When approaching plan limits, a banner appears at the top of the VM list showing:

Pool usage (owned and running)
Number of VMs vs limit
Which resource is the bottleneck
Link to the Pricing page to upgrade

Keyboard shortcuts

Shortcut	Action
`Ctrl+K`	Quick search / command palette
`Ctrl+Shift+F`	Search in terminal
`Ctrl+C`	Copy selected terminal text
`Ctrl+V`	Paste into terminal