What’s the Best Self-Hosted, De-Googled Service Stack?

I’m trying to reduce my reliance on Google by moving email, cloud storage, calendars, photos, and productivity tools to self-hosted alternatives. I need help choosing a secure, reliable, and manageable de-Googled service stack that works well together.

If you want maximum control, self-host mail; if you want reliability without a second job, outsource mail to a privacy-focused provider and host the rest. A sensible stack is Nextcloud for files, calendars, contacts, and office apps, Immich for photos, and Vaultwarden for passwords. If email must be self-hosted, run Mailcow on a separate VPS and expect DNS, reputation, and deliverability work. (docs.mailcow.email) Whatever you choose, prioritize MFA, prompt updates, off-site backups, and tested restores. Immich especially should never be the only copy of your photos.

Start by moving one low-risk service, such as calendars or contacts, and run it for a month before migrating everything else. The best stack is the one you can still update, monitor, and restore six months later, so resist building five separate apps when a simpler setup covers most of your needs.

Expect email to be the service that breaks the “self-host everything” plan. @j.collins is right about migrating gradually, but I’d keep mail with a privacy-focused provider and self-host Nextcloud for files, calendars, contacts, and office documents, plus Immich for photos. That gets most data off Google without turning spam filtering, deliverability, and IP reputation into a second job.

If this is mainly for one person or a household, the answer changes quite a bit: you probably do not need a large, internet-facing “Google replacement” at all. A private stack accessed through a VPN is easier to secure than exposing Nextcloud, Immich, an office suite, and several admin panels to the public web.

For a mostly solo setup, I would compare the options this way. Nextcloud gives you one login and a familiar web interface, but it carries more maintenance and can feel heavy if you only need file sync, contacts, and calendars. Syncthing plus Radicale is much smaller and easier to troubleshoot, though it lacks the polished portal and sharing features. Immich makes sense when photo browsing, search, and phone uploads matter. Plain file synchronization is safer and simpler when all you want is an off-device photo copy. For documents, OnlyOffice or Collabora can cover occasional browser editing, but neither automatically recreates the smooth Google Docs experience, especially once several people are editing from phones and tablets.

I agree with keeping email elsewhere, but I would go further: treat email, DNS, and domain registration as infrastructure that should not depend on the same server. If your home server dies, you still need to receive password resets, outage alerts, and renewal notices. Using one machine for mail, files, authentication, backups, and monitoring creates an impressive-looking stack with a very unimpressive failure mode.

My practical version would be a privacy-focused mail provider, Nextcloud only if its sharing and groupware features are genuinely useful, Immich for the photo interface, and Vaultwarden for passwords. Put private services behind WireGuard or Tailscale rather than publishing everything. Keep DNS, backups, and monitoring independent of the main host. The overlooked comparison is not “which app has the most features,” but “how many separate databases and upgrade procedures am I willing to own?” A slightly boring stack with three maintained services usually beats a perfect de-Googled diagram containing twelve containers and a custom identity system.

Careful with Immich if you plan to set it and forget it. It’s still moving fast, and skipping releases or not reading the breaking-change notes before you update is a good way to end up with a container that won’t come back up right when you least want it to. That doesn’t mean avoid it, the photo experience is genuinely nice, but treat every update as something you do deliberately, not on autopilot. @mike34 nailed the real question, which is how many separate upgrade paths you’re willing to babysit, and Immich is one of the ones that actually demands attention. If that sounds like a chore, the plain file-sync route for photos really is less headache, just uglier. Also worth saying out loud: a backup you’ve never restored isn’t a backup, it’s a hope. Pull a real file out of your off-site copy once before you trust it with the only copy of anything.

Account recovery is the missing design problem here. If your email, password vault, DNS credentials, MFA seeds, and single sign-on all depend on the same server, a routine outage can lock you out of the tools needed to repair that outage.

Keep a small recovery path outside the self-hosted stack. That means independent registrar and DNS accounts, hardware security keys where supported, printed recovery codes, and an encrypted offline copy of essential credentials. Do not store the only copy of your server password inside Vaultwarden running on that server. Likewise, skip centralized SSO until the basic services are stable. Authentik or Authelia can make daily use cleaner, but they introduce another database and another way for every application to fail at once.

I would build around replaceable standards rather than trying to reproduce Google as a single portal:

  • Hosted email on your own domain, using normal IMAP and SMTP clients. Owning the domain makes changing providers much less painful.
  • Nextcloud if you actually need browser sharing, contacts, calendars, and multiple users. If you mainly work from your own devices, separate file sync and CalDAV/CardDAV services can be easier to repair.
  • Immich for the photo interface, with original files stored and backed up in a form that remains useful without Immich. Albums, face recognition, and application metadata may not transfer neatly to another program, so the directory of originals should be treated as the durable copy.
  • Local office software plus synchronized files for most document work. OnlyOffice or Collabora makes sense when browser editing is a real requirement. Running an online office suite for one person who normally edits on a laptop adds quite a lot of machinery for little gain.
  • Vaultwarden for convenience, but with periodic encrypted exports and recovery material kept somewhere independent.

This is where I slightly disagree with treating “one login” as an automatic benefit. A unified login is pleasant after the system is mature. During setup, it can turn a broken certificate, identity-provider update, or DNS mistake into a stack-wide outage. Separate credentials are less elegant, but they give you more ways back in. You can consolidate later once you know which services are staying.

Migration needs similar care. Google Takeout gives you data, but it does not necessarily preserve the way you used that data. Shared Drive permissions, Photos albums, document comments, calendar invitations, and Google-native document formatting can require manual cleanup. Move a copy first, validate it with the clients you plan to use, and leave the Google account intact until you have checked ordinary tasks such as accepting calendar invitations, searching old mail, uploading from a phone, and opening documents on another device.

The “best stack” is therefore less about choosing the perfect container list and more about making every component removable. You should be able to replace the mail provider without changing addresses, replace the calendar server without rebuilding contacts by hand, and recover photo originals without starting Immich. If a service cannot be exported in a common format or read without its database, treat that as lock-in even though the software is self-hosted.

For a household, my practical answer would be hosted mail on a custom domain, Nextcloud for groupware and shared files, Immich only for people who want its photo features, local office applications by default, and Vaultwarden with an offline recovery plan. Keep SSO out of the first version. That stack is not completely independent of outside providers, but it removes most Google dependence while preserving a sane failure and exit path.

Do not start by deploying twelve containers and calling the resulting login page “your new Google.” If uploading a photo, accepting a calendar invite, or sharing a file takes extra explanation, everyone in the household will quietly return to Google while your immaculate dashboard gathers dust.

I would choose based on client behavior rather than server features: hosted email on your own domain, Nextcloud for files and DAV sync if you need sharing, Immich only if its mobile upload and browsing features matter, and ordinary desktop office software for documents. Test the actual phones, laptops, calendar invitations, contact sync, and external share links before migrating years of data. A feature existing in the web interface does not mean it works pleasantly from a phone at 7 a.m.

I would push back slightly on putting everything behind a VPN. That is sensible for admin panels and a solo setup, but it gets annoying when relatives need shared albums, someone changes phones, or you want to send a file to an outside person. Expose only the services that genuinely need public access, put the rest behind the VPN, and avoid pretending that maximum isolation automatically equals usability. The best stack is the smallest one people will actually use without asking you to become unpaid family tech support.