Quickstart

Define a multi-agent workflow in markdown, compile it, and run it on your own appliance.

1

Deploy & Sign In

Deploy the AppXen Platform appliance from AWS Marketplace into your own AWS account, then sign in to its console:

  1. Open the stack's ConsoleUrl output. Accept the self-signed certificate warning unless you set a domain.
  2. Sign in as the AdminEmail you gave the stack, using the stack's InstanceId output as the temporary password. The console makes you change it at once.
  3. Check the health panel on the Home page. It shows your AWS identity, the services, and Amazon Bedrock access for each model.

The full steps are in First sign-in. Then open Agent Orchestrator from the sidebar.

Before you run a workflow: workflows call Amazon Bedrock in your account, and compiling one uses Claude Sonnet. Claude models need a one-time step by an AWS account administrator first, described under Amazon Bedrock model access. Amazon Nova and Titan need no such step.

2

Write a Workflow in Markdown

Navigate to Workflows and click New Workflow. Use the built-in CodeMirror editor — or pick a template from the gallery — to define your workflow:

workflow.md 
# Market Research Report

## Inputs
- topic: The subject to research (string, required)

## Agents

### Researcher
Expert at gathering and synthesizing information from multiple sources.
Model: Sonnet
Tools: rag-engine

### Writer
Skilled at writing clear, structured reports.
Model: Sonnet

## Steps

### Research
Search the knowledge base for information about {inputs.topic}.
Find key facts, trends, and insights.

### Write Report
Using the research: {steps.research.output}

Write a comprehensive report on {inputs.topic}.
Include an executive summary, key findings, and recommendations.

## Output
steps.write_report.output

See the Workflow DSL Reference for the full syntax.

3

Save & Compile

Click Save. The orchestrator compiles your markdown into a structured execution plan using Claude. You'll see a preview of the compiled plan showing agents, steps, and dependencies.

If there are issues (missing agents, circular dependencies), the compiler will flag them with notes so you can fix them before running.

4

Run the Workflow

Click Run on the workflow page. Fill in any required inputs (like topic) and confirm.

The execution page shows real-time progress:

  • A segmented progress bar showing which step is running
  • Step-by-step results — expand each step to see its output
  • Token usage per step and total
  • A Stop button if you need to cancel mid-run
5

View & Download Output

When the workflow completes, the final output renders at the bottom of the execution page. Content is auto-detected — markdown renders as formatted prose, JSON is syntax-highlighted, and code blocks display with language hints.

Click Download to save the output as a file (.md, .json, etc. based on content type).

What's Next