> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiaxoniq.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Try it in the playground
> Open a workspace that already has a fortnight of telemetry in it — no account, no install, no card. Three demonstration estates to choose from, each a different kind of system with a different thing going wrong.
export const PLAYGROUND_URL = 'https://play.aiaxoniq.com/playground';
export const PLAYGROUND_RETAIL = 'https://play.aiaxoniq.com/playground?demo=ecommerce-storefront';
export const PLAYGROUND_SAAS = 'https://play.aiaxoniq.com/playground?demo=saas-platform';
export const PLAYGROUND_QUICKSTART = 'https://play.aiaxoniq.com/playground?demo=quickstart-tour';
The fastest way to see what aiAxonIQ does is to open one that is already full.
The playground is the product — the same build, the same queries, the same
pages — logged into a demonstration workspace that has been seeded with a
fortnight of logs, metrics, traces, alerts, SLOs and synthetic checks.
**No account, nothing to install.** The playground opens a workspace that
already has a fortnight of telemetry in it. It is read-only and the data is
fictional — a demonstration estate, not anyone's production system.
## Choose an estate
The three are deliberately different systems, not three skins on one dataset.
They run different services, in different namespaces, on different clusters, in
different languages, and each has a different thing going wrong in a different
place. Pick the one that looks most like yours.
A retail estate under Black Friday load — 8 services across four namespaces,
with a payment dependency that is quietly failing and dragging checkout down
with it. The one to open if you want to watch an incident be traced to its
root cause.
A multi-tenant B2B platform on a weekday rhythm — 7 services, an ingestion
pipeline building a backlog overnight, and objectives to run it against.
The one to open if you operate a platform other teams build on.
Two services and a database — 3 services in one namespace, the smallest
estate that still lights up every page. The one to open if you want the
shape of the product rather than a scenario.
Those links open the picker with that estate already selected. If a link is
ever out of date, the picker says so and shows you what it does have — it
will not quietly open a different demo than the one you asked for.
## What is actually in there
Every estate carries the same signal types, because they all come from one
generator:
| What you get | Where to look |
| :--------------------------------------------- | :------------------------------ |
| Logs, with patterns already clustered | **Logs** |
| Metrics, including host and container series | **Metrics**, **Infrastructure** |
| Traces, and a service map discovered from them | **Traces**, **Services** |
| Alert rules with a firing history | **Alerting** |
| SLOs, some meeting target and some burning | **SLOs** |
| Synthetic checks run from three locations | **Synthetics** |
| Security and audit events | **Security** |
| Hosts reporting through the eBPF agent | **Zero-code** |
The two larger estates also carry LLM request telemetry, so **LLM
observability** has something in it; the quickstart tour deliberately does not.
Each card in the picker lists what that estate demonstrates, and the list is
derived from the data that was actually seeded rather than written by hand — so
a section it does not name is a section that estate genuinely has nothing in.
## Then send your own data
The playground is not a dead end. **Send your own data** inside it creates an
ingest key and moves you into a private workspace of your own, so your telemetry
never lands in the shared demo. From there the
[quickstart](/get-started/quickstart) applies unchanged.
No account and no card. Pick an estate and you are in the product in a few
seconds.