Skip to Content
Documentation
Getting startedNavigate the dashboard

Navigate the dashboard

The dashboard keeps operational resources in the left navigation and the current workspace and project near the top of that navigation.

Main areas

AreaWhat you do there
DashboardSee the current project context and a summary of resources
ApplicationsSearch applications, deploy a new app, and open application details
Resource poolsConnect your own server for free management, inspect capacity, or review optional hosted pools
cPanelManage the separate free legacy-hosting accounts, when available
IntegrationsConnect GitHub and manage project access to private registry credentials
MembersInvite collaborators and review roles and invitation status
BillingReview optional paid hosted services, renewals and wallet deposits
SettingsUpdate your profile and configure two-factor authentication

Switch context safely

Before a create or change action, verify both the workspace and project. A workspace controls people, billing, and integrations. A project controls where applications and resource pools are organized.

Use names that reveal purpose without exposing sensitive information. production, staging, and payments are useful context; credentials and customer data are not.

Application details navigation

An application has these primary tabs:

  • Overview — source, runtime, capacity, endpoint, and timestamps;
  • Deployments — release history and status;
  • Analytics — resource and available HTTP traffic history;
  • Domains — custom hostnames and DNS verification;
  • Logs — live standard output and error output;
  • Terminal — an interactive session for an active application;
  • Settings — source, build, resource, and runtime configuration.

The Open application action appears when the application has a public endpoint. Otherwise, View logs is the quickest path for checking startup behavior.

Refreshing state

Provisioning and deployments are asynchronous. Use Refresh when a state has not updated, but avoid repeatedly submitting the original create or save action. A duplicate submission can create an unintended release or resource.

Permission-aware controls

Your role can affect what you can see or change. If an action is unavailable, confirm you are in the intended workspace and ask a workspace owner or administrator whether your role includes the required access. UI visibility is not a substitute for authorization; the platform validates actions when they are submitted.

Last updated on