r/SelfHosting • • 24d ago

Honey we have Streaming at Home!

Post image
878 Upvotes

full flow of my homelab/networking stack. Im sastifed so far and i’ve been able to cut pretty much all of my streaming services. Pangolin allows me to share my Jellyfin server to friends and family without the complexity of having them download Tailscale. Navidrome + octo gives me the Apple Music experience. Navidrome for my music and octo which allows me to look up songs/artists via the search bar and return their latest music. Happy Self Hosting!!


r/SelfHosting • • Feb 15 '26

Self-hosting email in 2026 is effectively impossible. Here's why.

547 Upvotes

I tried to self-host my email server to escape Gmail surveillance. Here's what I learned:

The barriers:
Gmail/Outlook blacklist residential IPs by default
SPF/DKIM/DMARC configuration is deliberately arcane
One misconfiguration = all your emails go to spam forever
Maintaining reputation scores is a full-time job
Microsoft/Google can arbitrarily block your domain
Zero recourse if you get blacklisted
Your server goes down for an hour? You lose emails permanently

The result - Email has become a centralized oligopoly.

Three companies (Google, Microsoft, Apple) control 90%+ of email infrastructure. If they don't like you, you're done. No appeals, no alternatives.

This is by design. The technical barriers aren't accidents - they're moats. Big email providers benefit from making self-hosting impossible.

Questions:
Why is email so hostile to self-hosting when the protocol was designed to be decentralized?
What would it take to make email decentralized again?
Or should we just accept that email is dead and build something new?


r/SelfHosting • • Feb 03 '26

Cheap VPS hosting, best low-cost providers?

320 Upvotes

I want to run my own game server and need something like 2x vCore CPU, 2 GB RAM, and enough bandwidth to avoid lag. So, just looking for a cheap, good quality VPS. A bit hesitant due to mixed reviews. Any good recommendations?


r/SelfHosting • • Sep 13 '26 Bravo Heartwarming

Thingport – a self-hosted 3D print model library that pulls your MakerWorld/Printables/Thingiverse collection into one place

Thumbnail
gallery
276 Upvotes

Like a lot of people here, my 3D-printable models were scattered everywhere — bookmarks across MakerWorld, Printables, and Thingiverse, random downloaded ZIPs, half-organized folders. I built Thingport to fix that for myself, and figured it might be useful to others here too.

What it does

  • Personal, self-hosted library for your 3D printing models

  • Import directly from MakerWorld, Printables, and Thingiverse links (or whole collections)

  • In-browser 3D preview (STL/OBJ/3MF) — no slicer needed just to look at a model

  • Organize with categories, collections, and tags (with casing-aware merging, bookmarkable tags, etc.)

  • Keeps the original source link and metadata alongside the files

  • Multi-user with admin controls (users, logs, storage settings, instance-wide update checker)

  • Dark mode, multi-language UI (English/Lithuanian so far)

Two small companion tools, if you want them

  • Thingport Grab — a Chrome extension that imports a model straight from MakerWorld/Printables/Thingiverse's own page, no copy-pasting links

  • Thingport Bridge — a tiny helper so "Open in Slicer" actually works for slicers (Bambu Studio, PrusaSlicer) whose own URL-protocol handlers only trust a domain allowlist your self-hosted instance isn't on

Stack: React + Three.js frontend, Node/Express + PostgreSQL backend, all Dockerized.

Running it

Pre-built, multi-arch images (amd64 + arm64 — runs fine on a Pi or ARM NAS), no build step. Drop these two files in a folder and run docker compose up -d:

docker-compose.yml:

