I'm the author. Walnut is self-hosted: it runs on my own machine (in the browser or as a Mac app), with everything kept as plain files and SQLite on your own disk, no account, no telemetry.

It started because my work was scattered across too many Claude Code terminal windows. Then I moved my notes and todos in too, so it replaced Notion and my Claude Code terminals.

The part that changed how I work: I run it like a small company, with a CEO agent and a VP for each area. The CEO agent (Main) sits on top, and each area gets a VP (the app calls them leads). I have a work VP, a life VP, a health VP and a side-project VP. I only talk to Main and the VPs. They bring me the few questions that need me, I answer those, and that's how I manage 100+ agents at once, around the clock, with thousands of subagents under them.

What else is in it:

• An Org page with the whole chart and each lead's team, plus a Board page for a team where I tick what I've read and pick between options instead of reading its chat
• Markdown notes the agents can search, my Mac calendar, and tasks
• Coding sessions on the laptop or on any box I can SSH into; the remote ones keep running when the laptop sleeps or SSH drops
• Claude Code, or locally Codex, Gemini, OpenCode or Goose, plus plugins
• Rich mode, where a session answers in HTML. I was surprised when Claude Code started drawing diagrams in front of me.

Limits: Mac and Linux only, the calendar is macOS only, remote boxes run Claude Code only, and the iPhone app is a beta you build yourself.

https://github.com/EvanZhang008/open-walnut (MIT). Do you run your agents as one long chat, or have you split them up somehow?

Hi all!

In January I posted about Vikunja Quick Entry, the little tray app I posted here. The quick entry feature is part of the official Vikunja desktop app now, which was pretty cool to see. I kept working on my own version of a client though, and it turned into Vicu.

Vikunja is a fantastic tool and backend, and it does way more than I need day-to-day. I wanted something closer to a personal todo manager; a task goes in the Inbox, gets a day, and ends up in the Logbook. So Vicu is a lot less powerful than Vikunja, on purpose. When I'm planning something bigger I'd still open the web app.

How I use it:

• Quick entry on a hotkey on my work laptop, so I can note something during a call without leaving it
• The widget and quick settings tile on my phone
• Typing (or talking) "clean the garage saturday 3pm"

