Skip to main content

What is AlphaAgent

AlphaAgent is an operating system for agents that mirrors how a high-performing team works: a specialist grounded on your doctrines and policies that run at scale privately in your AWS account.

You build specialist agents, ground them in your documents, data and systems, and run them in chat, on a schedule, or from your own applications through a REST API. Everything runs in AWS accounts you own. This page names the four products, the one choice you make per deployment, and each reader's first page.

The four products​

ProductWhat it isWhere it runsStart with
AlphaAgent StudioThe application your people work in: chat with agents, build workflows and knowledge graphs, connect data. Each deployment is standard or governed.One fresh AWS account per deployment, at its own app domain. Users sign in through your Entra ID tenant.Getting started
AlphaAgent OrganisationsYour control plane. Its console registers AWS accounts, deploys and updates every Studio, connects your identity provider, grants roles, holds Libraries and API keys, and keeps an audit log.An AWS account of its own, installed once from the bundle, at a hostname you choose. Administrators sign in through Entra ID.Before you start
AlphaAgent ConsoleYour account with Prometheus Research Labs: the private offer on AWS Marketplace, licence keys, usage and monthly statements, and the Organisations bundle download.Hosted by us at console.alphaagent.prometheusrl.com. Sign in with an email address and password.Console account, offer and licence
Programmatic accessA REST API for systems, not people: list workflows, start runs, poll status, download outputs, cancel and erase runs. Approvals stay with people in Studio.A governed deployment, at https://<app domain>/api/v1, called with an API key.Programmatic access: overview

The Console never connects to your AWS accounts. The only traffic it receives from a running Studio is the licence heartbeat and the metering receipts, which carry token counts and never content. Security and architecture reviewers start at Architecture overview and What leaves your account.

Cloud engineers start at Install Organisations. Identity administrators have two Entra ID set-ups: Sign in with Entra ID for the Organisations console and Connect your identity provider for every Studio.

Standard or governed​

When you deploy a Studio you choose, once and for its whole life, between two kinds.

  • Standard ("Standard · personal resources"): what you create is yours. Other users see it only when you share it through a Library. Each user's workspace files are their own.
  • Governed ("Governed · shared resources"): everyone assigned works on the same agents, workflows, connectors, environments and knowledge graphs, and can open and download every user's workspace files. New files still land in their owner's folder. Only a governed deployment offers programmatic access, and its PII redaction default is preselected to Mask.

Studio shows which kind you are in: the Profile page reads "Personal resources" or "Shared resources", and a governed deployment carries the strip "Governed deployment · resources are shared by everyone assigned" on every screen. See Deploy your first Studio and Working in a governed deployment.

Libraries: how deployments share​

A Library is a shared home for one kind of resource (agents, workflows, data connectors, environments or knowledge graphs). An Organisations administrator creates it and adds members from your directory as Contributors (share and pull) or Readers (pull only). In Studio, a Contributor opens a resource, chooses Share and picks the Library and the version. Anyone in the Library, in any deployment, can then download a copy or update a copy they already hold; each copy records where it came from. Connector credentials travel account to account and are never stored in the Organisation. See Libraries and sharing and Libraries.