PenterDocumentationWeb dashboard
Documentation

Web dashboard

Manage your PENTER account, available Cloud AI models, usage, connected Desktop devices, access tokens and security settings. Local Browser/HTTP work stays in Desktop.

01

Control plane, not local pentest runtime

Your dashboard lets you manage your account and use available Cloud AI chat. Desktop Browser and HTTP tools require the installed app.

Expect different tool availability in web Mission chat
Web chat uses available Cloud AI models. It does not provide Desktop Browser tools or unrestricted shell execution. The Cloud command runner is disabled during public beta.
02

Dashboard sections

Overview

Current plan/account state and high-level Cloud health.

Mission chat

Cloud-backed conversational workflow available from the web control plane.

Usage

Recent AI/request usage, credits and request status.

Devices

Authorized Desktop installations and revocation state.

API Tokens

Create/revoke PENTER Cloud credentials for supported clients.

Billing

Plan, credit balances, checkout/portal and overage-credit workflows.

Security

Account-security controls and security-related state.

Settings

Profile/account configuration and privacy/account actions.
03

Mission chat and Cloud-backed work

Mission chat provides a browser-accessible PENTER AI conversation. The separate Cloud command runner is intentionally unavailable in the public beta.

  • Select a supported Cloud AI model and keep customer secrets out of prompts unless your engagement permits it.
  • Use PENTER Desktop for supported scoped Browser/HTTP and Request Lab investigations.
  • If an AI provider returns an error, keep the request ID and check your account usage before requesting help.
04

API tokens

API tokens are server-created credentials for supported PENTER Cloud clients. The token value is returned once at creation time; the database stores the token prefix and a hash rather than plaintext token material.

Copy the token at creation time
Because the full token is not retained in plaintext, create a new token instead of expecting the dashboard to reveal an old one later. Revoke credentials you no longer need.
05

Devices

Field/stateMeaning
Device identityAn authorized PENTER Desktop installation tied to the account.
Last seenRecent device activity used to distinguish connected/stale installations.
RevokedThe device should no longer authenticate as active.
API-token relationDesktop authorization can be associated with a server-created API token/credential record.
06

Usage, credits and billing

Your plan and available credits determine which Cloud AI models you can access. Paid checkout may remain disabled while public-beta release checks are completed.

  • Use Usage for request-level status and consumption history.
  • Check Billing for available plans or credit information; paid checkout may still be disabled during beta.
  • Cloud AI usage may consume account credits; Cloud CLI execution is currently disabled.
  • If credits look stale after a payment/change, use the dashboard sync/refresh flow before debugging the desktop client.
07

Security and account settings

Account settings cover profile and privacy/account lifecycle actions while the Security area is intended for account-protection state. Device/token revocation belongs in their dedicated pages because those credentials control downstream access.

Next step

Ready to get started?

Follow the setup guide, install the current approved Desktop release, and connect your account.