I am a tax accountant in Japan. I have been working in IT for over forty years — starting from an era when source code was compiled overnight.

Last year I sat down and added up what my small practice was paying for SaaS: cloud storage, document collaboration, AI assistants, calendar, email, remote desktop, monitoring. The number was $163 per user per month. I decided to see whether I could build a self-hosted replacement that I actually understood and controlled.

This is what I ended up with, running in production on real client work every day:

  • VPS: Vultr, $24/month, Ubuntu 24.04 LTS
  • Access: Cloudflare Zero Trust (free tier) — 2 open ports, no VPN, no exposed SSH
  • Cloud + editing: Nextcloud + Collabora Online
  • AI: Unified proxy for ChatGPT, Claude, Gemini, Perplexity (~100 lines of Node.js)
  • Automation: OpenClaw (≥2026.1.29, patched for CVE-2026-25253)
  • Remote desktop: Apache Guacamole through 5 authentication layers
  • Monitoring: Prometheus + Grafana + Alertmanager
  • Backups: Nightly DB to Supabase + weekly AES-256 encrypted config archive

Total for a 3–8 person team: approximately $35–50/month.

I wrote a five-part guide covering the entire build. Every command, every configuration file, every place where I made a mistake. It is free and will remain so.

A few things I learned that may be useful to others here:

  1. Cloudflare Tunnel eliminated the need for a VPN entirely. Two ports open, everything else invisible. This was the single biggest simplification.
  2. The hardest integration was not the AI proxy — it was getting Collabora’s aliasgroup configuration to work correctly with Cloudflare’s TLS termination.
  3. OpenClaw’s CVE-2026-25253 (CVSS 8.8) is a serious concern. The architectural defense — localhost-only binding plus tunnel authentication — neutralizes it structurally, but it should not be deployed without understanding the risk.
  4. The most underrated component is Supabase as a backup target. PostgreSQL-to-PostgreSQL with zero format conversion.

I would be grateful for any feedback from this community. If you see something I could improve, or a better approach to any part of this stack, I would genuinely like to hear it.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 month ago

    Hmmmh. I think you better find a way to deal with it, mentally. That circus isn’t going to go away.

    I wish people would pay more attention. I think it’s a bit sad an article like this always gets dozens of upvotes anyway.

    • greyscale@lemmy.grey.ooo
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      Eventually the circus has to go away because the cost of tokens is too high - its literally cheaper to train software developers.

      Also, the cost to business from having business-continuity-ending events is gonna eat some of these businesses.

        • greyscale@lemmy.grey.ooo
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          Ha. Eventually, the bottom will drop out the market as low-cost NPUs pick up the model running. A good enough open model will emerge and there wont be a market for a paid model.

          We’re already kinda seeing it on the hardware side. Eventually it’ll all dissolve into the hardware like how MPEG2 decode hardware for DVDs was once upon a time an expensive addon accellerator card, but is now fractions of a square mm of gates laid out as part of a larger assembly within the silicon of your GPU.