services:
  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_USER=${POSTGRES_USER:-thingport}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-thingport}
      - POSTGRES_DB=${POSTGRES_DB:-thingport}
    volumes:
      - thingport_db:/var/lib/postgresql/data
    networks: [app-net]
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-thingport}"]
      interval: 5s
      timeout: 5s
      retries: 10

  flaresolverr:
    image: ghcr.io/flaresolverr/flaresolverr:latest
    restart: unless-stopped
    networks: [app-net]

  backend:
    image: ghcr.io/tautvydasderzinskas/thingport-backend:latest
    restart: unless-stopped
    environment:
      - INITIAL_ADMIN_EMAIL=${INITIAL_ADMIN_EMAIL:-}
      - AUTH_SECRET=${AUTH_SECRET:-changeme-secret}
      - DATABASE_URL=postgresql://${POSTGRES_USER:-thingport}:${POSTGRES_PASSWORD:-thingport}@db:5432/${POSTGRES_DB:-thingport}?schema=public
      - FLARESOLVERR_URL=${FLARESOLVERR_URL:-http://flaresolverr:8191/v1}
    depends_on: [db, flaresolverr]
    volumes: [thingport_storage:/app/storage]
    networks: [app-net]

  frontend:
    image: ghcr.io/tautvydasderzinskas/thingport-frontend:latest
    restart: unless-stopped
    ports: ["${WEB_PORT:-80}:80"]
    depends_on: [backend]
    networks: [app-net]

volumes:
  thingport_storage:
  thingport_db:
networks:
  app-net:

.env (minimum you actually need to set):

AUTH_SECRET=<a-long-random-string>
[email protected]   # first account to register with this email becomes admin
POSTGRES_PASSWORD=<a-real-password>

Then just:

docker compose up -d

Full version (with SMTP, storage template, image pinning, etc.) plus a docs page for setting up the MakerWorld/Thingiverse import credentials is in the repo.

Repo: https://github.com/TautvydasDerzinskas/Thingport

Still actively developed — happy to hear feature requests, bug reports, or just general feedback. If you try it and something's confusing or breaks, please open an issue.


r/SelfHosting • • 23d ago

Papyra is here 🌿 — a self-hosted home for your notes. Every note is just a plain Markdown file.

252 Upvotes

Hi everyone!

I'm so happy (and a little nervous) to finally share something I've been pouring my heart into: Papyra — a self-hosted notes app that feels like Google Keep, but keeps every single note as a plain Markdown file in a folder that belongs to you.

I made it because I wanted one cozy place for my thoughts: the "just jot it down" ease of Keep, the plain files and [[wikilinks]] I love from Obsidian, and a proper web app my family and friends can use from the homelab, each with a private account. It turned out to be something I genuinely use every day, and I hope some of you will enjoy it too.

The nice bits

Your notes are your files. Plain .md with YAML frontmatter. The database and search index are just disposable caches. If you ever stop using Papyra, you simply keep a folder of Markdown files. No lock-in, ever.

Easy to move in. Drag any .md onto the window and it becomes a note. Import from Google Keep (checklists, labels, colours and pins come along), Obsidian vaults, and Day One journals.

Linked thinking. [[wikilinks]] and backlinks, tags, smart collections, to-do lists, full-text search with highlighted matches, and full version history you can scrub back through.

Write together. Live collaboration on shared notes with cursors and presence, plus comments and @ mentions.

Private by design. Locked notes are encrypted on disk, opened with a vault PIN or biometrics. Passkeys, authenticator-app 2FA and OIDC single sign-on, with multiple separate accounts on one server.

A daily journal. One page a day with moods, a streak, a calendar and lockable days.

Homelab-friendly. REST API with API keys, signed webhooks, email through your own SMTP, Git backup (optionally encrypted), zip export. It installs as a PWA and works offline, syncing when you're back.

One container, one volume, for amd64 and arm64: a NAS, a Pi, or a small VPS are all fine.

Try it

curl -O https://raw.githubusercontent.com/lyfie-org/papyra/main/docker-compose.hub.yml
docker compose -f docker-compose.hub.yml up -d

A few honest notes

  • Privacy: no analytics, no crash reports, and no third-party requests (even the fonts are served from your own server). The one thing Papyra does is a daily check for updates, which I also use as a count of active installs — it helps me know the project is being used, and it keeps me motivated. (Edit 12th Nov 2026: I have removed this check from Version 1.2.0 - total privacy here on out. I have received over a 100 stars in the last couple of weeks and that helps keep me motivated on my efforts for this project. Thank you all for such incredible support!)

  • How it's made: Papyra is partly vibe-coded — roughly a year or more of solo work in about half the time. However, I'm a software engineer: I design the architecture, write some of the logic myself, and review and test everything that ships. But it's a young project, so please keep backups like you would with anything new. (Your notes being plain files makes that easy!)

  • What's missing: native mobile and desktop apps are planned but not here yet. The PWA covers phones and tablets for now.

Thank you for reading, truly. If something's missing for your setup, something breaks, or you just want to say hi, I'd love to hear it — issues, ideas and kind words all make my day. And if you try it, I hope it brings a little calm to your notes.


r/SelfHosting • • Nov 16 '25

Why do you selfhost? (what is the motivation and drive?)

Post image
217 Upvotes

r/SelfHosting • • 19d ago

notesd 1.0: self-hosted notes with native mobile apps (now with spaces, multi-user, and an offline web app / PWA )

Post image
216 Upvotes

A while back I posted about notesd, a notes app that isn't trying to be a second brain. The response was much bigger than I expected, so thank you. A lot of what's in this release came from your comments.

It's still the same idea: one server binary with SQLite inside, offline-first Android and iOS apps, tags, full-text search, and locked (end-to-end encrypted) notes.

https://github.com/cassiozen/notesd

What's new:

  • Spaces: keep separate contexts like Work and Personal apart, each with its own notes and tags.

  • Multiple accounts: host a few people (family, friends) on one server. Each account gets its own database.

  • Markdown mirror: --mirror-dir keeps a folder of .md files updated as you write, one folder per space. Point Syncthing, git or your backups at it. Your notes are never locked in.

  • Offline web app: install it as an app, and it keeps a full copy of your notes in the browser, so it opens and saves edits with no connection.

  • Docs site: notesd.app

Feedback welcome and appreciated, as before.


r/SelfHosting • • Feb 21 '26 LOL Bravo

I finally stopped talking about self-hosting and actually did it

Post image
177 Upvotes

I’ve been lurking here for years telling myself “one day.”
This weekend I got bored enough (and annoyed enough at subscription prices) to finally do it.

I picked up a cheap old pi off eBay, wiped it, and spent way too many hours tinkering. By Sunday night I had:

  • Nextcloud running for files and photos

  • Jellyfin for movies/shows

  • Navidrome for music

  • Everything tucked behind a reverse proxy with SSL so it feels “real”

Was it smooth? Absolutely not. I broke things. I locked myself out once. I stared at logs like they personally offended me.

But once it worked? It felt so satisfying.

Streaming my own media with no ads, no weird compression, no “this content isn’t available in your region” — it honestly feels kind of rebellious in the smallest way.

The biggest surprise wasn’t the privacy angle. It was how nice it feels to actually understand the thing you’re using. Like, if something breaks, it’s my problem — but it’s also my system.

I’m still not brave enough to self-host email. I have limits.

Anyway, just wanted to say this sub finally pushed me over the edge.
What’s the one thing you self-hosted that made you go, “Yeah, I’m never going back”?


r/SelfHosting • • Oct 05 '26

Two computers, two auction routers, and a phone as my only internet: the story of my tiny command center

Thumbnail
gallery
175 Upvotes

Chapter 1: Origin

Every hero story starts with something small. Mine started with a 2012 MacBook Air nobody wanted. Tired battery, years on its back. To the world it was junk. To me it was the first recruit.

I installed Debian on it, set it up to keep running with the lid closed, and gave it a name: debiancito ("little Debian" in Spanish). It would be my server. I didn't know exactly what it would serve yet, but I knew I wanted something mine: not rented, not living in someone else's cloud.

Chapter 2: The Mission

Every server needs a reason to exist. Debiancito's is called Pickflow: a web app I built to manage the warehouse and production of a cabinet factory (inventory, pick lists, missing parts). Python, a database, and a lot of late nights.

The magic wasn't writing it; it was watching the loop close. I make a change on my main computer, push it to GitHub, and debiancito notices on its own, pulls the new version and restarts itself. Hands off. The first time it worked, I stared at the screen like I'd just seen a magic trick.

Chapter 3: The Second Hero

My desktop, an HP Omen, was running Fedora. One day I decided it would run Debian too, so both machines would speak the same language. I named it trixie, after the codename of Debian 13.

It didn't come free. The installer couldn't find the internet even with a cable plugged in. On first boot, the Nvidia card left me staring at a black screen and a blinking cursor. And one night, because of my own mistake, I locked myself out of admin rights on my own server and had to rescue it with a USB stick, going in through the system's emergency door. I learned more that night than in weeks of tutorials.

Chapter 4: The Villain

Here's where the antagonist enters the story: I don't have home internet. Right now I can't afford the classic connection everyone installs. My entire network (the server, the workstation, and an app that's live for the world to see) runs on my phone's hotspot.

