Skip to main content
Version: 0.9.19

How it works

This page walks the full AlphaAgent journey from creating an account to chatting with an agent, so you can see how the Console and Studio fit together before you start.

The end-to-end flow​

The path from zero to a working agent has five stages: sign up, get a license, deploy Studio, build, and chat. The first two happen in the Console; the rest happen in your own AWS account.

Stage 1: Sign up (Console)​

An account owner signs up in the Console and creates an organization. This is the tenant that holds your billing, licenses, and team. See Sign up and onboarding.

Stage 2: License (Console)​

After setting up billing, the owner creates a license key. At creation the Console shows a one-time license token — copy it and keep it safe, because it is shown only once and you will need it during deployment. Then download the Studio install bundle from the Console. See License keys and Downloading Studio.

Stage 3: Deploy (your AWS account)​

A technical deployer runs the guided installer from the bundle to deploy Studio into your AWS account. During deployment you supply the license token and connect Studio to your own identity provider for single sign-on. When deployment finishes, Studio activates the license against the Console and is ready for users.

See Deployment walkthrough and Single sign-on (SAML).

Stage 4: Build (Studio)​

Your users sign in to Studio through your identity provider and start building:

  • Create agents and write their instructions.
  • Add data connectors so agents can reach your databases, APIs, and tools.
  • Build Knowledge Graphs (AMPG) from your documents.
  • Optionally group agents into swarms and choose execution environments.

See the Studio guide.

Stage 5: Chat and automate (Studio)​

With agents built, users chat with them — asking questions, attaching files, and watching the agent reason, run code, and produce charts and tables. For repeatable processes, users build workflows that chain agents together and run on a schedule.

See Chat and Workflows.

What flows back to PrometheusRL​

While Studio runs, it sends a small, signed stream of information back to the Console: it activates the license once at deploy, sends periodic heartbeats to confirm the license is healthy, and reports usage for billing. That is the only traffic that crosses out of your AWS account. Your data, agents, and conversations never do.

For the full data boundary and the exact fields transmitted, see Data residency and security and Licensing and telemetry.