ScenarioX Self-Hosted V1

ScenarioX Self-Hosted V1 is delivered as a source-free ZIP for a single Linux x86_64 host running Docker Engine and Docker Compose v2. Normal operation uses the included scenariox command from the extracted package directory.

Start here

Read Installation and prepare the host, release files, registry access, and secrets.
Complete Configuration without committing .env or key material.
Use Operations for startup, health, logs, and shutdown.
Use Troubleshooting when a service is not ready.
Read Limitations before defining production recovery or identity requirements.

Emergency procedures are plain Markdown so they remain available when the ScenarioX web interface is unavailable:

Package contents

Path	Purpose
`scenariox`	Package-native operator command
`.env.example`	Configuration template; copy it to `.env`
`docker-compose.customer.yml`	Customer runtime topology using published images
`VERSION`	Release version
`release/release-metadata.json`	Release version, immutable image tag, and commit
`release/published-image-digests.json`	Published image digest inventory
`release/package-manifest.json`	SHA-256 digest for every packaged file
`release/self-hosted-capabilities.json`	Evidence-backed capability status
`docs/self-hosted/v1/`	Offline copy of this documentation

Supported operator path

./scenariox config-check
./scenariox preflight
./scenariox pull
./scenariox start
./scenariox bootstrap-admin \
  --organization-name "Example Engineering" \
  --organization-slug "example-engineering" \
  --admin-email "admin@example.com" \
  --admin-full-name "Platform Administrator"
./scenariox health

The bootstrap command prompts for the administrator password without accepting it on the command line. It can create only the first organization and administrator.

Availability language

Supported means the behavior is present in the package and has repository evidence.
Partial means the package provides part of the workflow and names the customer-owned portion.
Not available in Self-Hosted V1 means operators must not depend on the behavior in this release.
Planned / Future describes roadmap intent, not a release commitment.