And the hotspot is a cunning villain. It has its own rules and its own limits, and it counts what the phone browses differently from what the computers connected to it browse. I spent weeks fighting it. Some paths didn't work, others half-worked, and I learned more about networking fighting that limit than in any course.

The latest blow: one morning the phone updated itself. It changed its internal network, revoked an app's permissions, and left debiancito knocking on a door that no longer existed. The server stayed alive by pure luck, hanging on by IPv6.

Chapter 5: Reinforcements

That's when I decided to bring order. I went to a local auction and came back with two allies:

a cheap WiFi router that connects to the hotspot and turns it into a real network;

a TP-Link Omada router, the kind used in offices, which became the brain of everything.

The chain ended up like this: phone → WiFi router → Omada → both computers by cable. Each machine has a fixed address. If the phone gets moody, the ones inside don't even notice.

Then came the audit. Firewalls on both machines (trixie, I found out, had never had one), routers with no open ports, factory passwords changed, and a watchman that bans anyone trying to guess passwords. To get in from outside I use Tailscale: an encrypted tunnel between my devices that works without a public IP. Even the shared clipboard between my phone and PC came back to life through that tunnel.

Chapter 6: The Lair

Every hero needs a base. I built mine with mesh organizers from Dollar Tree: two levels, the WiFi router on top with its antennas free, the Omada below. Next to it, debiancito sits on a cooling pad, its screen showing a green Matrix-style character rain that turns itself off after five minutes to save power.

