MCMMCM DocsEngineering (Internal)
User StoriesMCM-01 — MCM Nexus
v1.2 is unreleased — see v1.1 for the current stable release.

MCM-04 — Request a Self-Hosted MSP Demo

A customer requests a 30-day MSP-role trial deployed into their own infrastructure.

MCM-04 — Request a Self-Hosted MSP Demo

← Back to MCM Nexus overview

As a Customer User,
I want to request a 30-day MSP-role trial that I deploy into my own infrastructure,
so that I can evaluate MCM end-to-end in my own environment.

Acceptance Criteria

  • The request form clearly labels this option as deployed in the customer's own infrastructure via the standard MCM installer (see MCM-09 — Download MCM Installation Package).
  • No data-sharing disclosure is required for this path (the customer's data never leaves their own environment).
  • On submission, a request of type Self-Hosted MSP Demo is created with status PENDING and routed to the Nexus Admin for review.
  • If approved, the resulting license is scoped to the MSP role for a 30-day validity window, and the approval flow issues MCM App credentials as described in MCM-07 — this path is what makes the MCM App User / instance-validation loop load-bearing.
  • The customer receives the standard Subscription Activation email unchanged — deployment guides, MCM App username/password, and support/documentation links — since this path deploys into the customer's own infrastructure the same as a paid self-hosted license.

Technical Design

Reuses the same RequestService.create(...) path in mcm-nexus/backend as MCM-03 — Request a Hosted Enterprise Demo, adding SELF_HOSTED_MSP_DEMO to the RequestType enum but skipping the disclosure-acknowledgment branch, since the customer's data never leaves their own environment. mcm-nexus/frontend's (customer)/requests/new form labels this option as a customer-infrastructure deployment. On approval, License.role is set to MSP_DEMO, which is what makes the MCM App User / instance-validation loop load-bearing for this path (see MCM-07 — Subscription Activation and Secure Credential Delivery).


UI / Frontend Changes

  • (customer)/requests/new: add a "Self-Hosted MSP Demo" option, labelled as deploying into the customer's own infrastructure (no disclosure checkbox needed, unlike the Hosted Enterprise Demo option).
  • Request history / detail view shows status (PENDING / APPROVED / REJECTED) for this request type.
  • Once approved, the customer's dashboard surfaces a "Download installer" call-to-action leading into the Download MCM Installation Package flow.
  • No disclosure-checkbox UI is shown on this form, distinguishing it visually from the Hosted Enterprise Demo request form.

On this page