Forge Pool

Appearance

Forge HQ ​

Control Plane for Forge Pool ​

Forge HQ is the control-plane interface of Forge Pool.

It is where users and organizations manage:

  • projects
  • API keys
  • jobs
  • nodes
  • credits and billing
  • observability
  • access and governance settings

HQ does not execute compute.

It provides the trusted operational surface around execution.

What HQ Is For ​

HQ exists so operators can:

  • create and manage organizations
  • isolate projects
  • issue and revoke API keys
  • monitor jobs and replay metadata
  • inspect node health and contribution
  • review credits, billing, and payouts
  • manage trust boundaries at the organization level

If Forge Pool is the execution system, HQ is the management interface around it.

Operational Role ​

HQ sits on the trusted side of the system.

Its role includes:

  • identity and access workflows
  • project lifecycle management
  • control-plane observability
  • billing and ledger visibility
  • node registration workflows
  • policy-facing operational visibility

HQ is not the Kernel and not the Hub.

It is the human-facing control surface above them.

Typical HQ Workflows ​

Common workflows in HQ include:

Project Management ​

  • create project
  • assign project context
  • issue API tokens
  • inspect workload history

Job Visibility ​

  • inspect recent jobs
  • review job-level metrics
  • inspect replay metadata
  • confirm verification mode and shard count

Node Operations ​

  • generate and revoke Node Tokens
  • review node status
  • inspect performance and health signals
  • monitor provider contribution and earnings

Billing and Credits ​

  • review credit burn
  • inspect invoices or balances
  • understand provider-side earnings
  • reconcile execution with spend

HQ and the Runtime ​

HQ is connected to the runtime, but not part of compute execution itself.

A simple model is:

text
User
  ↓
HQ
  ↓
Web Core governance surfaces
  ↓
Hub and runtime metadata

HQ lets humans understand and control the system without bypassing execution doctrine.

Key Areas in HQ ​

Typical sections include:

  • Dashboard
  • Projects
  • Jobs
  • Nodes
  • Billing and Credits
  • Payouts
  • Settings
  • Documentation links

Exact layout may evolve, but the control-plane role remains the same.

For visual orientation, see:

→ HQ Dashboard Tour

For client-side integration, see:

→ Clients

For node operation, see:

→ Providers

For telemetry and execution transparency, see:

→ Observability

Mental Model ​

HQ is not “the computer.”

HQ is the trusted operational window into the computer.

It gives humans visibility, control, and governance over a system whose execution truth is enforced elsewhere.