Deployment Resource Scaling: Transitioning from Legacy Always On to Reserved VM Tiers

Replit has transitioned from the legacy 'Always On' toggle to a structured Deployment system. This shift decouples the development Workspace from the production instance, meaning that Workspace sleep cycles no longer dictate the availability of a live application.

Under the current architecture, resource allocation is managed through specific machine types (such as Autoscale or Reserved) within the Deployments tab rather than a global account setting. This introduces a boundary where environment variables and resource limits in the Workspace may not align with the production deployment configuration.

When moving a project to a Reserved VM tier to ensure consistent uptime, it is unclear how the platform handles the synchronization of secrets and environment variables between the development environment and the deployed container.

• Do environment variables defined in the Workspace automatically propagate to a Reserved Deployment?
• What is the documented behavior for updating these variables without triggering a full redeployment of the production instance?