Blog

EmDash Hosting: Cloudflare, VPS, Panel and Managed Hosts

Cloudflare Workers is the default EmDash host, not the only one. What Workers free vs paid really costs, what a €4 VPS with Docker actually needs, and which managed hosts are live in November 2026.

Cover for EmDash hosting alternatives: neon-green line art of edge nodes, a server rack and a control panel on dark navy

Cloudflare Workers is where most EmDash sites land first, and for good reason: it is cheap, fast, and the docs assume it. But EmDash CMS (the Astro CMS from Cloudflare, not the punctuation mark) is a plain Node 22 application at heart, so Workers is not the only home it can have. If you want a server you control, a panel that runs several sites for you, or a fully managed host, there are real options with real prices. This guide covers what EmDash needs from a host first, then prices every route as checked on 3 November 2026.

The short answer: which EmDash host fits you

The short answer: which host fits you

Running one brochure site, no plugins
Cloudflare Workers Free. $0
Installing registry plugins, or expecting traffic
Cloudflare Workers Paid. $5
Running several sites or client sites
VPS plus EmDash Panel. €3.79 to €8
Wanting zero server work
DashHarbor, xCloud or WPMU DEV. $0 to $19
Already running a Docker fleet
Plain compose, or Coolify. $0 to $15

The free tier is not the whole story. The moment you install a sandboxed registry plugin or a page passes 10 ms of CPU time, Workers Free stops being enough, and the fix is the $5 plan, not a new host. Everything below explains why, with the numbers behind each row.

What EmDash needs from a host

Four requirements decide compatibility before price does. Miss one and the install either fails at boot or breaks the first time somebody signs in with a passkey.

Node 22.16 on glibc, and why Alpine fails

The standalone server (emdash) declares node >=22.16, and the reference image is node:22-bookworm-slim. The docs recommend 22.23.4 or newer; 22.16 is the floor on older Astro builds. Alpine (musl) images are out because the workerd binary that powers plugin sandboxing has no musl build. A host that only offers Node 18 or musl-based images cannot run a full EmDash install.

SQLite needs a real disk, Postgres does not

The default database is a SQLite file at /app/data/data.db, and uploads land in /app/uploads. Both need a persistent disk with real file locking; an ephemeral filesystem wipes them on every redeploy. PostgreSQL (via Kysely) or libSQL/Turso move state off the box, which is the only reason serverless targets stay on the table at all.

Passkeys need an exact HTTPS origin