It works offline (changes wait and go out when you're back), has voice input, and can link a task to an Obsidian note or a browser tab. There's also an AI assistant for brain dumps, asking about your todo's, and help you organize, but it's off unless you plug in your own provider key or a local model. Nothing else needs it.

It talks to your own Vikunja (2.4+) or Vikunja Cloud, with an API token, password + TOTP, or OIDC. Mine runs behind Authentik. There's no Vicu account or server, and no analytics.

I've been working on it since January, about a thousand commits across the desktop and mobile apps. Linux support and a pile of fixes and features came from people opening issues. So a big thank you to everyone who's been providing feedback and opening issues! Personal todo can be quite, well personal, and since we all use it different, Vicu has grown beyond features I personally use day-to-day.

https://vicutodo.app
Desktop: https://github.com/rendyhd/Vicu
Android / iOS: https://github.com/rendyhd/Vicu-Mobile

I'm trying to get the Android app on the Play Store (non-technical friends & family ;)), and Google wants 12 testers who stay in a closed test for 14 days. I saw on Github I had over a 100 donwloads, all direct APK. If you're interested in trying it out and want to go the playstore route, that would help a lot: https://github.com/rendyhd/Vicu-Mobile#get-vicu (if you'd rather skip Google, the APK on GitHub is the same build).

AI involvement: I've used multiple models throughout the development from the beginning. Also for the website.

The apps are free, no ads, no nonsense. You need your own Vikunja server, or get it via the fairly priced Vikunja Cloud.

I'm trying to build a personal music system that combines a collection I control with the discovery and convenience of a streaming service. I'm looking for advice from people actually running something similar, including an honest assessment of which parts aren't realistic.

I used Spotify for years, but got tired of albums disappearing, releases with only a few playable tracks, incorrect artwork, and missing editions. I started maintaining my own collection instead. Sometimes an album simply isn't available online, so I rip the CD myself, tag it, and add it to my library.

My current setup:

- Navidrome on a Windows PC.

- Beets for tagging and organizing imports, although my configuration still needs work.

- Feishin on desktop and Navic on my phone.

- An existing TorBox subscription, which I already use successfully with Nuvio for video.

- A Spotify account and library that I haven't migrated yet.

What I'd like the everyday workflow to be:

1. Search for an artist and browse their discography, including albums I don't already own locally.
2. Open an album and play it without manually hunting for a working source or addon each time.
3. Keep discovery listening in a temporary cache, with an explicit way to keep a selected album permanently.
4. Get useful recommendations, artist radio, or similar discovery features, ideally informed by my Spotify library and future listening history.
5. Keep the permanent archive independent of the online sources, so a provider going away doesn't affect music I've already kept.

Three details are particularly important:

- Multiple editions must coexist. I sometimes keep both a CD rip and a vinyl rip of the same album. I don't want an automation tool treating them as duplicates or replacing one with a supposedly better copy.

- Lossless matters. I'd prefer actual FLAC playback for discovery too, rather than YouTube audio being the only instant-play option.

- Personalized recommendations are essential. One of the biggest things I'm missing after leaving Spotify is discovering music without already knowing what to search for. I want recommendations for artists, albums, and tracks **outside my existing library**, based on my taste and listening history—not just shuffled playlists or radio limited to files I already own. Ideally, I could listen to a recommendation immediately through the temporary cache and keep the album if I like it. My Spotify library hasn't been migrated yet, so suggestions for using that data to bootstrap recommendations would also help.

I've looked at both V1ck3s/octo-fiesta and winters27/octo. Octo-Fiesta's older account-free backends appear to be unavailable or limited now. Winters27/Octo separates instant YouTube playback from acquiring lossless files, and has a prefetch feature, which sounds closer to the cache workflow I'm after. I haven't established a working end-to-end setup that meets my requirements.

I've also tried Eclipse Music and BitChord, but ran into unreliable addons, missing albums on artist pages, and incorrect artwork. Simply changing the player doesn't seem to solve the underlying catalog/source problem.

Constraints: native Windows, no Docker/WSL/VM, and I don't want to buy another music subscription or register additional accounts to access music. I already have TorBox, so using it is fine. I realize these constraints may rule out otherwise good solutions—please say so if that's the case.

Does anyone actually run a setup close to this? In particular:

- Is there a practical music discovery/streaming frontend using TorBox that can coexist with a Navidrome archive?

- Can lossless prefetching provide the experience I'm describing, or should I expect to request/download an album before listening?

- What handles recommendations and an external catalog without taking over or rewriting the permanent collection?

- Has anyone connected a recommendation engine to a workflow where recommended music can actually be found and played, rather than only generating a list of titles? What works well for this, and can it use an existing Spotify library as a starting point?

- If no single application does this, what combination has worked reliably for you, and what compromises does it require?

I'm open to changing tools. I'd especially appreciate real-world setups and their limitations, rather than a list of projects that each cover only one part of the workflow.

I'm away from home, something needs doing on a box, and the phone is useless. That's the problem I was solving.

Now every machine runs a small agent that dials out, and my AI chat talks to all of them through one MCP endpoint. "Why is the server slow?", "clean the disk on the NAS box", "ship this fix": it asks which machine, and runs there. The agent package is open source (MIT). The relay is hosted, and the agent only ever connects outward.

Recording of a real run (site update from my phone, 13 min): https://localcmd.app

I know this crowd's first question will be "why should I trust the relay," so ask it. I'd rather hear it now than after launch.

Last time I shared CaptureFlow here, a bunch of you (rightly) pointed out that "self-hostable on your own Cloudflare account" isn't really self-hosting. Fair enough. That stuck with me, so I spent the last few weeks making it run on plain Docker.

So now it's just:

git clone https://github.com/sardorml/captureflow.git
cd captureflow
cp .env.example .env
docker compose up -d

Set your URL in .env and you're done. No Cloudflare, no S3, no Postgres. Everything ends up in one data/ folder (a SQLite file plus your recordings as normal files), so backing it up is just copying a folder.

If you've never seen it: it's a screen recorder where you get a shareable link right after recording, since it uploads while you're still talking. People can comment and react on the video, and you can see who watched it. There's also screenshots with annotations, and team workspaces.

A few things I added because I figured this crowd would want them:

• Transcripts work with any OpenAI-compatible Whisper server, and there's a compose profile that spins one up locally
• Email is optional. No SMTP? Invite links just show up in the logs
• Self-hosted instances have no billing, no limits and no analytics, and they never auto-delete old recordings

For recording you can use the Chrome extension or the Mac app. Windows is what I'm working on next. Right now you'll need to build the extension with your own server URL (one env var); a "pick your server" setting is on the list.

Heads up: browsers only let you capture the screen over HTTPS or localhost, so you'll want it behind Caddy/Traefik/nginx if you're accessing it from another machine.

It's AGPL and nothing is held back from the open source version.

Repo: https://github.com/sardorml/captureflow

Docker guide: https://docs.captureflow.dev/self-hosting/docker

Would genuinely love to hear what breaks on your setup. First Docker release, so I'm sure something will.

These changes haven’t been released yet and aren’t included in the currently available download. I’m aiming to release the update as early as this week, but the date isn’t confirmed.

When I last shared BookManager here, a user pointed out that saving metadata could remove existing ScanInformation. I’ve since fixed that issue and improved how the app reads and edits existing XML metadata. Thanks for bringing it to my attention.

BookManager is an open-source desktop app for Windows and macOS for organizing comic and ebook files and editing their metadata. It can also help prepare files for a Kavita or Komga library.

The metadata changes planned for this update are:

• Improved preservation of existing scan information, page information, and additional XML elements when editing ComicInfo.xml.
• Improved reading of ComicBook.xml and CoMet.xml and conversion of their metadata to ComicInfo.xml, for workflows that also involve ComicRack or ComicTagger.
• Incorporated the fields and formatting from the ComicInfo.xml 2.1 draft.

I’ve also added a dashboard and author pages. If you’ve collected plenty of books but sometimes spend more time choosing than reading, the dashboard includes daily recommendations to help you pick something. You can also look back through your reading history and browse books by author.

If you’ve encountered metadata being lost or displayed differently when using ComicRack, ComicTagger, Kavita, or Komga together, please let me know which applications and fields were involved. I’d like to use those examples to check compatibility before the release.

• Source code
• Project website and current release

Hi r/selfhosted, I'm Dragos, part of the small team behind grovs.

When Firebase Dynamic Links shut down, a lot of mobile apps were pushed to paid SaaS like Branch to keep their links working, which also means a third party sees every click and install. grovs is the self-hosted version of that.

What it does

- Deep links that open the right screen in your app, including after an install (deferred deep linking), on your own domain

- Attribution: which link, campaign or QR code brought each install or open

- Analytics dashboards: opens, installs, retention, campaigns

- Migration: old Branch/AppsFlyer links keep working, the first click resolves them and creates a native link

- SDKs for iOS, Android, Flutter, React Native, Unity and web

Running it

One Docker Compose stack: Rails API, React dashboard, Postgres, Redis, optional ClickHouse, workers and a reverse proxy with automatic TLS, from published images. Setup generates secrets and an admin login. There are guides for a plain Linux box, Coolify, Dokploy, CapRover, Railway, Render, Hetzner, AWS, GCP and Azure.

Licensing, to be upfront

The core and all SDKs are MIT: links, attribution, analytics, custom domains and migration. Push, in-app messages, journeys and segments are in an ee/ folder under a commercial licence. The Community image doesn't include them, and you don't need them for links and analytics.

Repo: github.com/grovs-io/backend

I'd really like feedback on the install: what broke, what's missing, and what you'd need before running it for a real app.

I'm looking for a self-hosted alternative to startme, and I'm struggling to find something that offers the same kind of organization and visual structure.

I've tried Linkwarden, Karakeep, LinkAce and ArchiveBox. Linkwarden is currently my favorite, and others, but none of them quite offer what I'm looking for. Most of all, I hate the way it looks and how it feels to use.

What I want is something that lets me build my own structure:

• Custom bookmark groups with headings: I want to divide a page into clearly defined sections and give each group its own heading. For example, I might have separate groups for self-hosted apps, networking, Linux, documentation, useful tools, etc.
• Multiple groups side by side: Being able to arrange groups in columns is a huge part of what makes startme work for me. I can see several categories at once instead of having to navigate through folders or scroll through one long list.
• Complete freedom over the layout: I want to decide where groups go and how they're arranged on a page. I don't want to be limited to choosing between a tile view and a list view for an entire collection. I want to create a structured overview that makes sense to me.
• Multiple customizable pages: Separate pages for different topics, projects or areas of interest, each with its own layout and groups.
• Good bookmark management: Search, tags, descriptions, icons and the ability to save and organize lots of links are still important. Ideally, the solution would combine this with Start.me's flexible visual organization.

Widgets such as weather, calendars, RSS feeds and notes would be nice to have, but they're definitely not a priority.

Here some example sites:
Cyber Threat Intelligence - Start.me
AI - The Ultimate Page - Start.me
Tools - Start.me

Thanks a lot!

Hey all, I picked up a DXP2800 a few weeks ago and I'm about two weeks into UGOS before I commit and move my real data over. Would love some opinions from people who've lived with it longer.

Setup is simple: stock N100 with 8 GB RAM, two 4 TB IronWolfs in RAID 1 on Btrfs, and a Lexar NM620 512 GB NVMe sitting there unused. I got the SSD so I could try ZimaOS on it without touching UGOS, and boot back if I don't like it.

What I want out of it isn't crazy. File storage and PC backups for me and my partner, automatic photo backup from our two iPhones (around 400 GB and growing), a network-wide ad blocker, and a music library where I can dump my MP3s in a folder and stream them to my phone. Most of that will run in Docker, with Tailscale for remote access so I don't have to open ports. Backups will be a nightly USB drive plus something offsite.

Honestly UGOS has been fine so far. RAID, snapshots, users and photo backup all work without much drama. I just want some feedback before picking the OS I'll live with long term, since switching later means wiping the drives and starting over (I think?).

What's holding me back on ZimaOS is that I'm not sure how open source it really is, and it's another Chinese company on top of UGREEN. Not trying to start a political thread, I just don't love the idea of my whole photo library and network DNS running on software I can't really look into. Is that a fair worry or am I overthinking it? And if it's fair, does switching even make sense when UGOS is in the same boat?

Which makes me wonder if I should look at TrueNAS or Unraid instead. I'm comfortable following guides but new to NAS and Docker, so would any of those fit better for this? Also curious how Docker and Tailscale have been on this box for people, whatever OS you ended up on.

Cheers!

If you self-host local AI tools, you probably know how annoying it is to set up a memory layer. Most modern setups expect you to spin up multiple heavy Docker containers running dedicated vector databases that hog gigabytes of RAM just to store a couple of text documents. I spent the last six months building Hillock to replace that entire stack with a single, ultra-fast SQLite database and pure CPU math, and v1.0.0 stable is officially out today.

Hillock is designed to be completely self-contained. It stores all facts, relational links, and associative synaptic weights directly in a standard SQLite file using Write-Ahead Logging for fast concurrent reads and writes. To prevent the AI from making things up, it compresses query contexts into hyperdimensional bit vectors and runs hardware-level popcount checks on your CPU. The entire memory engine stays under 1.2GB VRAM and can run purely on laptop CPUs with zero GPU required.

It exposes a standard OpenAI compatible API at port 8000, which means you can plug it directly into your existing self-hosted interfaces like AnythingLLM or custom chat bots without changing your code. It has built-in streaming, local entity inspection commands, and zero external telemetry or cloud tracking.

I have put hundreds of hours of work into this over the past half year to make it stable, reliable, and completely offline. If you want a lightweight memory engine that does not choke your home server, check it out on GitHub. Dropping a star on the repo helps a ton to get this noticed: https://github.com/roandejager/Hillock

My current setup... and I'm getting so much satisfaction out of it!

Everything is running smoothly, 3-2-1 backups are in place and working, remote monitoring is set up, and even my wife is happy with KitchenOwl for recipes and Watcharr! :)

