The transparent PaaS

Free credit available Limited time

Not a black box. A glass box.

Every other PaaS hides the machine. A Selfhost.dev Project is a real dedicated server we run for you and keep in full view: drag a GitHub app, the databases it needs or one of 26 one-click configurations across 23 apps onto one canvas and wire them together. Nothing hidden and no server for you to maintain.

+$5.00 added automatically at signup · no card needed

GitHub auto-deploy / Postgres, Redis, MySQL, Mongo / Live metrics + logs / 2 to 48 vCPU, from ~$0.02/hr
Powered by Hetzner Cloud

Dedicated servers, run for you.

Hetzner
Dedicated project servers, run for you

Apps on dedicated single-tenant servers, 2 to 48 vCPU, from about $0.02/hr. A fraction of hyperscaler cost.

Provisioned and run for you, with no servers to babysit. You get dedicated performance; we handle the ops.

Architect your ecosystem

Managed application hosting
for your whole stack.
On one canvas, run for you.

Give it a name and you get a blank canvas. Drop on what you need: a GitHub repo that auto-deploys on every push, a PostgreSQL, Redis, MySQL or MongoDB database or one of 26 one-click configurations across 23 apps, each with custom domains and SSL handled for you. Orchestrate your code, databases and services from a single, unified view. More on running a full stack without the ops headache: our guide to full-stack app hosting. Or watch it happen, from repository to live URL, in four chapters.

->

Deploy from GitHub, auto-deploy on push, PR preview environments, rollbacks.

->

Any database: PostgreSQL (with pgvector), Redis, MySQL, MongoDB, one click each.

->

One-click apps: 26 configurations across 23 apps, from Supabase and n8n to GitLab and Open WebUI + Ollama.

->

Custom domains + SSL, add a domain, verify DNS, go live on HTTPS.

project: web
running

Services on this server

acme/web GitHub · auto-deploy
postgres database
redis database
supabase template
+ add a service

Deploy from GitHub

Push to deploy.
The rest is handled.

Connect the GitHub App or paste a public repo URL, pick a branch and flip on auto-deploy. We detect your build, ship it and keep it healthy. Browse everything you can deploy.

Auto-deploy on push

Toggle it on and every push to your branch ships automatically, with redeploy and one-click rollback when you need them.

PR preview environments

Open a pull request and get an isolated preview deployment to review changes before they reach production.

Auto-detected build packs

Nixpacks by default or use a Dockerfile, Docker Compose or static build. Set the base directory, port and ignore paths.

Environment variables

Paste a .env to import in bulk or set keys one by one. Wired into every build and deploy.

Streaming logs + health checks

Watch build and runtime logs live, with health checks that keep your service up and roll back a bad deploy.

Live metrics

CPU, memory and connections for the server and each service, from an agent running on the box.

Domains and SSL

Add a domain.
HTTPS handled for you.

Every project gets a wildcard subdomain on selfhost.dev out of the box. Bring your own domain when you are ready: add it, drop in the DNS records, verify with a TXT record and SSL goes live automatically. No certificate wrangling.

  • Default wildcard subdomain, instant
  • Custom domains with TXT verification
  • Automatic HTTPS, renewed for you

Project tabs

Information
Deployment
Domains
Variables
Metrics
Activity

Zero-trust architecture baked into every container.

AI-native

"Create a project and deploy my repo into it."
From your editor.

Projects, GitHub deployments, domains, env vars and project databases are covered by the 189 MCP tools across 31 modules. For one-click templates, MCP currently supports four configurations: Supabase, n8n (SQLite), n8n (Postgres) and Twenty; the console catalog is broader at 26. Use them from Claude, Cursor, Windsurf or any MCP client, with destructive operations gated behind explicit confirmation.

Explore the MCP server

A new kind of PaaS

The PaaS with the lid off.
The server, in plain sight.

vs DIY self-hosting (Coolify, Dokploy)

A dedicated server, without becoming a sysadmin.

Everything a DIY tool gives you, one-click databases, 26 one-click app configurations and GitHub deploys, but we run the box: no OS patching, no reverse-proxy debugging, no managing the host. You get the visibility; we handle the operations.

vs opaque PaaS (Railway, Render)

A real server you can see, not a black box.

A dedicated project server with live metrics, full logs and your databases right next to your code, billed by the hour. The deploy-in-seconds experience, with the machine in plain sight instead of hidden behind a dashboard.

It is a standard server running your containers, so there is no lock-in: you can take your stack elsewhere. See how Projects compares to the alternatives.

Sized for any workload

Three kinds of machine.
Six places to run them.

Pick the kind of machine your app needs, see exactly where we run it and what it costs there. Same drag-and-drop canvas, same live metrics and logs, same by-the-hour billing on every one of them.

1 · What kind of machine

2 · Where it runs

3 · Size

2 vCPU
4 GB RAM · 40 GB SSD Arm
~$0.02/hr
~$15/mo
2 vCPU
4 GB RAM · 40 GB SSD x86
~$0.02/hr
~$15/mo
4 vCPU
8 GB RAM · 80 GB SSD Arm
~$0.04/hr
~$29/mo
4 vCPU
8 GB RAM · 80 GB SSD x86
~$0.03/hr
~$22/mo
8 vCPU
16 GB RAM · 160 GB SSD Arm
~$0.08/hr
~$58/mo
8 vCPU
16 GB RAM · 160 GB SSD x86
~$0.06/hr
~$44/mo
16 vCPU
32 GB RAM · 320 GB SSD Arm
~$0.16/hr
~$117/mo
16 vCPU
32 GB RAM · 320 GB SSD x86 Sold out in Nuremberg right now
~$0.11/hr
~$80/mo

