Skip to main content

Console overview

The Console is for platform operators (your 4RGE vendor or internal platform team). While the dashboard manages a single organization, the Console manages the platform itself across all organizations.

Operators use the Console to onboard customers, set commercial entitlements, monitor platform health, and enforce governance policies that org admins cannot override.

Console vs dashboard

SurfaceAudienceScope
DashboardOrganization admins and membersSingle org — members, budgets, models, repos
ConsolePlatform operatorsAll orgs — contracts, capacity, provisioning, audit

What operators do here

Contracts & capacity

Define what each organization is entitled to — plan, allowance, and limits.

Governance

Set platform-wide policy and review audit activity.

Clients (organizations)

Each client is an organization on the platform. From the Console you can:

  • View org metadata, contract status, and current usage against entitlement
  • Adjust capacity when agreements change
  • Open observability views for support sessions
  • Manage platform-level people records tied to the org

Runtime and models

Platform-level controls for which models and runtime versions are available across customers:

ControlPurpose
Model catalog publishingRoll out or retire model versions globally
Prompt controlPublish prompt snapshots consumed by desktop and cloud
Effective policy deliveryPush policy bundles to connected clients

Org admins further restrict models within their entitlement via Model control.

Systems

Operational health and configuration for platform services:

  • API health summaries (/api/systems/health/summary on the platform API)
  • Service connectivity and deployment status
  • Internal worker and provisioning pipeline visibility

Access requirements

Note

Access to the Console requires a platform operator role. Most organization admins won't see it. After sign-in, users with platform access are routed to console.4rged.ai instead of the dashboard.

RoleConsole access
Platform owner / adminFull — clients, contracts, governance, systems
Platform supportRead-heavy — clients, observability, support sessions
Org adminNone — uses dashboard only
Org memberNone

Operator workflow: onboard a new client

  1. Create the organization

    Provision the customer record and organization via the Console clients view or the provisioning API (POST /api/provisioning/customers).

  2. Set contract and capacity

    Define plan kind, monthly allowance, support tier, and limits (including cloud agent and Sentinel licenses). See Contracts & capacity.

  3. Invite the customer admin

    Add the customer's primary admin via provisioning people endpoints or the Console UI.

  4. Verify entitlement

    Confirm the org's Usage page shows the correct "Included" bucket and that cloud agent runs are not denied by policy.

  5. Hand off

    Direct the customer admin to connect GitHub and configure cloud agent setup.

Console navigation

The Console sidebar groups operator work into five domains:

SectionRoutesPurpose
Command Center/Landing summary for platform health and ops
Clients/clients, /clients/[organizationId]Org lifecycle, people, and support context
Contracts/contractsCommercial entitlements and capacity
Runtime/runtime/prompts, /runtime/modelsPrompt snapshots and model catalog publishing
Governance/governancePlatform users, support sessions, audit search
Systems/systemsService health and readiness

External links in the sidebar point to 4rged.ai/docs and support@4rge.ai.

API ownership

Console UI routes proxy to the owning backend — never to Supabase tables directly:

DomainBackendExamples
Clients, contracts, governance, systemsplatform-api (api.4rged.ai)/api/provisioning/customers, /api/provisioning/contracts
GitHub health and agent runtimeagents-api (agents-api.4rged.ai)/api/github/app/status, agent run APIs

This split matches the deployment reference: dashboard and Console call platform-api for provisioning and policy authority, and call agents-api for GitHub and agent-run authority.

Local development

When running the monorepo locally, the Console app listens on port 3006:

AppLocal URL
Consolehttp://localhost:3006
Platform APIhttp://localhost:3007
Agents APIhttp://localhost:3008

See Troubleshooting for the full port map.

Contracts & capacity

Commercial entitlements and limit fields.

Governance

Roles, audit, and policy enforcement.

API reference

Provisioning and platform API routes.