Runtime and processes
Check a staging server that resembles production closely enough to expose deployment problems while remaining isolated from public indexing, real email, payments, and production data writes.
Staging server VPS
Test deployments in an environment separate from production. Keep staging out of search results and prevent real payments, emails and customer-data writes.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check a staging server that resembles production closely enough to expose deployment problems while remaining isolated from public indexing, real email, payments, and production data writes.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
A staging server earns its keep when it matches production closely: same operating system, runtime versions, service configuration, and deployment steps, with a database copied from production and then scrubbed of real customer data. Differences between staging and production are exactly where deployment surprises hide, so keep a short list of deliberate differences and review it.
Isolation is the other half: staging must not send real email, charge real cards, or get indexed by search engines. Point integrations at sandbox credentials, add password protection or IP restrictions plus a noindex header, and disable production webhooks and cron jobs that would write to live systems or message real customers.
After copying the production database, replace real email addresses, phone numbers, and payment references with test values. A staging system with live addresses will eventually send a real message.
Serve an X-Robots-Tag noindex header and keep the robots file set to disallow all crawlers. Password protection adds a second layer for panels and admin areas.
Write down every intentional difference from production, such as smaller memory, sandbox keys, and disabled jobs. When staging behaves oddly, this list is the first place to check.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.