It's honestly amazing how much fun self-hosting can be.

I’m Meg, a Software Engineer at Thermify. We’re building an unconventional cloud platform at Thermify. Instead of a conventional data centre, we're distributing the servers into UK homes, and recovering their waste heat for low-cost, low-carbon heating & hot water.

We're looking for a handful of DevOps engineers willing to put it to the test this winter.

The challenge: bring an ARM64 docker workload, deploy it, benchmark it, and tell us where it succeeds or fails.

Best fits:

• Batch processing
• CI/CD runners
• Data pipelines
• Short-lived containerised jobs
• Small-model CPU inference.

The Parameters:

• CPU only workloads
• Non-sensitive data
• No hard real-time requirements
• Non-production critical workloads

We're an early-stage platform, not a mature hyper-scale replacement (yet!).

What you get:

• Free compute.
• Direct access to our engineering team.
• Input into how the platform develops.

No endorsements required. No expectation of positive reviews. Just honest technical feedback and, if you're comfortable, sharing what you discover.

Interested? Comment with your proposed workload or drop me a message.

Hey selfhosted community,

I run CLI cursor agent on my debian mac mini.

I tend to interface with it via VPN SSH with Terminus from my Android phone. The chat experience is a pain, the CLI doesn't provide convenient text selection, autocorrect and such in that context. I am wondering if you guys know of some other method I should consider to interface with cursor (or feel free to let me know of another provider) in a more Claude / chatgpt way I guess ? Can be web-based only or app.

