Skip to content

The dashboard

The dashboard at app.managed.dev is where you create sites, open and promote environments, and read security and performance data. This page orients you on where each thing lives so the rest of the guides can get straight to the how. Everything here also has an API and CLI equivalent.

The sites list is the landing screen. It shows every site your current team can see, grouped by project, with a status badge, the active production release, and a quick link into each site.

The app.managed.dev sites list: a left rail with the team switcher and project filters, and a grid of site cards each showing the site name, primary domain, runtime badge, a green “production healthy” status, and the count of active preview environments.

The team switcher in the top-left changes which team’s sites you’re viewing; New site in the top-right starts the create flow.

Opening a site reveals five tabs. Each maps to a section of these docs.

  • Overview — the site’s home: primary domain, the active production release, a Resources box (storage, environments in use against your plan limits), and recent activity. Start here to see a site’s health at a glance.
  • Environments — every environment for the site: production, staging, and each preview, with status badges, preview URLs, and promote / rollback actions.
  • Insightsobservability: web vitals and p95 latency, logs, traces, and the requests view, scoped per environment.
  • Security — the security pipeline for the site: WAF and rate limiting, Patchstack virtual patching, malware scans, headers and allowlists, and the Blocks view of denied requests.
  • Settings — the git remote and branch routes, custom domains and TLS, config and secrets, and SSH access.
A site detail page with the five tabs (Overview, Environments, Insights, Security, Settings) across the top, Overview selected, showing the primary domain, the active release hash, a Resources box with storage and environment usage bars, and an activity feed of recent deploys.

Selecting an environment opens its own page — the working surface for a single copy of the site. From here you can open the preview URL, trigger a deploy, restore a snapshot, open a magic-link session into wp-admin, copy the SSH command, and read that environment’s logs and traces. Production, staging, and each preview all share this layout; the difference is which actions are destructive.

An environment detail page for a preview environment “feature/checkout”: the live preview URL with a copy button, the current release and its source branch, buttons for Deploy, Snapshot, Restore, and “Open wp-admin”, an SSH connect snippet, and tabs for that environment’s logs and traces.

The team switcher (top-left of every screen) changes the active team — its plan, members, and sites. Within a team, the project filter on the sites list narrows to one project. Switching teams re-scopes everything you see, including API keys and the audit log.

The open team switcher dropdown listing two teams with their plan badges, a “Create team” item at the bottom, and the project filter chips that appear on the sites list once a team is selected.

Your account menu (top-right) holds personal settings, API keys, and the link into team administration. Plan, usage, invoices, and payment method live under the team’s billing area; plans and limits explains what each tier includes. Team-wide settings — members and roles, the audit log, and transactional email — are reached from the same team administration entry.