It's still missing something: a couple of LED fans, for better airflow and, why not, to make it look like the lair it is. They're coming soon. Meanwhile, here are the photos of how it looks today.

It's not a real rack. But it's my rack.

Chapter 7: What's Next

The story doesn't end here:

Security cameras on an isolated network, viewable from outside only through my tunnel, with no vendor cloud.

A small Linux tool born from my fights with the hotspot, which I want to publish for others in the same situation.

And the day real internet reaches my home, turning debiancito into a secure exit point to browse from anywhere.

Tech summary, quick pass:

debiancito: 2012 MacBook Air with Debian 13. Serves Pickflow (Flask + PostgreSQL), with auto-deploy from GitHub.

trixie: HP Omen with Debian 13 and KDE. It's my workstation.

Network: phone hotspot → WiFi router in WISP mode → TP-Link ER605 (Omada) → everything by cable.

Security: UFW on both machines, fail2ban, routers with no open ports, and remote access only through Tailscale.

Budget: almost everything used, from auctions or Dollar Tree.

Now it's your turn. With two computers, two routers and a phone, what would you add? A NAS? Pi-hole? A Proxmox node? A crazy idea I'd never think of? I'll be reading the comments.


r/SelfHosting • • Sep 11 '26

Got an upgrade off fb today

Thumbnail
gallery
175 Upvotes

I was scrolling on fb yesterday and came across this ended up paying 175 for a pretty sweet workstation , and 6 1tb wd ssds, 3 green and 3 blues all passed smart tests. installed proxmox on it and now its going to replace the mini computer ive had running adguard home


r/SelfHosting • • Oct 17 '26

Self-hosted Notes with native mobile apps

Post image
168 Upvotes

I couldn't find a self-hosted "simple" notes app, so I made one: https://github.com/cassiozen/notesd

What I mean by "simple": Not a second-brain, multi-object record system; It's not Notion/Obsidian.

What it is:

  • Single-binary server + offline-first Android and iOS apps;

  • organization via tags;

  • full-text search;

  • encrypted/locked notes.


r/SelfHosting • • Aug 11 '26

Getting started

Thumbnail
gallery
168 Upvotes

Hey! I'm just getting started here. Very new to the community, I have jellyfin hosted on a gaming laptop if that explains how new I am. I was scrolling through Facebook marketplace when I found something pretty cool. Here is what I got for free

I got a HP proliant ml350p gen8 tower

255GB of RAM, (8) empty DIMM Slots

Dual Xeon CPUs (exact models not known yet)

HP Smart Array P420i

512 MB flash-backed write cache

(2) 480 W PSUs

(1) 6 bay 3.5" LFF SAS/SATA drive cage

(9) PCIe expansion slots (3) gen3 x16, (1) Gen3 x8, (4) Gen3 x4, (1)Gen2 x4

(1) Juniper SSG 350M Firewall