Admin login is WebAuthn first. It requires a valid certificate and an exact origin match: EMDASH_SITE_URL must equal the scheme and domain the browser sees (https://cms.example.com). Plain HTTP fails, a mismatched origin fails, and generated preview URLs such as *.vercel.app fail unless you realign the setting on every deploy.

Sandboxed plugins need workerd, and workerd needs a host that allows it

Registry plugins from the EmDash plugin catalogue run with capability manifests inside isolated V8 sandboxes. On Cloudflare that is the Worker Loader API (env.LOADER); on a VPS or in Docker it is a local workerd process inside the container. Serverless function sandboxes cannot spawn workerd isolates, so on those hosts the plugin sandbox does not run at all. What a sandboxed plugin can do once it runs, and where the security boundary sits, is covered in sandboxed vs native EmDash plugins.

Search Engine Journal argues that most of the 1.0 features rely on Cloudflare-specific infrastructure, which makes EmDash harder to host elsewhere than WordPress. The ecosystem is also brand new... It's stable as of 1.0. But the plugin ecosystem is tiny compared with WordPress, and much of its feature set leans on Cloudflare. Treat it as something to test on a small project first.

Jean Galeafounder of WP Mayor, 26 October 2026

What EmDash needs from a host

Node 22.16 on glibc (Debian/Ubuntu)
Alpine/musl images cannot run the plugin sandbox
A persistent disk for SQLite
Ephemeral filesystems lose the database and uploads on redeploy
Exact HTTPS origin for passkeys
A mismatched EMDASH_SITE_URL breaks WebAuthn login
workerd for sandboxed plugins
Serverless sandboxes cannot spawn isolates, so registry plugins do not run

Cloudflare Workers: the default, free or paid

EmDash on Cloudflare is the path the docs assume, and for a small site it is still the cheapest. The catch is which plan you need, and earlier versions of this post had that wrong: Workers Paid does not "add D1 and R2". Both live on the free plan. What $5 buys is the plugin sandbox and CPU headroom.

What the free plan includes (D1, R2, 100k requests/day)

Free gets 100,000 requests per day (resetting at 00:00 UTC), D1 with 5 million row reads and 100,000 row writes per day plus 5 GB storage (500 MB per database, 10 databases), R2 with 10 GB-month storage, 1 million Class A and 10 million Class B operations per month, and zero egress fees. For a brochure or portfolio site that is plenty, and the reason most people never leave:

Deploying on Cloudflare Workers and D1 means I don't wake up at 3 AM because an unpatched WordPress plugin let someone upload a shell script. It scales to zero and costs me literally pennies.

Independent developer on Hacker Newsitem 49877456, 28 September 2026

The 10 ms CPU ceiling, and the exceededCpu errors it causes

Free caps CPU time at 10 ms per request. Rendering complex blocks, parsing Portable Text, and deserializing D1 results can pass that ceiling, and when they do, the request fails with the exceededCpu error Cloudflare returns for CPU-limit breaches (error 1102, message: Worker exceeded resource limits). Free also caps subrequests at 50 per invocation, which matters once webhooks or external APIs enter the picture. The quieter cost is latency when you skip edge caching:

Unoptimized EmDash on Workers + D1 had a 543 ms mean response time compared to 84 ms for an identical WordPress setup on a dedicated Hetzner box. If you don't aggressively cache at the Cloudflare edge, D1 query roundtrips will bite your TTFB.

SHIFT64 engineering teambenchmark report, October 2026

What $5/mo really unlocks: Worker Loader, CPU headroom, request volume

Three things, and none of them is D1 or R2 storage. First, the Worker Loader API (env.LOADER), the isolated runtime that executes registry plugins: 1,000 unique dynamic workers per month included, then $0.002 per day for each extra one. Second, CPU time: a 30-second CPU default per request, configurable up to 5 minutes, with 30 million CPU-ms per month included. Third, volume: 10 million requests per month instead of a 100,000-per-day cutoff, then $0.30 per million.

Workers Free has runtime limits, including a 10-millisecond CPU limit per invocation... One relevant example is EmDash's sandboxed plugin system. On Cloudflare, registry-installed sandboxed plugins use a Worker Loader and require the Workers Paid plan ($5/mo). So a small EmDash website without that requirement might work on the Free plan, while a project needing sandboxed plugins may require Paid even with very little traffic.

DashHarbor technical overviewNovember 2026

Workers Free vs Workers Paid ($5/mo), 3 November 2026

Requests
100,000/day. 10M/mo included, then $0.30/1M
CPU time per request
10 ms hard cap. 30 s default, up to 5 min
Included CPU
n/a. 30M CPU-ms/mo, then $0.02/1M ms
Sandboxed plugins
No Worker Loader. 1,000 dynamic workers/mo, then $0.002/day each
D1 reads
5M rows/day. 25B rows/mo, then $0.001/1M
D1 writes
100,000 rows/day. 50M rows/mo, then $1.00/1M
D1 storage
5 GB (500 MB per DB). 5 GB, then $0.75/GB-mo (up to 10 GB per DB, 1 TB account cap)
R2 storage
10 GB-mo. 10 GB, then $0.015/GB-mo
R2 operations
1M Class A, 10M Class B/mo. Same included, then $4.50/1M and $0.36/1M
Egress
$0. $0

Where the bill can run away

The loudest post in this niche is titled "Cloudflare EmDash Can Cost You $13000 Overnight (And You Can't Stop It)", and it is the reason this section exists. On Free, the daily cutoffs cap the damage. On Paid, overage is metered: CPU past 30M CPU-ms is $0.02 per million, requests past 10M are $0.30 per million, D1 reads past 25 billion rows are $0.001 per million, D1 writes past 50M rows are $1.00 per million (every index update counts as a row write), R2 Class A operations past 1 million are $4.50 per million, and extra R2 storage is $0.015 per GB-month. Egress stays $0 on both plans. My practical answer: set a billing alarm on day one, watch the CPU-time metric after launch, and remember that media-heavy sites and write-heavy plugins drive the tail, not page views.

Self-hosting on a VPS with Docker

EmDash runs on plain Node 22 with SQLite, so any glibc Linux VPS works. One container idles at about 128 MB RAM and uses 256 to 512 MB under active rendering or plugin loads, so a single 4 GB box hosts 5 to 10 sites behind one reverse proxy. You install Docker, terminate TLS, and own the ops.

That scales further than the headline number suggests: the workerd sandbox listener was hardcoded to 127.0.0.1:18788, so a second EmDash instance on the same host crashed with an address-in-use error and its sandboxed plugins stopped loading. Dynamic port allocation landed in core on 5 November 2026 (PR #4665), and multi-site VPS hosting is unblocked now.

What €4 a month buys in November 2026

DigitalOcean Droplet pricing table listing the $6 basic plan with 1 GB of memory
DigitalOcean Basic Droplets, 3 November 2026: the $6/mo 1 GB plan is the realistic entry, the $4 512 MB tier is too tight for Docker and Node 22. Hetzner's CX22 undercuts it at €3.79.

Entry VPS prices, 3 November 2026

Hetzner CX22
2 vCPU, 4 GB, 40 GB NVMe, 20 TB. €3.79/mo (IPv4 add-on €0.50 to €0.60)
DigitalOcean Basic Droplet
1 vCPU, 1 GB, 25 GB SSD, 1 TB. $6/mo ($4 tier too tight)
netcup VPS 500 G12
2 vCPU, 4 GB DDR5, 128 GB NVMe, unmetered. €4.97/mo excl. VAT
OVHcloud VPS-1
2 vCPU, 4 GB, 40 GB NVMe, 500 Mbps unmetered. €4.20/mo, free daily backup
Contabo Cloud VPS 4
4 vCPU, 8 GB, 75 GB NVMe, 32 TB. €4.40/mo (shared resources)

More budget boxes from the same research pass:

More budget VPS options

Hostinger KVM 1
1 vCPU, 4 GB, 50 GB NVMe, 4 TB. $5.99 to $6.49/mo renewal
Vultr Cloud Compute
1 vCPU, 1 GB, 25 GB SSD, 1 TB. $5 to $6/mo with IPv4 ($2.50 IPv6-only)
Linode Nanode 1GB
1 vCPU, 1 GB, 25 GB SSD, 1 TB. $5/mo
UpCloud Starter
1 vCPU, 1 GB, 10 to 25 GB MaxIOPS. €3/mo (Premium €5)
Scaleway Dedibox VPS-START-2-XS
1 vCPU, 1 GB, 20 GB NVMe. €4.99/mo
Oracle Cloud Always Free
4 ARM OCPUs, 24 GB, 200 GB. $0

Oracle's free tier is the paper winner and comes with strings: Arm64 instances, strict identity checks, and an idle-reclamation policy that shuts down instances below 20% CPU for seven days. Scaleway's cheaper Stardust micro-instances lose their advantage once you add the €2.92/mo public IPv4. Hostinger bills on contract terms, so the headline price is the renewal rate.

The docker-compose file that works

yaml
services:
  emdash:
    image: ghcr.io/bitdoze/emdash-panel/emdash-site:latest
    restart: unless-stopped
    ports:
      - "4321:4321"
    environment:
      - NODE_ENV=production
      - HOST=0.0.0.0
      - PORT=4321
      - EMDASH_SITE_URL=https://cms.yourdomain.com
      - EMDASH_DATA_DIR=/app/data
      - EMDASH_DB=sqlite
      # Optional: Secret generated via npx emdash secrets generate
      - EMDASH_ENCRYPTION_KEY=replace_with_32_byte_hex_or_base64_key
    volumes:
      - emdash_data:/app/data
      - emdash_uploads:/app/uploads

volumes:
  emdash_data:
  emdash_uploads:

The two volumes are the part people get wrong: /app/data holds the SQLite database and config, /app/uploads holds media, and losing either loses content. Generate EMDASH_ENCRYPTION_KEY with npx emdash secrets generate instead of typing one, and set EMDASH_SITE_URL to the exact public HTTPS URL you will serve, because passkey login checks it character by character.

TLS and the reverse proxy, in one Caddyfile

caddy
cms.yourdomain.com {
    encode zstd gzip
    reverse_proxy 127.0.0.1:4321
}

Caddy issues and renews certificates on its own, which is why the research recommends it over nginx for this setup. The hostname in this file must match EMDASH_SITE_URL in the compose file (https://cms.yourdomain.com in both places) or WebAuthn rejects the login. Plain HTTP is not an option for the admin.

What you have signed up for

On this route you run the server. Certificate renewal is automated, but restores, monitoring, upgrades, Docker updates and host patching land on your calendar. Budget backups from day one (DigitalOcean sells automated droplet backups for $1.20/mo; OVH includes daily backups free). The honest version from someone who has done the math:

On Cloudflare, EmDash is effortless. But the second you decide to self-host to escape vendor lock-in, you realize you're trading WordPress's standard cPanel one-click installer for Docker, Caddyfile configs, node_modules volume permissions, and passkey origin headaches. Make sure your team actually wants to manage Linux containers before leaving Workers.

Agency technical leadReddit discussion, October to November 2026

Managed panels on your own VPS: Ploi, RunCloud and Cleavr

Managed panels on your own VPS

Ploi
Free (1 server), €8/mo Basic (5 servers), €13/mo Pro (10 servers plus backups). Docker server type plus Node/PM2; good for multi-server fleets
RunCloud
$9/mo Essentials (1 server), $19/mo Pro (50 servers). Docker templates plus Nginx reverse proxy; Docker setup needs more hand-holding
Cleavr
$15/mo Pro (unlimited servers), $30/mo Business. Node 22 first-class, PM2 clustering, zero-downtime SSR deploys, no Docker required

Not in the running: SpinupWP ($12/mo) and ServerPilot ($5/server plus $0.50/app) configure PHP/MySQL stacks only and cannot run Node or Docker, and Laravel Forge ($12 to $39/mo) is built for PHP and Laravel with no Docker orchestration, so Astro SSR there is marginal and needs manual reverse-proxy scripting.

EmDash Panel: hosting several sites on one VPS

For anyone ready to self host EmDash for more than one site, EmDash Panel (v0.2.0, MIT, released 19 October 2026) turns a single VPS into a small hosting platform. It is early release but functional end to end.

The emdash-panel GitHub repository showing version 0.2.0 and the MIT licence
EmDash Panel v0.2.0, MIT, 19 October 2026. Built by the publisher of this site.

What it handles for you

Each site gets its own container, Docker network and volume; Caddy 2.8+ terminates TLS with automatic certificates; new sites serve public content immediately while admin paths stay locked behind a panel-generated credential until you register a passkey. Backups are AES-256-GCM encrypted archives (SQLite snapshots via VACUUM INTO, or pg_dump -Fc for Postgres) on schedules from 6 hours to weekly with 1 to 90 retained copies, optional S3 sync, one-click restore and clone. Deploys are blue/green with health checks against /healthz, rollback on demand, and push-to-deploy webhooks for GitHub, GitLab and Gitea. Per-site CPU (100 to 8000 millicores) and RAM (128 to 16384 MB) limits adjust live, metrics sample every 15 seconds, and an ops tab runs emdash doctor and migrations. New sites start from a template, which is where EmDash themes come in.

Install, in one command

Fresh Ubuntu 22.04/24.04 or Debian 11/12 with ports 80 and 443 free:

bash
curl -fsSL https://raw.githubusercontent.com/bitdoze/emdash-panel/main/scripts/install.sh | sudo bash

For unattended setup (cloud-init, automation):

<!--ec:block {"type":"widgetcode","language":"bash","code":"curl -fsSL https://raw.githubusercontent.com/bitdoze/emdash-panel/main/scripts/install.sh \\

| sudo bash -s -- --hostname panel.example.com --base-domain sites.example.com --with-postgres --yes"} -->

The installer adds Docker if it is missing. Point an A record at the panel hostname and, optionally, a wildcard at the base domain so new sites get subdomains and certificates on creation.

Where it stops

One VPS, one owner: no client sub-accounts and no tenant billing. Deploy rollback reverts container code and images only; rolling back content means restoring a backup. The master key lives in /opt/emdash/env and every backup archive is encrypted with it, so a rebuilt server cannot restore anything without that file. Save it somewhere safe before you need it. Also stop a site before touching its data.db through the file manager: SQLite write conflicts against a live container are real.

Managed hosts, and the ones that do not exist yet

This is the EmDash CMS hosting market as of November 2026: three hosts run it for you, and several names people ask about do not. For the operator-side view, see our first-month field report, one month of EmDash, and the hosts that install it for you.

One hosting detail that gets skipped: forms need outbound mail, and the free Workers path has no SMTP. EmDash core now ships a native SMTP transport (merged to main on 6 November 2026, PR #2156), so a self-hosted install can send magic links and system email through any standard SMTP relay — Resend, SendGrid, or a self-hosted Postfix — straight from emdash.config.ts, with no third-party plugin or mail API in between. If you plan to run EmDash contact forms, pick a host with a mail relay or wire one up (WPMU DEV routes mail through its own relay). On Cloudflare, stopping form spam with Cloudflare Turnstile is the one setup that is simpler there than on a VPS.

DashHarbor: free beta now, $19/mo planned

Purpose-built managed EmDash. The free beta hosts 1 production site with no credit card, on one of the official starter templates (Marketing, Blog, Portfolio) under a shared yoursite.dashharbor.com subdomain. Custom domains are disabled during beta. The planned $19/mo tier per site adds custom apex and subdomain mapping with automatic SSL, recovery points with daily, weekly and monthly backups, staging environments, and selectable core update policies. There is no committed GA date, so treat the beta pricing as temporary.

DashHarbor pricing page showing the free beta website offer and the planned $19 per month tier
DashHarbor pricing, 3 November 2026: free beta, $19/mo planned for custom domains and backups.

xCloud: $0 BYOS, $5/server pro, $12 to $15 managed

An official one-click app that provisions EmDash in Docker behind Nginx, on your own cloud account (Hetzner, Vultr, DigitalOcean, AWS, GCP) or on xCloud's hardware. BYOS Free is $0/mo for one server with up to 10 sites (card on file for identity verification). BYOS Pro is $5/mo per server with unlimited sites, staging, team members, and external backups to S3 or Wasabi. Managed servers run $12 to $15/mo and bundle the VPS, Nginx, Let's Encrypt, and passkey registration through /_emdash/admin. Their one-click deployment guide is the page that matches the promise.

xCloud documentation page for deploying EmDash CMS in one click
xCloud's one-click EmDash guide, the BYOS tier is free for one server.

WPMU DEV: about $10 to $12/mo, WordPress agencies

Verified live on WPMU DEV's Unlimited Hosting VPS tier. The Hub deploys EmDash in one click with single sign-on into the admin, and wpmudev/emdash-sendmail routes transactional mail (magic links and notifications) through WPMU DEV's relay with no SMTP plugin. Nightly backups, staging, and storage tracking are included. Pricing starts around $10 to $12/mo. It is the natural pick for agencies already paying WPMU DEV for WordPress.

PikaPods, Elestio and Cloudron: not yet

Checked on 3 November 2026: Cloudron has community feature requests but no official EmDash package in its store, PikaPods does not list EmDash in its app catalog, and Elestio offers no managed template. Closest non-starters: SiteGround and WP Engine run strict PHP/MySQL stacks with no Node 22 or Docker support, and InstaWP publishes EmDash benchmarks but is a WordPress staging sandbox, not a production host.

Fly.io, Railway, Render, Vercel and Netlify: what works and what does not

The split is stateful containers against stateless functions. Long-lived container platforms with persistent volumes run the full EmDash stack, plugin sandbox included (workerd runs inside the container via a custom Dockerfile). Function platforms need the database and media moved off the box, and lose the sandbox regardless.

Deploy targets: what works and what does not

Railway
Yes, Railway volume. Custom Dockerfile. $5 base plus usage
Fly.io
Yes, Fly volume. Custom Dockerfile. $3 to $5
Render
Yes, Render disk. Custom Dockerfile. $7 plus $0.25/GB disk
Sevalla (Kinsta)
Yes, persistent disk at /app/data. Disk 10 GB to 1 TB, one replica per disk. $7 to $12 plus disk
Upsun (Platform.sh)
Yes, persistent mount. mounts: /data: storage in .upsun/config.yaml. $9 base plus $0.50/GB-mo storage
Coolify (self-hosted)
Yes. Your VPS and Docker. $0 (Cloud control plane $5, plus $3/server)
Vercel
No, ephemeral. External Postgres plus S3/R2, no plugin sandbox. $0 to $20
Netlify
No, ephemeral. External Postgres plus S3/R2, no plugin sandbox. $0 to $19
DigitalOcean App Platform
No, scratch space only. Managed Postgres +$15, Spaces +$5. $5 to $12 plus add-ons
AWS App Runner / Lightsail containers
No, ephemeral. RDS Postgres plus S3. $5 to $15
Google Cloud Run
No direct writes. Litestream to GCS with --max-instances 1, or Cloud SQL. Pay per use

Sevalla's persistent disk enforces a single instance per container, which happens to match SQLite's locking needs. Upsun runs the app container on one instance for the same reason. On the degraded side, the detail that proves the difference: Vercel preview URLs are fresh origins (*.vercel.app), so passkeys break on every preview deploy unless EMDASH_SITE_URL tracks each generated URL. Cloud Run cannot attach persistent disks at all, and mounting a bucket via FUSE lacks POSIX locking, which corrupts SQLite ("database is locked"). Coolify covers the container route from the other direction: self-hosted is free forever (Apache 2.0, one install script), while Coolify Cloud charges $5/mo for a managed control plane over two servers plus $3 per extra server, with the VPS still billed by your provider.

What hosting costs at each scale

EmDash hosting costs scale with site count and traffic, not with how much content you publish.

What EmDash hosting costs at each scale

Hobby brochure
Workers Free. $0
Small publication
Workers Paid. $5 plus usage
Agency with 10 sites
Hetzner CX22 plus EmDash Panel. €3.79 to €8
Zero-ops buyer
DashHarbor, xCloud or WPMU DEV. $0 to $19

A store changes the maths (webhooks, constant writes, and no idle-to-zero): if you are running a shop on EmDash, price the hosting against write limits first, because D1 writes and R2 operations are what grow the bill.

The verdict, by reader

One small site with no plugins → Workers Free

$0, 100,000 requests a day, nothing to operate. Watch the CPU-time metric for a week; exceededCpu errors mean you outgrew Free.

Plugins, or you expect traffic → Workers Paid

$5/mo unlocks the Worker Loader sandbox and a 30-second CPU budget per request. This is the default answer for a production site.

Several sites or clients → VPS + EmDash Panel

€3.79 to €8/mo covers 5 to 10 sites on one box. The panel takes over TLS, backups and deploys; you keep the server. If the ops still feel heavy, add Ploi or Cleavr on top.

You do not want a server → DashHarbor, xCloud or WPMU DEV

$0 to $19/mo. DashHarbor is the turnkey option while its beta lasts; xCloud and WPMU DEV are live today.

You already run Docker → plain compose, your own proxy

If you have a fleet and a pipeline, the compose file above is the whole deployment. Coolify or Dokploy add a UI on top.

The shortest path off Workers for most people is a €4 VPS and the panel's one-line install. If you try it, the repo's issue tracker is where rough edges get reported.

Common questions

Can you self-host EmDash without Cloudflare?

Yes. The standalone server runs on any glibc Linux VPS with Node 22.16 or newer, SQLite or PostgreSQL, and a reverse proxy for TLS. The compose file above is the whole deployment; nothing about the core requires Cloudflare infrastructure.

Do you need the $5 Cloudflare Workers Paid plan to run EmDash?

No for a brochure site, yes the moment either gate trips. Installing a sandboxed registry plugin requires the Worker Loader API, which is Paid-only, and dynamic pages that pass 10 ms of CPU time fail with the exceededCpu error on Free. Both gates lift at $5/mo.

Does EmDash work on Vercel or Netlify?

Technically yes through the Astro adapters, practically no without external PostgreSQL and S3/R2, and you lose the plugin sandbox because function sandboxes cannot spawn workerd isolates. Preview URLs also break passkey login unless EMDASH_SITE_URL tracks each generated origin.

How much RAM does an EmDash site need on a VPS?

About 128 MB idle and 256 to 512 MB under active rendering, image work, or plugin loading. Budget 1 GB for a single site and 2 to 4 GB for a box running Docker, Caddy, backups and the admin at once. Behavior of the local workerd sandbox on a 512 MB instance with swap is unverified, so do not build an agency fleet there.

Is EmDash hosting cheaper than WordPress hosting?

Workers Free is cheaper than both, a €4 VPS beats managed WordPress on price, and managed EmDash at $19/mo costs more than cheap shared WordPress hosting. My default: start on Workers Free or a €3.79 VPS, and pay for management only when an hour of your month is worth more than the difference.