Skip to main content
Version: 0.9.19

Console overview

The AlphaAgent Console is the web portal where you manage your AlphaAgent account: your organization, billing, license keys, and Studio release downloads. It is the starting point for every customer, and the only place you interact directly with PrometheusRL.

The Console is a portal, not a deployment service

The most important thing to understand about the Console is what it does not do: it never deploys, manages, or accesses your AWS account. AlphaAgent Studio runs entirely in your cloud — you download a Studio release bundle from the Console and deploy it yourself with python3 studioctl.py install (see Deploying Studio).

PrometheusRL holds no credentials to your account and performs no cross-account actions. The only ongoing link between a running Studio and the Console is a secure, signed telemetry channel that carries license activation, heartbeats, and usage metering — described in License Keys.

What you can do in the Console

AreaWhat it covers
Sign-up & onboardingCreate your login, set up your profile and organization, add a payment method
Organization & membersYour tenant, members, and invitations
Billing & subscriptionsPayment methods, invoices, and a usage summary
License keysCreate and manage license keys, monitor deployment health and usage
Downloading StudioBrowse available releases and download the deployment bundle

Who uses the Console

The Console is built for account owners and administrators — the people who manage the commercial relationship, issue license keys, and hand a release bundle to whoever deploys Studio. End users who build and run agents do all their work inside Studio itself, not in the Console; see the Studio Guide.

[Screenshot: Console home dashboard]

How the Console relates to Studio

A typical lifecycle ties the two together:

  1. You sign up and complete onboarding (profile, organization, billing).
  2. You create a license key and copy its one-time License Token.
  3. You download the latest Studio release bundle.
  4. Your technical team deploys Studio into your AWS account using the bundle and the License Token.
  5. The running Studio activates against the Console and begins sending heartbeats; the Console license page turns healthy within minutes.

For the end-to-end picture across both planes, see How it works.