The transparent PaaS

Not a black box. A glass box.

Every other PaaS hides the machine. A Project is a real dedicated server we run for you and keep in full view: drag a GitHub app, the databases it needs, and a one-click Supabase onto one canvas, wire them together, and watch every service run live, down to the CPU, memory, and logs. Deploy-in-seconds ease, nothing hidden, no server for you to maintain.

$1 welcome credit, about 2 days free. Pay only for what you run.

GitHub auto-deploy / Postgres, Redis, MySQL, Mongo / Live metrics + logs / 2 to 16 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 16 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 a one-click Supabase template, 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.

->

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

->

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

->

One-click Supabase, the open-source stack, on a server you control.

->

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, deployments, domains, env vars, and databases are all in the 150+ MCP tools across 23 modules. Drive the whole thing 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, Supabase, 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

From a side project to a production team.
Pick your server. The same glass box at every size.

Not just for hobby apps. Choose your server when you create a Project, from a 2 vCPU starter to a 16 vCPU, 32 GB machine, and get the same drag-and-drop canvas, the same live metrics and logs, and the same by-the-hour pricing on every one.

Small
2 vCPU
4 GB RAM ยท 40 GB SSD
~$0.02/hr (~$15/mo)
Medium
4 vCPU
8 GB RAM ยท 80 GB SSD
~$0.03/hr (~$22/mo)
Large
8 vCPU
16 GB RAM ยท 160 GB SSD
~$0.06/hr (~$44/mo)
XL
16 vCPU
32 GB RAM ยท 320 GB SSD
~$0.11/hr (~$80/mo)

Billed by the hour against prepaid credits. Stop the server and you pay nothing. Projects run on dedicated servers in our EU data centers (Germany and Finland), with region selection on the way.

Pay only for what you run

From ~$0.02/hr to a 16 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 gets you a $1 welcome credit, about 2 days of a project server free, 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 a one-click Supabase template. 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 available as a one-click template you deploy onto your project server, the open-source stack on a server you control, with no servers for you to maintain. It is the live template today.
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 16 vCPU, 32 GB machine at about $0.11/hr. Signing up gets you a $1 welcome credit worth about 2 days, 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: 2 vCPU / 4 GB, 4 vCPU / 8 GB, 8 vCPU / 16 GB, or 16 vCPU / 32 GB, with 40 to 320 GB of SSD, from about $0.02 to $0.11 an hour. 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 our EU data centers, in Germany (Falkenstein, Nuremberg) and Finland (Helsinki). You choose the server size and we place it in an available EU location; picking a specific region yourself is on the roadmap. 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, deploying, managing domains, env vars, and databases are all covered by the 150+ MCP tools across 23 modules. Run it from Claude, Cursor, Windsurf, or any MCP client in natural language. 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, Supabase, 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 a one-click Supabase, and 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, Supabase
Spin up a project