(1) Juniper SSG 550M Firewall

(2) Samsung 870 EVO 500GB SATA SSDs

(1) Samsung PM1643a 3.84 TB SAS SSD

Here is what I know I need and have ordered

(2) power Cables

(3) drive carries/adapters

I am not sure where to go from here and would love to hear opinions, recommendations, what I may be missing or forgetting


r/SelfHosting • • Oct 10 '26

Built a 1-click script to turn old Android phones into a headless NAS & Media Server (Jellyfin, FileBrowser, Syncthing) via Termux

Thumbnail
gallery
150 Upvotes

Got tired of old phones sitting in drawers while cloud storage subscriptions keep getting more expensive. Android phones have decent multi-core ARM64 silicon, built-in battery backup (UPS), and low idle power consumption, so I automated the whole self-hosted stack deployment into a single bash routine.

Repo: https://github.com/huzefdev/pocket-cloud

  1. FileBrowser (:8080) - Lightweight web UI to upload, stream, and manage internal phone storage directly like Google Drive.

  2. Syncthing (:8384) - Background continuous folder syncing between PC/phone nodes.

  3. Jellyfin (:8096) - Media streaming server running inside an isolated Ubuntu PRoot environment with FFmpeg codecs configured for hardware playback.

Running Jellyfin natively on Termux hits nasty dependency walls and broken shared library links (especially with curl/ffmpeg codecs). Instead of fighting Android bionic libc quirks for hours, the installer spins up an isolated Ubuntu container inside PRoot for the media engine, while keeping FileBrowser and Syncthing running directly on Termux bare-metal for maximum IO throughput.

Also handles Android wake-locks so the OS scheduler doesn't kill the server daemons 5 minutes after locking the screen.

curl -sL https://raw.githubusercontent.com/huzefdev/pocket-cloud/main/install.sh | bash

The script is non-destructive, checks existing mount points before binding storage, and lets you choose which modules you want to deploy interactively.

Code is completely open-source. Looking for feedback on process management and memory footprint on low-RAM devices


r/SelfHosting • • Sep 23 '26

VirgoOS: a Debian 13 image for self-hosting. Boot the USB, pick a disk, ZFS and Docker are already there.

Post image
131 Upvotes

Virgo (as in the constellation)

A friend of mine has been building a Debian box meant to be a home server from the first boot, and the ISO images are public.

It is called virgoOS. Debian 13 (Trixie), amd64, hybrid ISO. You write it to a USB stick, boot the machine, and choose Install. The installer copies a system that was already built: ZFS, Samba, Docker, and the rest are on the image. Apt does not run during the install, so a machine with no route to the internet still comes up as a server.

What is on it:

  • ZFS, with the module built at image-build time, plus Sanoid (hourly, daily, monthly, and yearly snapshots on the data datasets)

  • Samba

  • Docker

  • NetworkManager, Avahi/mDNS, and a default-drop firewall with fail2ban

  • NUT, so a USB UPS can shut the box down cleanly

  • A small web UI (virgo-api / virgo-ui) on port 3000

  • A floating virtual IP, for a box with a bonded NIC

BIOS and UEFI both boot. Secure Boot has to be off: the ZFS module is built with DKMS and is not signed by a key the firmware trusts. There is a separate ARM64 branch for Raspberry Pi; the ISO on the org page is the amd64 one (RPi/arm64 is also available)

SSH is enabled and the image ships with a default account. Set the password during setup and login with your user, because root is locked. Try the CLI tool virgo -h for management options.

ISO and the rest of the project: https://github.com/univrs-cloud

The image build repo (live-build stages, if you want to see exactly what gets installed): https://github.com/univrs-cloud/virgo

Try it and tell us what you liked. Thanks SelfHosting!


r/SelfHosting • • 29d ago

Self-hosted streaming app: No hard drives, no downloading, just direct streams on a Raspberry Pi

122 Upvotes

