If you've ever stopped to think about how many Google services run in the background of your daily life, the number is probably higher than you'd expect. Gmail, Google Drive, Google Photos, Google Calendar, Google Analytics, Google DNS, they're deeply embedded in both personal and professional workflows. And they're "free," which is convenient until you remember what's being exchanged for that convenience: your data.
DeGoogling: the process of replacing Google services with privacy-respecting alternatives has become increasingly common among developers, sysadmins, and privacy-conscious users. Self-hosting is one of the most effective ways to do it. Instead of trusting a third party with your data, you run the software yourself on infrastructure you control.
This article covers why you'd want to deGoogle, which tools are worth replacing, and how to get started self-hosting the most common alternatives on a VPS.
Why you'd want to deGoogle
The case for deGoogling isn't really about paranoia, it's about data ownership and control. When you use Google services, your emails, files, search queries, and browsing habits are processed, indexed, and used to build an advertising profile. Even if you trust Google's intentions today, you're still dependent on a single company's terms of service, uptime, and pricing decisions.
There are a few practical reasons to make the switch:
Privacy: Google processes your data to serve targeted ads. Self-hosted services don't. Your email stays on your server; your files aren't scanned.
Control: You decide what software version runs, what data gets stored, and who has access. No surprise feature removals or forced UI changes.
Cost at scale: Google Workspace charges per user. Running your own mail or file server often works out cheaper once you're past a handful of users.
Compliance: For certain industries, keeping data on infrastructure you control in a known jurisdiction matters. A VPS in the Netherlands, for example, falls under EU privacy law rather than US data-sharing obligations.
What to replace and with what
You don't have to switch everything at once. Most people start with one or two high-value services and expand from there.
Gmail → Stalwart Mail or Maddy
Running your own mail server has a reputation for being painful, but modern self-hosted options have simplified the process significantly. Stalwart Mail is a full-stack mail server (SMTP, IMAP, JMAP) written in Rust, with built-in spam filtering and modern security defaults. It's a solid choice if you want something well-maintained and performant.
For smaller setups, Maddy is another clean option with a simpler configuration model.
The main consideration with email is deliverability — your server's IP needs a clean reputation, and you'll need to configure SPF, DKIM, and DMARC records properly to avoid landing in spam.
Google Drive → Nextcloud or Seafile
Nextcloud is probably the most widely used self-hosted Google Drive replacement. It covers file sync and sharing, but also has apps for contacts, calendar, tasks, and video calls: effectively replacing a big chunk of Google Workspace in one install. It's PHP-based, so it runs on almost any Linux stack.
Seafile is a leaner alternative if you only need file sync. It's faster than Nextcloud at handling large numbers of files and has a cleaner sync client.
Google Photos → Immich
Immich is a self-hosted photo and video backup solution that closely mirrors the Google Photos experience, including mobile apps, facial recognition, and timeline browsing. It's actively developed and has become the go-to recommendation in the self-hosting community over the last couple of years.
It requires Docker and a reasonably capable machine (machine learning features need a bit of RAM), but the setup process is well-documented.
Google Analytics → Plausible or Umami
If you run a website, replacing Google Analytics is one of the easier wins. Plausible Analytics and Umami are both lightweight, privacy-friendly analytics tools you can self-host. They don't use cookies, don't track individual users, and give you the traffic insights you actually care about without feeding data to Google.
Both run well on a small VPS with Docker.
Google Search → SearXNG
You can't truly self-host a web search index, but you can run your own SearXNG instance — a meta-search engine that queries multiple sources (including Google, if you want) without revealing your identity to them. It's a good middle ground for privacy without giving up search quality.
Google DNS → Unbound or AdGuard Home
Switching away from 8.8.8.8 is simple and often overlooked. Unbound is a lightweight recursive resolver you can run locally or on a VPS. AdGuard Home adds DNS-level ad and tracker blocking on top, which is useful as a household or team DNS server.
How to get started
Self-hosting doesn't require a powerful machine. Most of these tools run comfortably on a VPS with 2–4 vCPUs and 4–8 GB of RAM, depending on what you're running and how many users you have.
Step 1: Pick a VPS
You want a provider that gives you root access, a clean IP, and good uptime. For privacy reasons, hosting in a jurisdiction with strong data protection law is worth considering. The Netherlands is a common choice, partly because of GDPR compliance and partly because of excellent connectivity. Check out why Netherlands web hosting is popular for more context, or browse the best VPS providers in the Netherlands if you're comparing options.
Step 2: Set up your server
A fresh Ubuntu or Debian install is a sensible starting point. Secure it before installing anything else: disable root SSH login, set up key-based authentication, configure a firewall (UFW works fine for most setups), and install fail2ban.
apt update && apt upgrade -y
ufw allow OpenSSH
ufw allow 80
ufw allow 443
ufw enableStep 3: Install Docker
Most self-hosted apps now ship Docker Compose configs, which makes deployment much simpler than managing dependencies by hand.
curl -fsSL https://get.docker.com | shStep 4: Deploy your first app
Start with something low-stakes — Plausible or Umami for analytics, or SearXNG for search. Each has a Docker Compose file in its documentation that gets you running in under 10 minutes.
For Nextcloud or Immich, follow their official quickstart guides carefully; both have environment variables and volume mounts to configure, and getting those right from the start saves headaches later.
Step 5: Set up a reverse proxy
If you're running multiple services on the same VPS, you'll want a reverse proxy to route traffic by subdomain and handle TLS. Caddy is the easiest option — it automatically provisions Let's Encrypt certificates and its config syntax is straightforward.
files.yourdomain.com {
reverse_proxy localhost:8080
}
analytics.yourdomain.com {
reverse_proxy localhost:3000
}Step 6: Plan for backups
Self-hosting means you're responsible for your own data. Make sure you have automated backups; either offsite snapshots, an S3-compatible object store, or both. Don't skip this step.
What you're trading off
Self-hosting isn't free effort. You're trading convenience and zero-maintenance for control and privacy. Things break, updates need applying, and you'll occasionally need to debug something at an inconvenient time.
That said, the operational overhead is lower than it used to be. Docker Compose, well-documented projects, and active communities have made self-hosting accessible to anyone comfortable on the command line.
The privacy and cost benefits tend to outweigh the maintenance burden for most people who commit to it, especially for services handling sensitive data like email and files.
Conclusion
DeGoogling doesn't mean giving up functionality. The open-source ecosystem has mature, actively maintained alternatives for almost everything Google offers, and running them on your own infrastructure is more accessible than it's ever been.
If you're exploring fast and scalable hosting for your self-hosted stack, QDE provides high-performance VPS in the Netherlands backed by NVMe storage and 10 Gbps uplinks — a solid foundation whether you're starting with one service or running a full suite.
Ready to start or need advice? Contact our team to find the best fit for your project.
Frequently asked questions about deGoogling and self-hosting
Is self-hosting really more private than using Google?
Yes, assuming your server is secured properly. When you self-host, your data stays on infrastructure you control and isn't processed by a third party for advertising purposes. The privacy benefit depends on how well you maintain and secure your setup.
Do I need a dedicated server, or will a VPS work?
A VPS is usually sufficient. Most self-hosted apps are designed to run efficiently on modest hardware. A 2-core VPS with 4 GB of RAM handles Nextcloud, Plausible, and a mail server simultaneously with room to spare for light usage.
What's the hardest part of self-hosting email?
Deliverability. Getting mail delivered to Gmail and Outlook inboxes (rather than spam folders) requires a clean IP reputation and correctly configured SPF, DKIM, and DMARC records. If your VPS IP is new or previously flagged, this can take some effort to sort out.
Can I self-host on a home server instead of a VPS?
Yes, but a VPS has advantages: static IP, reliable uptime, and no exposure of your home IP. Home servers work well for internal tools or services that don't need to be accessible from the internet.
How do I handle updates for self-hosted apps?
Most Docker-based apps update with docker compose pull && docker compose up -d. Setting up Watchtower can automate this, though for production setups it's worth reviewing changelogs before pulling major version updates.
Is self-hosting legal?
Running open-source software on your own server is legal in essentially every jurisdiction. Just make sure you comply with any relevant data protection laws if you're handling other people's data — GDPR applies if you're in or serving users in the EU.
Where can I learn more about privacy-friendly hosting?
The best privacy-friendly hosting providers guide on QDE is a good starting point, as is the broader self-hosting community on Reddit and various forums.