Runtime and processes
Check automation workers that run scheduled or queued jobs where credentials, retries, concurrency, logs, failure isolation, and outbound network dependencies need control.
Automation worker VPS
Run scheduled jobs and background workers on your own server. Plan retries, credentials and resource limits for each task.
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 automation workers that run scheduled or queued jobs where credentials, retries, concurrency, logs, failure isolation, and outbound network dependencies need control.
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
An automation worker runs scheduled or queued jobs: scrapers, report builders, sync tasks, notification senders. Size it for the heaviest job's memory and the number of jobs you allow at once, since concurrency multiplies both memory use and load on the external services the jobs call. Disk needs are usually logs, temporary files, and job artifacts.
The design decisions that matter are retry behaviour and idempotency: a job that runs twice after a network retry must not send the email twice or charge the card twice. Give each job a timeout, exponential backoff on retries, a dead letter path for jobs that keep failing, and alerts on failure, because silent worker failure is the default outcome.
Attach a unique key per job so retries and duplicate deliveries collapse into one effect. Queue systems deliver at least once; exactly once effects are your code's job.
Set a hard cap on simultaneous jobs and a per job memory limit. Uncapped concurrency turns one busy hour into an out of memory event.
Send worker failures to a channel you actually read, with the job name and error. A log file nobody opens is where automation problems go to hide.
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.