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.
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.
Dashboard sections
Overview
Mission chat
Usage
Devices
API Tokens
Billing
Security
Settings
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.
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.
Devices
| Field/state | Meaning |
|---|---|
| Device identity | An authorized PENTER Desktop installation tied to the account. |
| Last seen | Recent device activity used to distinguish connected/stale installations. |
| Revoked | The device should no longer authenticate as active. |
| API-token relation | Desktop authorization can be associated with a server-created API token/credential record. |
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.
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.
Ready to get started?
Follow the setup guide, install the current approved Desktop release, and connect your account.