Neckrez

Self-hosting VPS, paid in crypto

Run your own cloud storage, password manager, Git server or VPN on a server you control. Hourly billing, full root, no identity check.

In short

Self-hosting means running the services you use, such as file sync, a password manager, a Git server, a VPN or a photo library, on a server you control instead of renting them as someone else's product. A small VPS is the usual way to do it: you get full root and a dedicated IPv4 in about a minute, pay by the hour from a crypto balance, and need no identity check.

This page covers what is worth hosting yourself, what it really costs you in time, and a short setup that is safe by default.

Why people self-host

  • Your data stays in your hands. Files, passwords and photos live on a machine you configure, not in a vendor's account that can change its terms.
  • Fewer subscriptions. One small server can replace several monthly fees.
  • You choose what runs. No features removed, no service shut down on someone else's schedule.
  • You learn how it works, which is half the point for many people.

What it costs you

Self-hosting trades money for effort, and it is worth being honest about that. You become the administrator: you install updates, watch for failures, set up backups and keep the server secure. A hosted product does all of that for you. If you do not want that job, a hosted service is a fair choice, and self-hosting suits people who do.

What to host

Our deploy page offers a set of ready-made apps, so some of these start in one step. The list depends on the provider, and anything else runs in Docker.

  • Nextcloud for files, calendar and contacts. Ready-made on Vultr and Hetzner.
  • WireGuard and OpenVPN for your own VPN. See VPS for VPN.
  • GitLab for your own Git hosting and CI. Ready-made on Hetzner.
  • Docker on Vultr, DigitalOcean and Hetzner, for everything else: a password manager such as Vaultwarden, Gitea or Forgejo, Matrix, an uptime monitor, an automation tool.
  • Photoprism, Jitsi, RustDesk, Owncast, Coolify and Grafana are also offered ready-made on Hetzner.

How big a server

Most self-hosted tools are light. A password manager or a small Git server runs on the smallest plan, and a handful of small services fit in 2 to 4 GB of RAM. File sync, photo libraries and anything that indexes or transcodes want more memory and a bigger disk, so check what the project recommends and start one size up. Because billing is hourly, you can move to a bigger plan later without losing anything.

A safe setup in a few steps

  • 1. Deploy Ubuntu or Debian, and tick the limited user option if you want a normal sudo user instead of root.
  • 2. Log in with an SSH key, not a password, and update the system.
  • 3. Turn on a firewall that allows only SSH, HTTP and HTTPS.
  • 4. Install Docker with the one-click app, or by hand, and run your services as containers.
  • 5. Put a reverse proxy in front, so every service is reached over HTTPS on your own domain.
ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

A reverse proxy such as Caddy gets and renews the HTTPS certificate on its own. Point your domain's A record at the server's IPv4, then a block like this is all it takes:

cloud.example.com {
    reverse_proxy localhost:8080
}

Never expose a database or an admin panel directly to the internet. We check our own servers for database and admin ports open to the world and warn the owner, because exposed databases are the most common way a self-hosted server gets taken over.

Backups, or you will regret it

A server is not a backup. Take an on-demand snapshot from the panel before big changes: it is kept 7 days and works on all three providers. On Vultr you can also add automatic daily backups at deploy time. Beyond that, keep your own copy of the data somewhere else, and restore it once to check that it works.

What privacy it gives, and what it does not

Self-hosting keeps your data out of third-party products, but a VPS is still a machine in someone else's data centre. We do not read your files, yet the provider and we both could in principle reach the disk. For anything truly sensitive, encrypt it with keys that never leave your devices. See Anonymous VPS for how we think about privacy.

How to start with crypto

  • 1. Sign up with an email. No KYC, no ID, no phone and no card.
  • 2. Top up the balance in crypto. Bitcoin, USDT, ETH, Monero, TON or any of 300+ coins; the minimum top-up is $15.
  • 3. Pick a plan and a city, then an OS or one of the ready-made apps.
  • 4. Set it up with the steps above.
  • 5. Keep it or destroy it. Billing is hourly, so an afternoon of trying a stack costs a few cents.

FAQ

What is self-hosting? Running services such as file sync, a password manager or a Git server on a server you control, instead of using them as a hosted product.

How much RAM do I need? A password manager or small Git server fits on the smallest plan. A few small services fit in 2 to 4 GB. File sync, photos and anything that transcodes want more.

Is it safe? It can be, if you use SSH keys, a firewall, HTTPS, regular updates and never expose databases or admin panels. You are the administrator, so these are your job.

Do I need a domain? For HTTPS on your own address, yes. You can reach a service by IP for testing, but a domain is what makes it practical.

Can I pay without a card or identity check? Yes. You sign up with an email and pay with Bitcoin, USDT, ETH or any of 300+ coins.

Can I move to a bigger server later? Yes. Take a snapshot, deploy a bigger plan and restore, or set up the new one beside the old and switch. Billing is hourly, so overlap costs little.