01
Persistent infrastructure for automation
Run supported scripts and scheduled workloads on an environment chosen for access, resources, and operating system.
Automation
What this workload needs
Read the fit first, then lock the short requirements list before you open any pricing page.
Automation workloads need a machine that stays online, can run scheduled jobs, and has enough access to install the packages your scripts require. That might be a Windows desktop with Task Scheduler, a Linux VPS with cron and containers, or dedicated hardware for heavier pipelines.
Confirm that your tools and intended activity comply with the Acceptable Use Policy before you deploy. Then choose Windows VPS or Linux VPS for administrator or root control, and reserve Dedicated Servers for isolation or sustained concurrency.
Design for failure: estimate log growth, set restart behavior, and alert when a job stops. Persistent infrastructure only helps if you notice when automation stalls.
02
Expected resource use
03
Administrator or root access
Who it is for
People and teams this guide serves
If your use case matches one of these patterns, continue with the decision steps below.
Scheduled Windows jobs
Run Task Scheduler scripts, reporting pulls, and desktop automations that must survive local PC shutdowns.
Linux cron and workers
Host queue workers, scrapers within policy, and CLI pipelines with root-level package control.
RPA-style desktop flows
Keep supported UI automations on a persistent Windows session with predictable screen and app state.
Monitoring and watchdogs
Run lightweight checkers and restart helpers that watch other services you control.
Getting started
How to choose the right path
Follow these steps in order so the product recommendation matches a real requirement list.
- 0101
Validate policy and software
Ensure the automation and any third-party tools are allowed under acceptable use and licensing rules.
- 0202
Choose Windows or Linux
Match the OS to your runtime — PowerShell and desktop RPA on Windows; cron, containers, and CLI on Linux.
- 0303
Estimate concurrency and logs
Size CPU, memory, disk, and bandwidth for peak jobs plus growing log and artifact storage.
- 0404
Add restart and alerting
Configure service recovery, watchdogs, and notifications so failed jobs do not stay silent.
Compare options
Which product family fits
Use this as a shortlist filter, then open the recommended plans that match your access and resource needs.
| Option | Best for | Access | Notes |
|---|---|---|---|
| Windows VPS | Desktop and PowerShell automation | Full administrator | Install runtimes and keep user sessions available as needed |
| Linux VPS | Cron, workers, and containers | Root | Typical home for CLI pipelines and background services |
| Dedicated Server | Heavy or isolated automation fleets | Root / full control | Use when jobs need dedicated CPU, disk, or network capacity |
Recommended starting points
Choose the product family that matches the required control and resources, then compare its published plans.
Windows VPS
Reliable Windows VPS hosting with full administrator control for software, development, and always-on workloads.
Linux VPS
Isolated Linux VPS hosting with full root access, NVMe storage, and multiple OS options for websites, applications, Docker, and development.
Dedicated Servers
Dedicated physical servers when you need your own hardware, root access, and complete control.
Before you order
Important considerations
These details prevent the most common mismatches between workload and plan.
- Confirm your automation tools and intended activity comply with the acceptable-use policy.
- Use administrator or root access when jobs require custom packages or background services.
- Estimate concurrent processes, log growth, and bandwidth; configure restart and failure alerts.
FAQs
Questions about this workload
Clear answers on access, sizing, and when to move between RDP, VPS, and dedicated options.
Only when the activity complies with our Acceptable Use Policy and applicable laws. Policy-violating automation is not supported.
Related workload guides
Explore nearby use cases if your requirements overlap more than one solution.
Infrastructure for development and testing
Select virtual or physical infrastructure based on operating system, tooling, isolation, and resource needs.
VPS options for Forex trading workloads
Keep MT4, MT5, and supported Expert Advisor workloads on persistent Windows infrastructure.
Dedicated resources for demanding workloads
Move from shared access to virtual or physical resources when workload limits and isolation matter.
Best support
Not sure which server you need?
Tell us what you want to run, where your users are, and how much control you need. We'll help you choose the right RDP, VPS, or dedicated configuration.
48 hoursrefund window
24/7technical support