Hey guys, I built this and wanted to show it off.
It runs entirely on my Raspberry Pi. No hard drives, no downloading terabytes of movies, nothing like that.
I got tired of watching movies on pirate sites with 50 pop-up ads, fake links, and sketchy players. I figured if these sites can stream the video, why can’t I?
So I started looking into how they work, which led me down a rabbit hole of figuring out where they actually get their videos. Eventually, I ended up reverse-engineering the providers themselves so I could skip all the junk and grab the raw streams directly.
Right now I’ve got 4 providers working, but I’m planning on adding more.
How the setup works:
Raspberry Pi + Stream Relay: The Pi handles everything and runs a media relay that pulls the streams and serves them directly to my devices.
VPN Killswitch: All provider scraping and upstream traffic goes through a VPN on the Pi. If the VPN drops, the killswitch blocks that traffic so it can’t fall back to my home IP.
The iOS App: I built a custom SwiftUI app from scratch for my family. No ads, instant profiles, vertical swipe gestures for volume and brightness, and honestly, I think it’s a better experience than Netflix.
Recommendations: I also built my own recommendation engine that adjusts to each profile’s watch history and preferences. I wanted something that actually recommends movies and shows you’d be interested in instead of the random stuff most streaming sites throw at you.
What I’m still working on:
It’s definitely still a work in progress. Initial loading can be a little slow because probing the providers and grabbing the stream sometimes takes a few seconds. I’m still working on speeding that up.
The next thing I want to add is automatic failover. Basically, if a provider goes down or starts throttling in the middle of a movie, the relay would switch to another provider without interrupting playback.
What do you guys think? Any suggestions on providers or how you’d handle redundancy?


r/SelfHosting • • Aug 17 '26

I ditched Azure for a self-hosted VPS and cut my hosting bill by 80%

Post image
120 Upvotes

In the past 1 year it has always hurt me to see a 56 EUR hosting bill each month. Doing the math it accumulates to 672 EUR per year!

I don't know why I didn’t do the math a bit earlier though. It could have saved me those 672 EUR, but hey I never liked math anyway.

So I decided to move everything to a self-hosted VPS.

A VPS is basically a virtual server that you rent from a hosting provider. You get your own CPU, RAM, storage and operating system, but instead of paying for a managed platform like Azure App Service, you are responsible for running and managing the server yourself.

On top of the VPS I run Docker, with my frontend, backend, Dokploy, and Traefik each running in their own containers.

Traefik acts as the reverse proxy, receiving incoming traffic and routing each request to the correct container based on the domain. It also handles HTTPS certificates.

Dokploy is a self-hosted PaaS that gives me the Azure App Service experience on my own machines: push code, get a deployment. It connects to my GitHub repositories and manages deployments, domains, environment variables, logs, databases, and Docker services, all from a single dashboard.

So instead of paying Azure to manage the infrastructure for me, I rent the server directly and run the platform on top of it myself.

The result is around 80% lower hosting costs and much more control over how everything is deployed.


r/SelfHosting • • Oct 22 '25

Tried self-hosting AppFlowy — turns out it’s not really open-source or worth the hassle

112 Upvotes

Tried self-hosting AppFlowy — turns out it’s not really open-source or worth the hassle

Just wanted to give others a heads-up if you’re considering self-hosting AppFlowy as an open-source Notion replacement.

I spent quite a bit of time setting it up — Docker, configs, database, reverse proxy, the whole deal — only to find out there’s a hard member limit unless you “upgrade your license.” Even though it’s running entirely on my own hardware, it still enforces that restriction.

When I asked about it on their Discord, the first message I got from the team was:

My question:

