The dashboard shows what your Pro Cloud builds did. It is free for every registered account and tracks whether a build ran, what it cost, how much of your code it transformed, and what diagnostics it produced.
You do not need it to use AfterPack: npx afterpack@latest dist/ runs entirely on your machine, protects your bundle, and sends nothing anywhere.
What appears in the dashboard
| Build | Appears in the dashboard |
|---|---|
A local Free build (npx afterpack@latest, a plugin with no key) | No. It never contacts AfterPack, so there is no record to show. |
A Pro Cloud build (an AFTERPACK_key resolved, files sent to the cloud engine) | Yes. One row per build, with its metrics, cost, and diagnostics. |
| A Pro Cloud build with Protection Map capture on | Yes, plus a stored map you can open and read per token. |
| A build that failed | Anonymous, source-free failure telemetry may be sent (opt out with AFTERPACK_telemetry_enabled=false), but it does not create a build row. |
If builds are not appearing, they were probably local builds. See API keys.
Signing in
Sign in at afterpack.dev/login with either:
- A magic link. Enter your email and click the link that arrives. No password to manage.
- Google Sign-In. One click, same account.
Either one lands you on your last-active workspace. Registration is free and creates a workspace with a Default project.
How it is organized
Two levels, and the sidebar's two selectors are them: a workspace at the top, a project under it.
| Level | Holds | Pages |
|---|---|---|
| Workspace | The subscription, the MB allowance, the members, the projects | Overview, Billing, Settings |
| Project | The builds one API key produces, and their Protection Maps | Overview, Builds, Keys, Project Settings |
Inside a build, the sidebar nests that project's other builds under Builds, so you can compare two without returning to the list.
The Billing nav item carries a status badge when something needs attention: Trial, Past due, Blocked (entitlement lapsed, builds stopped), or Limit (allowance exhausted).
What to do here
- Create an API key, which turns local builds into Pro Cloud builds and populates everything else.
- Read a build: coverage, inflation, complexity, build time, diagnostics, and the Protection Map if one was stored.
- Organize work into projects and invite the people who need to see it.
- Watch usage and manage the plan: MB metered, what is left, and what a busy month costs.
Next
- Workspaces & projects: the objects everything else hangs off.
- Builds: the per-build record and how to read it.
- API keys: minting, scoping, and revoking.
- Usage & billing: the meter, the pools, and the plan.
- Accounts: what an account is for, and your own account page.
- Tiers: each plan's allowance and project limit.