From the laptop I use cursor IDE and remote connect to the server.

Thanks for your insights !

Has anyone ever sort of self hosted a couple of devices lets say a thousand plus with headscale as control plane and tailscale as Networking engine?

Hey r/selfhosted,

About four years ago I posted Sablier v1.1.0 on r/Traefik. If you've never heard of it: Sablier starts your apps when someone actually visits them, and stops them after a while without traffic. While an app boots, your reverse proxy shows a waiting page or just holds the request until it's ready. It's made for the services you open twice a month but keep running 24/7.

I've just released v1.19.0, and a lot has changed since that post, so here's a catch-up.

It's not just Docker anymore

• Providers: Docker, Docker Swarm, Kubernetes, Podman, Proxmox LXC, systemd, Nomad and AWS ECS
• Reverse proxies: plugins for Traefik and Caddy, plus Nginx, Envoy, Istio and Apache APISIX through a proxy-wasm plugin

Scale instead of stop
Cold starts are the main complaint about this kind of tool. With scale mode, Sablier doesn't have to stop an idle app. It can keep it running with throttled CPU, memory or disk I/O, and give it its full resources back when someone shows up.

Webhooks and observability

• Webhooks when an instance starts or stops, so you can plug Sablier into your notifications or monitoring
• A Prometheus /metrics endpoint
• OpenTelemetry tracing

