Install AlphaAgent Organisations into a new, empty AWS account, and give every AlphaAgent Studio deployment a new, empty AWS account of its own. Three reasons:
- It is AWS best practice to isolate each workload in its own account, with its own limits, billing view and permissions.
- Amazon Bedrock quotas are set per AWS account. Many users in one deployment share one quota and exhaust it; one account per deployment keeps each team's capacity its own.
- The blast radius is smaller. A problem in one deployment, or one team's mistake, cannot reach the others.
Console account, offer and licence
For the administrator who will own the AlphaAgent relationship: one person, once, in a browser. Before you start: your organisation's legal name and billing address, and the 12-digit id of the AWS account that will accept the offer (use the Organisations account).
1. Create your Console account
- Open
https://console.alphaagent.prometheusrl.com/and sign up on the hosted sign-in page (email and password, or a social provider); follow the verification email if one arrives. - Onboarding opens. On Welcome to AlphaAgent click Continue.
- On Your information fill in First name, Last name, Job title, Phone number with country code; Business: Organization name, Industry, Company size, Country (billing); Billing address: Address line 1, Address line 2, City, State / Region, Postal / ZIP code. Click Continue.
- Almost there finishes on its own and opens the home canvas ("Welcome back to AlphaAgent Console"): a left rail with Home, Billing, License Key Management, Organisation and Organization & Profile, and Sign out in the dock. No payment details are collected.
2. Request your private offer
Write to hello@prometheusrl.com from your sign-up address with: your organisation's name as entered in the Console; your use case (what agents will do, roughly how many people, where); the 12-digit AWS account id that will accept the offer and host Organisations (for example 123456789012); the region you will install into. We agree the terms, allow-list your buyer account on the limited listing, and reply when the offer is released. The offer carries your rate in US dollars per one million prompt tokens (the public list price is the ceiling), its name, the agreement duration from acceptance, and a last acceptance date.
3. Accept the offer and link the subscription
Use one browser throughout; the hand-off from AWS to the Console is tied to the browser session.
- Signed in to AWS as the buyer account, open
https://aws.amazon.com/marketplace/pp/prodview-zkhytujgq3kyw. Review and accept the offer. - Click Set up your account. AWS posts a one-time registration token (held for one hour) and redirects you to the Console at
/marketplace/link; without a Console account yet, onboarding runs first and brings you back. - In Link your AWS Marketplace subscription, confirm the Billing contact email and click Link to this Console account (Not now leaves it unlinked). Billing switches to AWS Marketplace from tomorrow (UTC); today's usage is not reported.
The Console opens Billing > Subscription. Status reads Active once the agreement is recorded (Linked, no active agreement for a few minutes first); usage is reported hourly and appears on your AWS bill as the AlphaAgent prompt-tokens line. The strip, field by field: Console: licences, usage and billing.
4. Create your first licence key
One key authorises one Studio deployment; create one per deployment, never reuse one.
- Open License keys and click New license key.
- Enter a Name (placeholder
prod-eu-1; name it for its deployment) and an optional Description; click Create license key. - On the key's page, under License key, click Reveal token, then Copy token, and store the whole value where you keep secrets. It has the shape
aalk_<id>.<secret>: the part before the dot is the License ID; the deployment wizard needs the whole token, not the ID.
What you should see
| Screen | Reads |
|---|---|
| Organization & profile | Your details; Save changes confirms "Your organization details were saved." |
| Billing, Subscription | Status Active, your rate, the agreement table ("No agreements yet" for a few minutes after linking) |
| The key's page | Name, License ID, Status, Heartbeat, Last seen; Heartbeats and Usage fill once a deployment runs against the key |
Notes
- Onboarding must finish before the rest of the Console is reachable; leaving part-way returns you to the first unfinished screen.
- One Console account links to one buyer account and vice versa. To bill a different account, or after the last acceptance date, ask for a new offer. Usage is metered against the most recently started active agreement, so a new rate means a new offer accepted from the same buyer account.
- Licence keys are blocked until an active agreement is linked: "Subscribe to AlphaAgent on AWS Marketplace and link the subscription to this Console account (Billing → Subscription) before creating a license key."
- The create screen says the token "is shown exactly once after creation"; the key's page keeps it behind Reveal token while the key is active. Revocation is irreversible, stops usage at once and removes the token ("Unavailable"); usage already incurred is still billed. Key management: Console: licences, usage and billing.