ScenarioX Self-Hosted V1 Limitations

Read this page as part of production planning. A capability listed as unavailable or future is not hidden behind configuration and must not be included in the V1 operating promise.

Supported

Single-host Docker Compose

The source-free customer package runs on one Linux x86_64 host. It uses immutable ScenarioX image tags and a published digest manifest.

Local administrator access

A terminal-only bootstrap creates the first organization administrator. Recruiter sign-in uses organization slug, email, password, database-derived roles, rate limiting, and a 15-minute access token.

Candidate workspace isolation

Candidate workspaces use per-workspace networks and runtime hardening. Docker authority remains behind docker-socket-proxy rather than being mounted directly into workspace-orchestrator.

Anthropic provider

A customer-provided Anthropic API key is the supported V1 AI provider configuration.

Partial

Customer-managed TLS

The bundled edge serves HTTP. The customer must provide production DNS, certificates, HTTPS termination, and the network boundary in front of the package.

Service readiness coverage

Core APIs and instrumented workers expose health or readiness probes. Interview orchestrator API, session workspace consumer, and session pipeline consumer currently report process state only.

Not available in Self-Hosted V1

Backup and restore

Package-native backup, backup verification, and complete restoration have not passed the V1 release acceptance gate. Reserved operator commands exit without performing work.

Version-to-version upgrade and rollback

No named baseline-to-target upgrade or automated rollback workflow is certified for V1. restart restarts the installed release; it is not an upgrade.

High availability

V1 is a single-host deployment. It does not provide multi-node scheduling, failover, or a high-availability control plane.

Invitation email delivery

The platform creates candidate invitation tokens but the V1 package does not deliver invitation email.

Support bundle and data purge

Automated support-bundle collection and package-native purge are unavailable. Preserve logs and release files manually without exporting secrets or candidate content.

Planned / Future

SSO and SCIM

Production identity-provider sign-in and automated user provisioning are planned beyond Self-Hosted V1. IDP_PROVIDER=local is the supported release configuration.

License enforcement

V1 uses the built-in always-licensed implementation. LICENSE_KEY is reserved for a future release and does not activate or enforce V1 features.

Release interpretation

The packaged release/self-hosted-capabilities.json is the machine-readable status record. Documentation and support guidance must not promote a capability beyond that record without new release evidence.