A few smaller ones I like

• Running hours: keep something up during set hours, whatever the traffic
• Anti-affinity: make an app back off while another group is in use, e.g. free the GPU from Nextcloud while your streaming stack is running
• Groups, optional instances, and themes for the waiting page

The maintainer side

This part is more personal. For most of its life, Sablier was mostly me, on evenings and weekends, because I enjoyed it. Outside contributions were rare. After a while that gets heavy: issues pile up, every feature takes weeks, and the project lives in the back of your head as a to-do list.

This year changed that, and AI is a big part of why. I know it's a touchy subject here, so I'd rather say it upfront. On my side, I can turn an idea into a working feature in days instead of months. It comes with tests and docs, and I still review every line. Contributions came back too: 13 people besides me have contributed so far this year, about twice as many as in any previous year. I was honestly expecting a wave of AI slop. I didn't get any, just really nice PRs.

The result is that I don't carry the project around in my head anymore, and maintaining it is fun again.

If you already use Sablier, I'd really like to hear from you

I know very little about who actually runs Sablier. I see the stars, the issues and the occasional PR, but most people who use it never say anything. That's fine, but it means I'm guessing a lot when I decide what to work on next.

So if you use it, I'd love a comment, even a short one:

• Is it for your homelab, for work, or both?
• What do you put behind it, and why? Saving RAM or power, a small VPS, GPU sharing, or something else?
• Is it really useful to you day to day, or more of a nice-to-have?
• What's annoying, missing, or confusing?

Negative feedback is just as welcome. If you tried it and dropped it, I want to know why too.

• GitHub: https://github.com/sablierapp/sablier
• Docs: https://sablierapp.dev

I am self hosting a number of services, like Book Orbit for example. These services are proxied by Nginx Proxy Manager and are all HTTPS enabled. I use the auth systems provided by each individual service. I have my own domain and I have a wildcard domain pointing to my public IP. NPM will only proxy matching addresses and those addresses aren't published anywhere since I have a wildcard subdomain DNS entry, making me think this is some sort of security through obscurity. Is that true? i.e. Nobody knows my subdomain addresses to access my services with.

What other things can I do to improve security?

Hi folks, I maintain repowise, an open source tool that indexes a repo on your own machine and tells you which files are most likely to need the next bug fix, and what to do about them. Nothing leaves your box. Indexing and scoring make zero LLM calls, and the same commit gives the same score on every run, so you can put it in CI and trust it.

After indexing, it checks itself against your own git history and prints the result. Something like "16 of the 20 lowest-health files had a bug fix in the last 6 months, 3.3x the 24% baseline."

What you get from one index, served from localhost -

- Every file scored 1-10 by 53 deterministic detectors (complexity, god classes, clones, untested hotspots, etc), split into defect risk, maintainability and performance.

