Skip to main content

​
Control Center

Control Center is the privileged operating surface for Starfire AI. Its purpose is to let authorized operators manage the platform without treating direct database edits, source-code changes, or ad-hoc production commands as normal administration.

​
Control Center 4.0

The NEXUS-era Control Center expands the admin experience into a broader platform operating system. The administration model spans areas such as:
Individual surfaces can roll out independently during Alpha 1.6.3.

​
Operating principles

​
Least privilege

Administrators should receive only the platform permissions required for their job. Support access, billing access, model administration, and security administration do not need to be the same role.

​
Audit important changes

Actions that affect users, plans, credits, permissions, models, platform configuration, or security should be attributable to the administrator who performed them when the active subsystem supports auditing.

​
Prefer observable state

Use request IDs, run IDs, billing records, health checks, incident timelines, and diagnostic state instead of guessing from symptoms.

​
Keep private content separate from operations

Control Center needs enough metadata to operate the platform, but operational administration should not become unrestricted browsing of private user conversations or artifact contents.

​
Typical investigation flow

  1. Identify the affected resource: user, organization, request, run, subscription, model, provider, artifact, or component.
  2. Confirm the active account/organization and entitlement context.
  3. Review recent state, logs, health, and audit information.
  4. Determine whether the problem is local or platform-wide.
  5. Apply the smallest administrative change needed.
  6. Verify the resulting state.
  7. Record or update an incident if the problem affects broader platform availability.
The Control Center architecture includes a global-search/command-palette concept so administrators can locate operational resources by identifiers such as user email, request ID, run ID, artifact ID, subscription/price identifiers, or other supported administrative references.

​
Control Center is not the user app

Organization administrators and developers should be able to manage their own appropriate resources without receiving platform-wide Control Center access.

Users & Identity

Operate account state, sessions, access, credits, and user-level diagnostics.

RBAC & Support Mode

Understand granular admin permissions and safer support access.

Models & Routing

Manage providers, health, fallback, and routing controls.

Intelligence

Operate research, builds, artifacts, Knowledge, retrieval, and tools.

Billing

Reconcile customers, subscriptions, plans, credits, and usage.

Security & Audit

Investigate sessions, events, admin actions, abuse, and risk signals.