Hosting by stack

Start from what you are deploying. Each page lists only the providers that publish their own documentation for that stack, with a link to the guide.

Frameworks

AstroContent-focused framework that ships zero JavaScript by default and renders components from several UI libraries.7 providers Next.jsReact framework with file-based routing, server components and a build step that produces both static and server-rendered output.7 providers NuxtVue framework with file-based routing and a choice of static, server-rendered or hybrid output.7 providers SvelteKitSvelte application framework that targets different deployment platforms through adapters.7 providers

Backend

DjangoPython web framework with an ORM, admin interface and long-running server process.5 providers LaravelPHP web framework with an ORM, queue workers and a scheduler that expects a persistent process.4 providers

self-hosted

GhostOpen-source publishing platform running as a long-lived Node process, requiring MySQL in production and a writable content directory for uploads and themes.3 providers n8nOpen-source workflow automation tool deployed from an official Docker image, storing workflows, credentials and execution history that must survive redeploys.3 providers Plausible AnalyticsOpen-source web analytics deployed as a Docker Compose stack, requiring PostgreSQL for application data and ClickHouse for the event store.1 — not enough

Runtimes

Node.jsJavaScript runtime used to run servers and build tooling outside the browser.7 providers

CMS

WordPressPHP content management system that requires a database and persistent filesystem for uploads and plugins.4 providers