Get Started with aamp — Sandbox, Self-Host or Talk to Us

Tell us what you're building.

One short message and we point you at the right starting point. No phone number, no company size.

01We reply within one business day — a person, not an autoresponder.

02Prefer to skip the conversation? Boot a sandbox or self-host below.

03Regulated environment or a deadline? Say so and we'll scope it.

Or start on your own

Two more ways to start.

Not everyone wants to talk first. Boot a sandbox or self-host today.

Option · A

Try in the sandbox.

A hosted aamp environment, ready in minutes. No credit card. Enough to see whether it fits your stack before you install anything.

Boot the sandbox →

Option · B

Self-host it.

Install on your own Linux host and evaluate the architecture before you talk to anyone. Most technical teams start here — and we'd rather they did.

You will need

A Linux host with KVM

Hardware virtualization (nested, for private cloud)

A 32-byte secrets master key

Open docs →

Option · C

Talk to us.

Scoping, deployment planning, and a walk through your compliance footprint. Useful when there is a deadline attached or the environment is unusual.

Use the form above ↑

Licensing

The license is not the hard part.

You get the distribution bundle and a token file named aamp.license.
Drop it into the host config directory and start. No online activation, no portal, no seat reconciliation before you can run your first workflow.

Read the full terms →

How it stays live

The token renews itself in the background, twice daily before expiry

One outbound HTTPS connection to the licensing server — no prompts or documents travel over it

Status, validity dates and a manual refresh button sit in Mission Control

An active license also opens the distribution endpoints for updates and microVM components

Tell us what you're building.

Thanks — message sent.

Two more ways to start.

Try in the sandbox.

Self-host it.

Talk to us.

The license is not the hard part.

Not ready to talk?