Choose the environment boundary
Organize development, preview, staging and production work explicitly. Review the variables and connected services for each environment rather than assuming they share data.
MolternCreate a preview environment
Guides
Give test work its own place to run.
Separate preview workloads and configuration from the application people already depend on.
Flight paths artwork / 22
Choose an environment group and create a preview environment before deploying test workloads. Connect appropriate test services and variables; do not assume production data has been copied. Review resource limits and remove work that no longer needs to run.
Create a preview environment
Connect and test the data path
Put the service in the appropriate environment and use explicit private connections where supported. Keep server credentials out of browser code and source control.
Review limits and operating costs
Check the workspace plan, workload limits, CPU, memory and storage requirements. Review usage and applicable guardrails before adding or resizing resources.
Detailed instructions are maintained in the product documentation.
Questions before you start
Does a preview copy production data?
Do not assume it does. Configure appropriate test services and verify which data and variables the preview can access.
Who owns backups and recovery?
Name an owner and review the service-specific persistence and recovery instructions before relying on its data.
Are program benefits or resource limits automatic?
Plans and eligibility differ. Use the pricing and billing pages for current terms; program benefits require individual confirmation.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