Hey guys! I am new here and would really love some direction. I have an instance of appflowy self-hosted. There has been some hiccups along the way, but finally got it up and running. Currently the issue I am facing is that when I try to add new users, I have the error that the usage limit has bee reached. A reddit post (https://www.reddit.com/r/AppFlowy/comments/1kec021/if_i_selfhost_i_still_have_user_limits/) told to try using the desktop app instead of the web console, since it's a bug. I tried adding members via the console and the desktop application, but to no avail. I only have two users and it says that I cannot have more than that. One of the user is created on the self hosted instance and the other is manually created. Any help or direction will be very greatly appreciated!

Their response

The dialog says please upgrade your license to add more members. Is the message not clear?

That tone pretty much summed it up. They later clarified that “we have member restrictions for the free plan.”

To be fair, if you’re only planning to use it for yourself or one other person, it’s fine. But beyond two users, you’re stuck behind a paywall. And honestly, the whole point of using a project management or collaboration tool is to have multiple people working together.

It’s also worth mentioning that the “AI support” features aren’t available — even if you bring your own key — because that’s behind the paid plan too. They also don’t support local AI models you might already be hosting, which kind of defeats the self-hosting idea altogether.

In hindsight, I should have looked more closely at the pricing details. But based on older Reddit posts, it seems like this used to be unlimited and they quietly added this restriction around 5–6 months ago. So a lot of people (myself included) went in expecting a truly open-source experience.

AppFlowy looks the part, but it behaves more like a closed, freemium SaaS product. Between the hidden limits, missing AI flexibility, and dismissive support tone, it’s just not worth the setup time.

Out of curiosity — what are you all using instead? Ideally something that supports Kanban, team collaboration, and can be self-hosted without these pseudo open-source restrictions.

Sorry for the rant. Just wanted to have a post available online that clearly states the caveat for self-hosting AppFlowy, and no one else spends too much time setting it up, without knowing what they are getting their selves into.

TL;DR:
Spent hours self-hosting AppFlowy thinking it was an open-source Notion alternative. Turns out it’s limited to 2 users unless you “upgrade your license.” Even with your own server, you still hit a paywall. AI features are also locked behind a paid plan (even with your own key) and no support for local models. Feels more like freemium SaaS than open source.

EDIT: Added missing conversation


r/SelfHosting • • Mar 06 '26

Best VPS providers and hosting recommendations?

111 Upvotes

I'm planning to set up a website that might scale, and also need to run openclaw on the same server. Looking for VPS hosting providers with decent performance, reliable uptime, and good customer support. What do you recommend?


r/SelfHosting • • 8d ago

[ANNOUNCEMENT]: New Rules and AI

106 Upvotes

Based on the results of the poll and the feedback we've received from the community, we've made some changes to the rules. The previous AI rule has now been specified in more detail, renamed as Rule #2 and will be enforced. We also want to emphasize that Rule #1 will be enforced.

Rule #1 Be kind and respectful: This is a great community, don't ruin that. Any offensive or disrespectful comments will be dealt with and possible bans will be handed out.

Rule #2: No AI-generated posts: Posts must be human/hand-written. If you want people to actually read your post, then take the time to do a write up yourself. Supplementing your post by using AI for translation and listing specs is allowed only by posting it as a comment on your own post. Projects using AI-assisted development is allowed, but you must be transparent about how it was used.

We believe that requiring posts to be human/hand-written and enforcing this will also discourage people to post projects that are entirely vibecoded. We will try out these new rules for some time and re-evaluate. If there is enough activity and the community gains some momentum based on the new rules, then we can discuss adding restrictions to vibecoded projects.

Thank you for voting and being part of this community. Let's try to make it even better!


r/SelfHosting • • 24d ago

Self Hosted Closet Web App

104 Upvotes

Made this for my wife and figured I'd share it with everyone.

Github Repo


r/SelfHosting • • 4d ago

I got tired of ssh-ing into my boxes, so I made this

103 Upvotes

I made a TUI tool to put the whole homelab on one screen, you may find it useful to troubleshoot resource issues or explore logs of containers and systemd services. Nothing to install on the machines, it's all over ssh.

Demo: https://asciinema.org/a/VWnselSOsXKvLzJO

Code: https://github.com/cmdoret/sshwarm


r/SelfHosting • • Oct 22 '26

A self-hosted ManyChat alternative for Telegram, WhatsApp, Instagram, SMS and email.

91 Upvotes

Hi all. I've been building BrightBean Chat, an open-source, self-hosted alternative to ManyChat. It has chat automation for Telegram, Instagram, Messenger, WhatsApp, SMS and email.

GitHub: https://github.com/brightbeanxyz/brightbean-chat

To be upfront: This is a business tool. If you don't run a bot or message customers for a small business or side project, you don't need it.

What people use it for

  • A Telegram bot that answers FAQs and hands off to a human when needed

  • Instagram comment-to-DM: Someone comments with a keyword, they receive a DM

  • Drip sequences and broadcasts to contacts who opted in

  • A shared inbox so several people can answer conversations

  • Wiring it into n8n or anything else through a REST API and signed webhooks

The stack

  • PostgreSQL, which is also the job queue, so there's no Redis

  • a one-shot migration container

  • the Gunicorn web process

  • a background worker

  • Caddy with automatic HTTPS

Only Caddy is exposed. Postgres stays closed to the internet, credentials are encrypted at rest, and production settings refuse to start with placeholder secrets.

Running it

git clone https://github.com/brightbeanxyz/brightbean-chat.git
cd brightbean-chat
cp deploy/env.prod.example .env
make prod-secrets
# fill in APP_DOMAIN, ACME_EMAIL, SECRET_KEY, ENCRYPTION_KEY_SALT, POSTGRES_PASSWORD
docker compose -f docker-compose.prod.yml up -d

If you just want to look around, plain docker compose up serves it at localhost:8000 with no .env needed.

Things that will bite you

  • Instagram, Messenger and WhatsApp deliver messages via webhooks, so you need a public HTTPS URL plus your own Meta developer app. That's the most annoying part of setup. The README walks through every field Meta asks for.

  • Telegram, SMS (your own Twilio) and email (your own SMTP, Resend or SES).

  • If web and worker run on separate hosts, uploaded media needs S3-compatible storage. MinIO works.

License

AGPL-3.0.


r/SelfHosting • • 17d ago

Local / CalDAV Web and Android Calendar

79 Upvotes

I've just open-sourced calendar app that I've created as an alternative to Google and Proton calendars, for my own purposes and I'm using personally: Calendar. It's a calendar and task manager for the browser and Android that keeps everything on your device or on your own CalDAV server (Nextcloud, Radicale, Baïkal, Fastmail, iCloud, mailbox.org, Posteo, Synology and others). No account, no cloud, no analytics.

What it does

  • Day, week, month, year and agenda views, plus a custom view of 2 to 7 days. Drag to create, move and resize events

  • Recurring events with "this event / this and future / all events" edits, Yes/Maybe/No replies to invitations, and a Join button for Zoom, Teams, Jitsi and Webex links

  • Tasks with subtasks, priorities, due dates and reminders, and a quick add that understands "Call Anna tomorrow"

  • Several CalDAV accounts side by side with incremental sync (RFC 6578), and a "Move my data" wizard between the device and a server that checks every item before anything is deleted

  • .ics import and export, webcal:// subscriptions, public holidays for 19 countries computed on the device

  • Birthdays and anniversaries that show the years ("Anna's birthday (36)"), and hidden events that keep a title off the screen

  • 5 themes, your own accent colour, 12 bundled fonts, 10 interface languages, keyboard shortcuts and undo for every change

  • Android app with a native CalDAV client and reminders that fire while the app is closed

Self-hosting

Every release is a ready-made Docker image for amd64 and arm64 (a Raspberry Pi works). There's nothing to persist, because the data lives in the browser or on your CalDAV server:

mkdir calendar && cd calendar
curl -fsSLO https://raw.githubusercontent.com/sysoppl/Calendar-CE/main/docker-compose.yml
docker compose up -d

Then open http://localhost:8787.

The container is a small Node server with no dependencies that serves the app and a DAV proxy, because browsers can't reach most CalDAV servers directly (CORS). The proxy stores nothing and contacts no server until you allowlist it (CALENDAR_PROXY_ALLOW). It keeps away from private addresses unless you allow them, rate-limits per client and never logs paths or credentials. The container runs read-only as a non-root user with all capabilities dropped. The README walks through a server setup with HTTPS (Caddy and nginx examples), updating, docker run and running without Docker. There's also an optional Radicale demo in the compose file if you want to try it without a CalDAV server.

Full disclosure: I also run a small fee hosted edition (E2EE Calendar) that adds end-to-end encrypted sync between devices. The community edition is the same app without that cloud, and the local and CalDAV features are the same in both. The "try it" link above is the hosted site used without an account. The hosted edition's client-side encryption code is in the repo, if you want to review it.
AI was used to develop this software. Public Google Play app was released few days ago - there is almost none downloads yet, same for public repository.

Not there yet: no contacts (CardDAV), no CalDAV servers that only accept OAuth (so no Google Calendar), no iOS app, and the Android app has to be built from source for now.

Feedback and bug reports are very welcome.


r/SelfHosting • • 25d ago

Would you dedicate a second PC entirely to background automation?

Post image
74 Upvotes

I've got a small geekom as my second pc, and I'm starting to wonder whether giving it its own dedicated role makes more sense than just using it as another normal computer. Things like cloud AI agents, scheduled tasks, document processing, file organization or even a home server. The upside is my main PC stays completely separate. The downside is now I’m maintaining another PC lol.