Skip to main content
Click any pod name from the dashboard to open its detail page. The tab bar shows Overview, Logs, Metrics, Domains, Env, Services, Git, Backups and Settings. The less-used tabs - Terminal, Events, SSH, Dev Tools and Feedback - sit under More at the end of the bar. A pod that runs a Docker image has an Image tab in place of Git. The header carries the pod name, its status, app or runtime, and plan, plus an actions menu (start or stop, restart, reload, delete).

Overview

The overview opens with a status card: whether the site is up, its address with a copy button, and Visit site and Use your own domain buttons (Manage domains once it has one). When the pod is stopped, the card has a Start pod button. Below it:
  • Next steps - a short checklist: use your own domain, deploy from GitHub, turn on automatic backups, and add a database (marked optional). A 1-Click App pod skips the GitHub and database steps, and a worker skips the domain step. The checklist disappears once every step on it is done, the optional one included.
  • How it’s doing - CPU, memory and disk in plain words (“Plenty of room”, “Filling up”, “Almost full”), with shortcuts to edit code, logs, env and secrets, the terminal, domains and support.
  • Plan and usage - live CPU, memory and storage against the plan, with Upgrade, Downgrade and Usage history.
  • Recent activity - the latest events, with a link to all of them.
  • Work on your code - buttons for the Web IDE and Terminal, and the full SSH command.
  • Details - runtime, region and creation date.
The Plan and usage card shows live CPU, memory and storage use against the pod’s plan. Storage is measured in GB, the same unit plans are sold in, against the pod’s enforced disk limit. Every pod’s disk size is a hard limit: when it is full, the app can’t write anything new. From 80% the card shows a warning, and the owner gets an email at 80% and again at 95% with what to clear and which plan would fit. See Pod disk is full. The card also shows Bandwidth this month: the traffic the pod has sent out since the start of the calendar month (UTC). If that is above typical use for the pod’s plan, a note says so. Bandwidth is not capped, throttled or billed. For a Node.js pod, the details also carry a Node version picker that switches the pod’s Node major in place - see Node.js. If the pod is running but your app isn’t reachable, an amber banner appears here with the Deploy Doctor verdict: what’s wrong, the evidence, the fix, and an Apply fix button where InstaPods can do it for you. On a 1-Click App pod the banner has no verdict; it suggests restarting the pod, and getting in touch if the app went down right after an update. A pod created by uploading a ZIP also gets an Update from ZIP card, which replaces its files and rebuilds in place - see Import an existing app.

Domains

Manage custom domains mapped to your pod.
  • See the pod’s built-in address next to its custom domains, with each domain’s status in plain words (“Waiting for DNS”, “Live”, “SSL active”)
  • Add a new domain with CNAME or TXT verification. The panel shows the exact record to create, each value with a copy button
  • Click Check DNS to check a pending domain right away (InstaPods also checks on its own)
  • Remove a domain mapping
See Custom Domains for the full guide.

Services

Install and manage database services inside your pod.
  • View installed services with their status and version
  • Click Add database to install MySQL, PostgreSQL, or Redis
  • Copy connection credentials (the password stays hidden until you reveal it) and a ready-made terminal command
  • Remove a service. You type the service name (for example mysql) to confirm, because removing it deletes its data
Services require the Build plan or higher. Launch plan pods show an upgrade prompt.
See Services Overview for details on each database.

Git

Connect a Git repository and manage deployments.
  • Connect a GitHub repository or any Git URL
  • View deployment history with status and commit info
  • Click Deploy now to deploy by hand, or roll back to an earlier deploy (it asks first)
  • View build logs in a terminal-style viewer
  • Change deployment settings, such as auto-deploy, in a dialog, or disconnect the repository
See Git Deployment for the full guide.

Env

Edit the pod’s environment variables in the browser, one KEY=VALUE per line. Save changes writes them to the pod’s env file and applies them to the running app - existing keys are updated in place, and lines you delete are removed. See Environment Variables for the CLI and API equivalents.

Backups

The tab has three panels: Back up now (take a backup with an optional note, or import one), Automatic backups (turn the schedule on or off, and pick its frequency and how many to keep), and the list of backups, each marked Manual, Automatic or Imported. Restoring or deleting a backup asks you to type the pod’s name first. See Backups for what is captured, plan retention limits, and the restore semantics.

SSH

SSH connection information and key management.
  • Copy the ssh, scp and sftp commands for the pod (ssh instapod@host -p PORT)
  • List authorized SSH keys
  • Add or remove SSH keys (removing one asks first)

Logs

View container and application logs.
  • Filter by service. The list matches the pod: its runtime, its web server and any databases you added
  • Choose how many recent lines to read (Last 100 lines and up)
  • Search logs - a regular expression, matched across the lines you chose. Matches are highlighted
  • Live - refresh every few seconds while the tab is open
  • Wrap long lines, copy the output, or download it as a file
A status line under the logs counts the lines and how many of them look like errors. Error and warning lines are tinted.

Metrics

The latest reading as four cards (CPU, memory, disk against the pod’s disk limit, and network in and out), then a chart of each over time. Hover a chart, or use the arrow keys, to read a value. A gap in a line means the pod was stopped. Memory is normally the pod’s working set: what its processes actually hold (plus any swap), as a share of the plan’s memory. Reclaimable file cache is left out, so the graph doesn’t climb towards 100% just because the pod has read a lot of files. On the rare sample where that reading isn’t available, the total including cache is charted instead. Readings from before 12 November 2026 still include the cache, so a longer graph shows a step down at that point.

Events

A timeline of pod lifecycle events, grouped by day:
  • Creation, start, stop, restart
  • Resize operations
  • Service installations
  • Backup, restore and app-update activity
  • Error events

Feedback

Comments left by visitors through the pod’s shareable feedback widget. Visible to controls who sees the widget - Everyone, or Only people with the link. You can also reset the feedback link, which stops anyone holding the old one from submitting.

Dev Tools

Install and manage AI coding agents inside the pod: Claude Code, Codex CLI, Aider and OpenCode. Installing one puts the agent’s command on the pod’s PATH, so you can run it from the Terminal or over SSH against your own code. You sign in to the agent yourself the first time you run it - InstaPods never holds those credentials. The pod must be running to install an agent, and the install happens in the background, so the entry sits at “installing” for a minute or so. See AI Coding Agents for the API.

Terminal

A full shell in the browser, attached to a persistent tmux session so your work survives a disconnect. See Web Terminal.

Settings

  • Pod type - choose Web pod or Background worker. A worker has no public URL; switching to it asks first, because the site goes offline. A 1-Click app pod always stays a web pod. See Worker Pods.
  • Transfer ownership - hand the pod to someone else’s team. See Transfer a pod.
  • Delete pod - destroys the pod, its files and its databases, and stops billing for it.