- Multi repo workspaces where it matches API contracts between your repos, so changing an endpoint shows which calls in other repos break

- Dead code detection with confidence tiers

- A dashboard with an architecture graph, a health bubble map of every file, and a generated wiki

- An MCP server, so Claude Code, Cursor or a local agent reads the same index instead of grepping blind

28 languages parsed to an AST, including the old ones (COBOL, Delphi, C).

Running it - pip install repowise, or Docker with the compose file in docker/. The only part that wants an LLM is the optional wiki prose, and Ollama with a local embedding model keeps that fully offline too.

AGPL-3.0, about 7.9k stars, and 200+ contributors so far.

Feedback and contributions welcome!

Repo: https://github.com/repowise-dev/repowise

Demo: https://repowise.dev/repo/repowise-dev/repowise/overview

Hi everyone! So I’m really new to self-hosting and unsure of where to start equipment-wise. I’ve done a little bit of research and have an idea of what I need to run for what I’m wanting. Mainly I need enough storage for music, movies/shows, and to store pictures and important files securely.
While I am not tech illiterate, the most “coding” experience I have is cheating in the Sims. So beginner-friendly is preferable.

I have been getting familiar with Jellyfin and plan to use that for the entertainment. I also use the Proton suite for file storage, email, passwords, etc
I do like the interface Proton offers, but I’m open to other suggestions, as I’m trying to reduce the subscriptions I’m paying for. For storage I’m thinking of having a couple different places to store my files as backups, hence the need for local storage.

I do play videogames and have a PC that I would like to repurpose to get every ounce of usage I possibly can when I do upgrade. I have a good size mid tower that can fit e-ATX motherboard and a lot of bays for storage (the MSI Seikira specifically) Figured the specs would be more than enough since I use it for gaming currently. I also stream as well, so I’m not sure if the load on my internet would be too much. I plan on using Jellyfin, Pi-hole, and docker, as those are repeatedly recommended online.

What would the best set up for my situation? Would I have to wipe windows completely to convert it to a home lab? It seems like self-hosting is pretty code-heavy too, and I’m willing to learn, however I would like an interface to keep track of everything. I’m not too sure of the budget because it seems like the budget can vary drastically depending on what you get. I’m thinking 500$ and under to start.

Thanks in advance for reading and for any advice you can offer!

With the rise of AI assisted threats, I sure would like a single spot that I can see if everything I run appears to be secure.

"But brainzhurtin, just don't expose things on your WAN!". Nope. Threats come from inside too.

Something that could keep track of releases, news articles, common sources for this type of thing. I just have too much to keep track of, and having a tool like this would be amazing at least letting me know when and where I need to spend some time patching holes. It doesn't have to even actually do the fixing. Just alert me. Or maybe that's a feature later if it doesn't exist already.

I'm just thinking with my linode servers, 40 or so self hosted apps, tvs that need to get network blocked (screw you Samsung), routers that I didn't occur right away have PHP (OPNsense), etc, etc etc. It's a lot.

Does something like that exist?

Doing "Meta Post" because, well, there's "solved" but no "question" flair, oddly enough....

I really like Ninox. In fact, one of the main reasons I started using it was the ability to keep my databases locally and sync them through iCloud, without depending on a cloud subscription.

I've invested a tremendous amount of time and effort building my databases, and I would hate to lose that flexibility. If Ninox eventually removes the option to use local databases without a subscription, unfortunately, I'll have to move on.

As UKenGB mentioned, what I really need is a future-proof solution where I have full control over my own data.

I've actually started exploring the idea of building my own Ninox-like application. With AI tools such as ChatGPT and Codex, development has become much faster than it used to be. It also makes me wonder whether other Ninox users facing the same concerns would be interested in collaborating on an open-source alternative.

I've been burned by software subscriptions before. I've purchased applications, invested years of work into them, and then watched their developers switch to subscription models or introduce restrictions that weren't there originally.

To be clear, I'm not accusing the Ninox team of doing this. I appreciate the work they've put into the software, and I genuinely hope Ninox continues to succeed.

However, announcing Ninox 4 without clearly explaining the future of standalone Mac databases, local storage, and iCloud synchronization leaves users like me understandably concerned.

I really hope Ninox will clarify its plans, because I'd much rather continue using a product I already enjoy than have to replace it.

Good day r/selfhosted,