Same cores and memory on an Arm and an x86 row means the same machine size on a different processor, and the two are priced separately. Billed by the hour against prepaid credits. Stop the server and you pay nothing. You choose the location when you create the project and a server cannot be moved afterwards.

Pay only for what you run

From ~$0.02/hr to a 48 vCPU server.
Stop it and pay nothing.

Project servers are billed by the hour against prepaid credits, no tiers, no subscriptions. A full day on the smallest server runs about $0.50. Signing up adds $5 in free credit to your balance, no card needed. Top up from $5; run low and resources pause, then restart when you top up.

Build your exact bill

Frequently asked questions

Is Selfhost.dev a PaaS?
Yes, a transparent one. You get the deploy-in-seconds, drag-and-drop experience of a PaaS like Railway, Render or Heroku, but instead of a black box, a Project is a real dedicated server we run for you and keep in full view: live metrics, full logs and your databases right next to your code. You never touch the OS and nothing is hidden.
What is a Project on Selfhost.dev?
A Project is a dedicated managed server we run. Selfhost.dev provisions and runs the server and you place services on it: an app deployed from GitHub, databases (PostgreSQL, Redis, MySQL, MongoDB) or one of 26 one-click configurations across 23 apps. You get the control of a dedicated box without having to maintain it.
How do I deploy an app from GitHub?
Connect the GitHub App or paste a public repo URL, pick a branch and enable auto-deploy on push. Selfhost.dev auto-detects the build (Nixpacks, Dockerfile, Docker Compose or static), runs it and keeps it healthy. You also get PR preview environments, redeploys, one-click rollback and streaming logs.
Which databases can I run in a Project?
PostgreSQL, Redis, MySQL and MongoDB, each added as a one-click database on your project server. PostgreSQL in a project supports pgvector for vector search and embeddings. If you need a dedicated managed instance instead, Selfhost.dev offers managed PostgreSQL, MySQL, Redis and ClickHouse, with Multi-AZ across every managed engine and PITR and pooling on the SQL engines. See also the vector database page.
Can I deploy Supabase?
Yes. Supabase is one of 26 one-click configurations across 23 apps available in the console. The same catalog includes n8n, WordPress, GitLab, Open WebUI + Ollama and more, all deployed onto your project server.
How are custom domains and SSL handled?
Every project gets a wildcard subdomain on selfhost.dev by default. To use your own domain, add it, set the DNS records and verify with a TXT record, then HTTPS is provisioned and renewed automatically. There is nothing to configure on the certificate side.
How much does a Project cost?
Project servers are pay-as-you-go, billed by the hour against prepaid credits, with no tiers. Servers range from a 2 vCPU box at about $0.02/hr (a full day is about $0.50) up to a 48 vCPU, 192 GB machine at about $3.23/hr. Signing up adds $5 in free credit to your balance, no card needed; top up from $5 and resources pause at a zero balance rather than surprise-billing you. See pricing.
What server sizes can I choose?
You pick the server when you create a Project: 19 sizes across three families, from 2 vCPU / 4 GB up to 48 vCPU / 192 GB, with 40 GB to 960 GB of SSD, from about $0.02 to $3.23 an hour. Cost-Optimized and Regular are shared CPU; Dedicated CPU gives you cores nobody else can touch. Every size gets the same drag-and-drop canvas, live metrics and logs, so you can start small and move up as your workload grows.
Where do Projects run?
On dedicated servers in one of six locations: Germany (Falkenstein, Nuremberg), Finland (Helsinki), the United States (Ashburn, Hillsboro) and Singapore. You choose which one when you create the project. Which locations are open depends on the machine you pick and if you would rather not choose, we place it in an available one. Managed databases, by contrast, run on AWS with worldwide regions.
How is a Project different from managed PostgreSQL?
A Project is a server for your apps and their databases, ideal when you want code and data in one place you control. Managed PostgreSQL, MySQL, Redis and ClickHouse are dedicated database instances on AWS with BYOC and Multi-AZ across every managed engine, plus PITR and connection pooling on the SQL engines. Many teams use both a Project and a managed database, billed together on one account. Compare the two.
Can I manage Projects with AI?
Yes. Creating projects, GitHub deployments, domains, env vars and project databases are covered by the 189 MCP tools across 31 modules. For one-click templates, MCP currently supports four configurations: Supabase, n8n (SQLite), n8n (Postgres) and Twenty. The console catalog is broader at 26 configurations. See the MCP server.
How is Projects different from Railway, Render or Heroku?
Those are opaque PaaS platforms: you deploy into a black box and get a usage-based bill. A Project is a dedicated server you can see, with live metrics, full logs and your databases next to your code, billed by the hour. You get the deploy-in-seconds experience on infrastructure you actually control. See the Railway comparison.
How is Projects different from Coolify or Dokploy?
Coolify and Dokploy are DIY self-hosting tools, you run and maintain the server yourself (OS patching, reverse proxy, uptime). A Project gives you the same control plus one-click databases, 26 app configurations and GitHub deploys, but Selfhost.dev runs the box for you, so there is no sysadmin work.
Can I run a full-stack app (frontend, backend and database) in one Project?
Yes. A Project is a canvas for your whole stack: drop on a frontend, a backend from GitHub, the databases they need and any of 26 one-click configurations, then wire them together in one view. They run on the same server, provisioned and managed for you.

Your code and your data.
On a server in full view, run for you.

From ~$0.02/hr, pay-as-you-go
GitHub deploys, databases, 26 app configurations
Launch a project