Skip to main content
Every managed Voyant deployment includes Max directly in the deployed Admin workspace. Voyant provisions the installation, associates it with the deployment, and issues short-lived sessions for authorized staff. You do not need to install @voyant-travel/max-embed, paste an API key, create an operator, or add a token endpoint. Those steps are handled by the managed control plane.
Self-hosted deployments cannot add Max. Voyant API tokens cannot mint Max embed sessions, and there is no public operator-registration API.

​
What users see

Authorized staff open Max from the managed Admin interface. The Admin uses the current staff session and deployment identity to request a short-lived Max session. Platform-owned credentials never enter the browser or the customer-facing dashboard.

​
What the platform manages

Voyant owns the complete lifecycle:
  • Installation during managed deployment provisioning
  • Operator registration and configuration
  • Credential creation and rotation
  • Session authorization for signed-in staff
  • Revocation when a deployment is disabled or leaves managed hosting
The public @voyant-travel/max-embed package remains published for compatibility with existing managed integrations. Installing the package alone does not provide access to Max, and Voyant does not issue session tokens for customer-built or self-hosted integrations.

​
Next steps

Max overview

Learn how Max fits into managed Voyant deployments.

Extend with platform Tools

Add canonical Tools to the deployment’s MCP catalog.

Cloud

Learn about managed deployments.