Wednesday is an exception day for sharing projects, so I wanted to introduce Lagrange Reader, an Android companion app for BookOrbit, Komga, and now Kavita, with more integrations planned.

The project started from a simple need: I wanted to read my books offline on Android and have my reading progress sync back to my self-hosted library when I reconnected.

I’ve been a heavy reader for as long as I can remember, but I’ve never fully satisfied with how most Android apps handle offline reading from self-hosted book servers. I’m also not really comfortable using OPDS as the main way to access my library.

Lagrange is my attempt to make reading from a self-hosted library on Android feel more comfortable and natural. Among the sea of Android readers, I’m trying to build it as a convenient way to connect to your library and read offline whenever you need to.

Some of the features I’m most happy with:

• Download books for reliable offline reading
• Sync reading progress back to your server after reconnecting
• Read EPUBs, PDFs, and comics
• Listen to supported audiobooks
• Browse libraries, series, authors, and search
• Customize the reading experience with themes, text size, margins, and orientation controls
• Continue reading even when your connection is unreliable

A heads-up about how it is made: my day job is as a data engineer, and I also work as a freelance backend engineer on various private projects. I do not have any real Android development experience. I designed the system and framework myself, but much of the implementation work has been AI-assisted.

I completely understand if that makes some of you close this post immediately. I wanted to be transparent about it. I research, test, review, and maintain the project myself, and contributions and feedback are more than welcome.

The project very recently reached 100 stars, and we already have multiple external contributors and translators helping with the project. That has been a really encouraging milestone.

In a way, I’m trying to give something back to the self-hosting community that has helped and inspired me for years. Lagrange is completely free and licensed under GPLv3, so you can do almost anything you want with it. There is also no telemetry whatsoever.

I would be honored if some of you would give it a try and let me know what you think.

GitHub: https://github.com/van-geaux/lagrange-reader

Thank you!

Hi All,
Looking to begin my selfhosting journey as a beginner with no idea where to start. Main things I want to accomplish:
- Plex/Jellyfin for streaming, both locally to Apple TV and remotely on phones and other Apple TVs.
- Immich for photos
- Adblocking on home network

Am I best to look at a Raspbery Pi or thin client or mini PC? How much power do I actually need?

Yesterday we cut the v1.23.0 release for Spinifex, the open source, self-hosted AWS-compatible cloud. Whilst a good portion of our resources are being devoted to opportunities with partners such as OCI, we still managed to get a significant update out:

Route53:

• Host public DNS zones on your cluster: point your domain at the cluster's name servers and it goes live.
• A new console walks you through adding a domain and editing A, AAAA, CNAME, MX, TXT, SRV and CAA records.
• Existing Terraform or AWS CLI Route 53 code works against it.

Security:

• Patched guest kernels in the system images and the load balancer VM, and the load balancer moves off end-of-life Alpine 3.20 to 3.24.
• Hardening of the instance metadata service (IMDS): it limits connections, enforces timeouts and honours HttpPutResponseHopLimit.
• Signing out ends the console session in every open tab.

Operator quality-of-life:

• spx admin storage status (S3 metadata node health), spx admin dns, and spx admin init --external-dns.
• The metadata service stays reachable after an Open vSwitch restart.
• Cluster shutdown and account termination now fail safely when a node is silent.

Full release notes on our GitHub: https://github.com/mulgadc/spinifex

Hey r/selfhosted — I put together https://stackswitcher.com, a client-side calculator and config generator that maps 45 commercial SaaS tools to 71 open-source self-hosted replacements (Immich, Plausible, PocketBase, Vaultwarden, n8n, Coolify, SigNoz, Ollama, etc.).

You can select multiple apps in the interactive stack builder, see the combined RAM/vCPU requirements, and export a ready-to-run docker-compose.yml + Caddyfile reverse proxy config right in the browser. Let me know which self-hosted stacks I should add next!

Is there a simpler UI for OPNsense?

Im still fairly new to it and figured out how to do most of what I need but the UI has been so overwhelming for me every time I use it. There's just so many menus.

Sometimes I just want to see usage stats, system stats, maybe assign ip addresses, just basic maintenance stuff. I dont need to edit all my rules all the time.

All the menus and sub menus that constantly move around as you click is starting to get to me. Maybe I'm not using it right but I hate having to dig through a lot of sub menus to do basics tasks that were much easier to access on a store bough router.

I really like how much control I have with OPNsense but the UI has been my biggest gripe so far.