AlphaAgent Console

Manage AlphaAgent.

Console manages your AlphaAgent subscription, licences and usage. Organisations manages deployments, access for systems that trigger workflows, and shared capabilities inside your AWS accounts. Customer work stays there.

Your organisation

AlphaAgent management

Account ready

  • Subscription

    AWS Marketplace linkedOne agreement for the organisation

  • Studio licence

    ActiveOne licence for each deployment

  • Licence heartbeat

    HealthySigned heartbeats arriving

  • Usage

    Month to dateAttributed by deployment and activity

  • Organisations bundle

    Latest release availableInstall in your AWS account
Subscription, licences, usage and the Organisations bundle in one commercial account.

Management scope

Everything in view.

Account owners and administrators can manage the complete AlphaAgent relationship without entering Studio or handling the work taking place inside it.

Your organisation

Keep the commercial relationship and every Studio licence under one AlphaAgent account.

Your subscription

Link one AWS Marketplace buyer account. AlphaAgent charges join the AWS bill your organisation already manages.

Your licences

Authorise each Studio deployment with its own licence and a one-time token your deployment team controls.

Licence health

See whether licensed Studios are sending heartbeats. Organisations shows the operational state of your deployment fleet.

Usage and cost

Follow prompt-token consumption and estimated cost for each deployment and across the organisation.

Organisations bundle

Download the Organisations bundle for installation in an AWS account you control. Manage Studio releases from Organisations.

Customer lifecycle

From account to running.

Console establishes the commercial account and licences. Your team installs Organisations in its AWS account, then deploys and manages Studio from there.

  1. 1

    Create the organisation

    Set up the tenant that owns your AlphaAgent subscription and licences.

  2. 2

    Link AWS Marketplace

    Connect the buyer account that will carry AlphaAgent charges on its AWS bill.

  3. 3

    Issue the licence

    Create one licence for the Studio deployment and securely hand over its one-time token.

  4. 4

    Install Organisations

    Download the Organisations bundle and install the control plane in your AWS account.

  5. 5

    Deploy Studio

    Use Organisations to deploy Studio into a separate AWS account and manage its access and releases.

Licences and health

Follow every licence.

Each licence represents one Studio deployment. Console gives administrators a clear operational record without becoming part of the work that deployment performs.

One licence. One deployment.

Activation, heartbeats, usage and the audit trail remain attached to the deployment they describe. Administrators can identify it, update its description or revoke it from one record.

A durable audit trail
Creation, activation, billing changes and revocation remain visible.

Licence heartbeats

  • HealthyHeartbeats arriving on schedule
  • WarningRecent heartbeats missed
  • UnhealthyLicence heartbeats missing
Heartbeat history shows connectivity. Organisations shows deployment operations.

Usage and billing

Follow every charge.

Console turns usage from every licensed Studio deployment into one traceable commercial record. Charges flow through AWS Marketplace and appear on the buyer account’s normal AWS bill.

Studio deploymentsSigned usage counts
AlphaAgent ConsoleOrganisation ledger
AWS MarketplaceYour AWS bill

  1. Attribute the usage

    See prompt-token consumption per licence, then break it down by model or activity to understand what drove it.

  2. Trace the estimate

    Month-to-date cost follows the rate in your AWS Marketplace agreement, with a timeline when rates change.

  3. Reconcile with AWS

    Hourly metering records connect Console reporting to AWS Marketplace. The AWS bill remains authoritative.

Deployment boundary

Your AWS. Private access.

AlphaAgent runs in AWS accounts you own and connects directly to your AWS Transit Gateway, with zero access from the public internet. Your agents, workflows, intelligence and results stay inside your deployment boundary.

Customer-controlled boundary

Your AWS accounts

Private access through AWS Transit Gateway

Only network ranges you approve can reach AlphaAgent, with sign-in through your Entra ID and MFA. Your network, DNS, identity and firewall policies control access.

AlphaAgent Studio

AlphaAgent OS

AlphaAgent Organisations

Private connections
  • Amazon Bedrock
  • Your data
  • Your systems

Amazon Bedrock and AWS services use private VPC endpoints. Your prompts, research and results never cross the public internet. Agents can reach only approved network ranges and ports, with read-only SQL access.

Customer work stays here
  • Agents and workflows
  • Specialist intelligence
  • Conversations and documents
  • Data and credentials
  • Results and evidence
Outbound onlySigned licence heartbeats and usage counts

Outbound traffic follows your firewall, allow-list, inspection and logging policies.

Private deployment guide

Architecture diagrams and network checklist

Start with the organisation

Set up AlphaAgent.

Set up your AlphaAgent account and AWS Marketplace agreement, then install Organisations to deploy your first Studio.

Talk to usRead the Console docs