Skip to main content
Updated April 2026 — 5 Providers Tested

Best VPS for Windmill in 2026

Windmill's Rust backend runs on a fraction of the RAM that Node.js and JVM tools need. For developer teams who want to write real code — Python, TypeScript, Go — instead of clicking nodes, Windmill is the most resource-efficient choice.

About Windmill

What is Windmill, and why host it yourself?

Windmill is a developer-first open-source platform built on Rust, designed for teams that want to write scripts and workflows in real programming languages rather than click-and-drag interfaces. Unlike n8n or Activepieces, Windmill doesn't wrap APIs in pre-built nodes — instead, you write TypeScript, Python, Go, Bash, or Rust functions directly, and Windmill handles scheduling, execution, secrets management, and building a UI around your code. Each script becomes a deployable 'app' with auto-generated forms, making it straightforward to expose internal tools to non-technical teammates without building a separate frontend.

The Rust backend is the key architectural differentiator: Windmill's server process consumes a fraction of the RAM that JVM-based or Node.js-based tools require. A fresh Windmill deployment idles at roughly 100–200 MB, compared to 400+ MB for n8n and 1+ GB for Kestra. This efficiency means you can run Windmill productively on Hetzner's CX22 (4 GB RAM) alongside multiple other services, or pack more automation capacity into a given server budget.

Worker processes are isolated with resource limits, so a runaway Python script consuming excess memory won't affect other running scripts or the Windmill server itself. Scripts execute in isolated processes using Linux namespaces for file system separation — a genuine security boundary, not just process separation.

Windmill VPS Requirements

How much server power does this tool actually need? Tested recommendations based on workload size.

Basic

  • 1 vCPU
  • 1 GB RAM
  • 20 GB SSD

Solo developer, occasional scripts, basic scheduling.

Recommended

Recommended

  • 2 vCPU
  • 2 GB RAM
  • 40 GB NVMe

Small teams, concurrent scripts, internal tool hosting.

Production

  • 4 vCPU
  • 4 GB RAM
  • 80 GB NVMe

Teams, Python/TypeScript at scale, high-concurrency workflows.

Top VPS Providers for Windmill

Ranked by overall value for running Windmill. All providers tested with Docker setup.

DigitalOcean

DigitalOcean

Top PickBest for Developers

Developer-friendly cloud with one-click app marketplace and great docs.

$6.00
Starting at
1 GB
RAM
1 vCPU
CPU
4.8/5
Rating
Excellent documentation One-click installations for many tools Hourly billing available
Hostinger

Hostinger

Best Value

Affordable VPS with excellent performance and global data centers.

$6.49
Starting at
4 GB
RAM
1 vCPU
CPU
4.7/5
Rating
Very affordable starting prices Easy-to-use control panel Good performance for the price
Hetzner

Hetzner

Best in Europe

European cloud with dedicated vCPUs and transparent pricing.

$4.35
Starting at
4 GB
RAM
2 vCPU
CPU
4.7/5
Rating
Dedicated CPU cores (not shared) Excellent price-to-performance ratio 20 TB traffic included on all plans
Vultr

Vultr

High-performance cloud with 32 global data centers and hourly billing.

$5.00
Starting at
1 GB
RAM
1 vCPU
CPU
4.6/5
Rating
Largest data center network Competitive pricing Hourly billing flexibility
Contabo

Contabo

Most Resources

Maximum resources at minimum prices — most bang for your buck.

$4.50
Starting at
8 GB
RAM
4 vCPU
CPU
4.3/5
Rating
Unbeatable resource-to-price ratio Huge RAM and storage allocations Long track record
Self-Hosting Advantages

Why Self-Host Windmill on a VPS?

Windmill Cloud charges per execution-second — compute time adds up quickly for teams running frequent or long-running scripts. Self-hosting eliminates this cost entirely. Beyond savings, there are strong technical reasons to own your Windmill deployment:

Scripts as code, not config

Windmill stores all scripts as plain TypeScript, Python, or Go files that sync to a Git repository. Version control, code review, and CI/CD deployments work exactly like application code.

🔒

Minimal resource footprint

Windmill's Rust server idles at 100–200 MB — 3–5x lighter than n8n, 10x lighter than Kestra. You can run Windmill alongside a full web stack on a $5/month VPS.

🧩

Automatic dependency resolution

Python scripts list pip requirements at the top of the file; Windmill installs them automatically on first run and caches for subsequent executions. No requirements.txt management needed.

🗄️

Internal tool access

Scripts running on your VPS can query private databases, hit internal APIs, and access services behind your firewall — all impossible from cloud automation platforms.

Frequently Asked Questions

How little RAM does Windmill actually need?

Windmill's Rust server process idles at roughly 100–200 MB. Adding PostgreSQL brings total idle usage to 600–800 MB. A 2 GB VPS runs Windmill comfortably for a solo developer or small team. For comparison, n8n with PostgreSQL uses 3–4× more RAM at the same workload.

Does Windmill support Python libraries?

Yes. Python scripts in Windmill resolve pip requirements from an import block at the top of the file — no requirements.txt or manual pip install needed. Each execution gets a fresh virtual environment with your specified packages. Heavy packages like pandas, numpy, or torch are cached after first execution.

What is the difference between Windmill scripts, flows, and apps?

Scripts are individual functions (Python, TypeScript, Go, etc.) that can be run on demand or scheduled. Flows chain multiple scripts with conditional logic, loops, and error handling. Apps are auto-generated or hand-crafted UIs built on top of scripts, complete with forms, tables, and charts. This three-layer model makes Windmill more versatile than pure workflow tools.

Can I use Windmill as a cron job replacement?

Yes. Windmill's scheduler supports standard cron expressions and can run any script on a timer. Execution logs, error alerts, and retry logic are built in. For scheduled tasks like database cleanup, report generation, or data syncing, Windmill is significantly more capable than raw cron because you get execution history, alerting, and a web UI without needing SSH access.

How does Windmill's worker isolation actually work?

Each script execution runs in an isolated process with configurable CPU and memory limits, using Linux namespaces for file system isolation. Worker processes exit after each execution, preventing state leakage between runs. This is why Windmill can safely run scripts from multiple users on the same server — the isolation is a genuine security boundary.

Ready to Deploy Windmill?

Write real Python and TypeScript workflows on your own VPS. Windmill runs on as little as 1 GB RAM.