Hey all, happy Wednesday.

Self-hoster, same as most of you. Pi-hole, mattermost, home automations, a Zeek sensor, a dozen Linux boxes and, like everyone (I expect), a /var/log I almost never open unless I'm actively troubleshooting something. But this year’s avalanche of CVEs has been sitting in the back of my head for a while: “if something got in here, would I even know?”

So I went looking for a tool and found a gap instead. There’s good ol' grep on one end and a full SIEM on the other, and not much in between for just a guy and his stuff. I ended up making my own. It’s called sigwood and is at 1.1 as of today.

What it does: point it at logs you already have (Zeek, Pi-hole/dnsmasq, syslog or journald, CloudTrail if you have any cloud stuff) and it runs a handful of statistical detectors over them. Outbound connections with a beacon rhythm, DNS names that look machine-generated, port scans, big transfers out, odd TLS setups, rare syslog lines and reboots, that kind of thing. There’s also a digest command that just profiles a log file so you know what’s in it before you do anything, and a graph command that animates your conn.log as a Sankey flows in a self-contained HTML file (second screenshot).

What it is not: not a SIEM, not an agent, nothing to deploy. No database, no daemon, no account, no network calls. pipx install sigwood, then sigwood /var/log/, and read the output. Your logs stay on your box.

A “finding” is something unusual for your network, not known-bad. There's no signatures or anything like that. On a home network it mostly finds your own stuff first. And that’s sort of the point, you get to see what your network actually talks to and then allowlist the normal stuff. When it finds nothing, the conclusion is that the network is behaving like itself during that window.

The AI part, up front: I wrote the original implementation of the detectors and have used AI to assemble it all into working tool. Claude and Codex both together in a propose/challenge harness I made for them, with me reviewing and steering. This wouldn't exist without AI, I’m not going to pretend otherwise. And some of you will bounce off that, which is entirely fair. But I'm a security professional and a privacy nerd, never been a SWE.

Anyway, the repo is here: https://github.com/helixmap/sigwood

I genuinely want feedback, good or bad. If you run it on your logs and it gets something wrong, I want to hear about it. If the output is confusing, tell me that too. If you think the whole idea is misguided, I’d still rather hear it than not.

First screenshot is an example HTML report (no real network data). Second is a still from the graph animation.

So i have an old thinkcentre m710q sitting in my attic (wifi only gets really hot in the summer) running a couple of my sites. And I wanted a dashboard and instead of just using homepage or glances i ended up making this.

It gives like a win2000 desktop vibe with a biblically accurate angel in the middle. Every eye is one of my services, if something goes down the eye closes and starts crying. The wheels spin faster with cpu load and it goes from white to red when the attic heats up. also lain in the neofetch window because I love it.

Yeah it's kinda cringe and the animations probably eat more of my laptop's cpu than the server uses, but it's beautiful and I like looking at it, backend is just python with no dependencies and it's read only (no docker socket, can't restart anything). keeps 6 months of temps in sqlite so i can finally see how bad the attic gets in august.

Video of it: https://imgur.com/a/rncy4Sv

repo if anyone wants to check it out: github.com/Lozano-Miguel/vault-dashboard

TrailBase is an open and fast(est) Firebase-like backend (BaaS) for building your apps. It provides: type-safe APIs with change subscriptions, auth, multi-DB, a WebAssembly runtime, GeoJSON, admin UI, ...

It's a single self-contained executable, easy to self-host and built with Rust, Wasmtime & SQLite and more recently also Postgres. We provide clients for many environments: JS/TS, Dart/Flutter, Go, Rust, .Net, Kotlin, Swift and Python.

Just release v0.34.6. Since the last time posting here, TrailBase has added:

• Major UI overhauls:
  • Built-in admin OpenAPI browser with user-impersonation.
  • Table explorer: make foreign-keys followable, split data/schema/indexes into separate tabs, and organize tables/views by DB. Add `ON (DELETE|UPDATE)` referential action support to the schema editor.
  • Mobile glow-up and improved screen estate usage with sticky nav and url bar fade.
  • A searchable and interactive ERD page. Overhauled logs and accounts pages.
  • Many more: prompt users on schema changes in the SQL editor, improved dark-mode colors, add S3 settings, ...
• Built-in MCP server.
• Performance: a lot of detail performance optimizations (reduce allocations, ...) resulting in an additional 10+% gains.
• CLI auto-complete.
• Expose custom WASM endpoints in OpenAPI spec.
• "Sign-in with Apple" token exchange for native iOS/MacOS apps.
• Many more features and fixes, e.g.: `trail user export` CLI command for take-out combating lock-in, `trail run --read-only` flag for read replicas., batch execute support for WASM guests, custom scopes for OIDC providers, ...

The project is still young (~2 years) and rapidly evolving, any feedback is genuinely appreciated. If you're feeling adventures and end up checking it out, don't hesitate to reach out 🙏.

Take a look at the live demo, our GitHub or website.

Dashboard:
Glance
https://github.com/glanceapp/glance

System Metrics:
Glances
https://github.com/nicolargo/glances

Weather:
Open-Meteo

Markets:
Yahoo Finance

Font:
Inter by Rasmus Andersson:
https://rsms.me/inter/

Liquid Glass:
Inspired by Apple, written from scratch by Claude using SVG displacement-filter technique

Background Photos by me

ignore Open WebUI being offline, its fine 😅

I've been using Dockge to manage my docker containers on a headless Debian 13 server, and I'd like to switch to Arcane, but I'm a bit of a noob so idk the best way to go about it. I only have seven stacks (backrest, beszel, immich, isponsorblock, npm, nut_webgui, and scrutiny), all of which I created directly in Dockge using the compose feature, so they should all be in /opt/stacks.

Do I just need to run mv /opt/stacks/ /app/data/projects/, install Arcane, and let it autodetect the containers? Do I need to stop all the containers first? Or is there more to it than that?

didn’t realize it was this kind of subreddit, but since I do have something I’ll share. glad to find a place to show off!

utilizes the built in Minecraft server RCON protocol to act on behalf of logged in users. prioritizes parity with vanilla files over everything.

HyCanvas is a browser design tool in the Canva and Genspark space: social graphics, slide decks, video editing, whiteboards, docs, and sheets, with realtime collaboration. Decks can be generated from one sentence, and every generated slide stays fully editable.

The self-hosting side:

• One Go binary with the web app embedded. The only dependency is Postgres; no Redis needed.
• A first-run wizard sets up the database, storage (local disk or any S3 bucket), optional SMTP, and the first account.
• Images for amd64 and arm64. No telemetry; stock photo search uses Openverse and can be turned off.
• AI is optional and uses your own key: OpenAI, Anthropic, Amazon Bedrock, and more, or any OpenAI-compatible endpoint, including one on your own network.

Try it: download the latest build for your platform (Linux, macOS, or Windows) from https://github.com/hyscaler/HyCanvas/releases/latest, then, with a Postgres database you can start:

tar xzf hycanvas_*_linux_amd64.tar.gz
./hycanvas start

It prints a setup link and a one-time secret; the wizard in your browser connects Postgres, picks storage, and creates the first account. Run it as a regular user, not root.

Prefer Docker? The published image is hycanvas/hycanvas (amd64 and arm64), and the Docker guide has a compose file and every environment variable: https://docs.hycanvas.com/operate/docker/

License: Open Source under the AGPL 3.0.

• Self-hosting setup Video: a fresh install in one minute: https://youtu.be/DN7V-4MbCyc
• Code: https://github.com/hyscaler/HyCanvas
• Docs: https://docs.hycanvas.com
• Hosted demo: https://hycanvas.art

Disclosure: I work on HyCanvas.

Happy to answer questions!

Hi r/selfhosted,

It’s been a while since our last post, but since then a lot of new features have been added to Dreeve.

Dreeve is a self-hosted, open-source dashboard for your sports and fitness data

Features and improvements worth mentioning since we lasted posted here:

• Released an API spec: https://docs.dreeve.app/api/
• Added several connectors to automatically sync activities from external platforms: https://github.com/orgs/dreeveapp/repositories
• Added automation rules to streamline gear tracking, commuting flags, and more
• Added support for managing custom segments
• Added explorer tiles to the heatmap
• Multiple new dashboard widgets
• Integrated WindAhead with Dreeve segments

As always, thanks for your feedback and I'm looking forward to more feature requests!
Stay fit, stay healthy 💪

• Example: https://demo.dreeve.app/dashboard
• GitHub: https://github.com/dreeveapp/dreeve
• Docs: https://docs.dreeve.app/#/

I'm an engineer at Mulga, and we build Spinifex, an AGPL-3.0, self-hosted platform that serves the AWS APIs on hardware you own. You point the AWS CLI, an SDK or the hashicorp/aws Terraform provider at your own endpoint and get real resources: aws ec2 run-instances boots a VM on your hardware, and terraform apply builds a VPC on your network. Emulators like Floci and LocalStack mock the APIs for testing, while Spinifex runs the infrastructure your workloads use.

What it's for

• Move compute-heavy AWS workloads such as GPU inference onto your own hardware, without rewriting the code or the Terraform.
• Self-host software that was built for AWS, including on an air-gapped network.
• Learn AWS without a bill: build the VPC, EC2 and RDS stack from a cert course and leave it running for a month.
• Keep one AWS profile for work and another for the rack in the cupboard, with the same commands for both.

Running it

Install a single node onto an existing Ubuntu 26.04 or Debian 13 machine using the binary installer https://docs.mulgadc.com/docs/install or do a fresh install using a bootable USB https://docs.mulgadc.com/docs/install-usb

Repo: https://github.com/mulgadc/spinifex

I remember Fasten started as a project to have all your clinical health data locally as copy of it. I remember them doing well they got a way to import data from American insurers but since I am from EU I was waiting for interoperability with EU come in.... and checked today to find that fasten is now an API company that dose the interoperability presumable for US insurers and AI.

https://www.fastenhealth.com/

Looks like the selfhosted and open source project is dead:

https://github.com/fastenhealth/fasten-onprem repo is archived

https://github.com/fastenhealth/fasten-onprem/issues/629 issue thread confirms that they turned into a service.

I did not find a maintained fork.

I am lookin for selfhosted option for local records copy ideally with FHIR importing option. Is there one? I would like to have a copy of my medical records just in case system gets hacked/bombed/flooded.

P.S. Discussion Werther founder of Fasten intended to used the community to gather knowledge and 'sell out' to make a cloud service or that was just enviable because of (intentionally) high complexity of healthcare record interoperability to make low cost solutions unsustainable dose not really matter and dose not contribute to having independent health records. Please be civil.

I'm the developer of Sidstuga. Sidstuga can connect to a WebDAV folder and browse or play media from Android TV or a phone. It can also record and transfer files to WebDAV.

You can see source details before opening a file, then use subtitle search and timing controls during playback. Jellyfin, Emby and Plex can also sit in the same Hub.

If you use WebDAV for media, do you browse by folder or prefer a library view?

r/sidstuga

I host websites and email for about 30 small businesses on two Hetzner servers. Next month I'm moving all their DNS from the registrar's nameservers to Cloudflare, mostly to get proper API access and DNSSEC.

The last time I moved a handful of domains, two of them lost MX records in the process and their email bounced for half a day before a customer called me. I would rather not learn about problems that way again.

For this migration I want checks running before, during and after the switch:

1. A and MX records resolving to what I expect for every domain
2. Mail servers accepting connections on 25 and 587
3. SSL certificates still valid after the move

I already run Uptime Kuma internally, but it sits inside the same network. For the outside view I've looked at UptimeRobot, StatusCake and Dotcom-Monitor. Their site lists DNS, SSL, mail server and port checks in one place. Has anyone used one tool for all three during a DNS migration, or is it better to split them?

And if you have done a bulk nameserver change before, what bit you that you didn't expect?

Hi guys, I copied some of my files (around 600 GB) from my nextcloud to OpenCloud directly using Krusader while OpenCloud was stopped. After it finished copying the files, I changed the ownership and permissions to match OpenCloud, then I started OpenCloud, and after around 30 to 60 seconds, my unraid hangs. I cannot access the GUI or SSH, but I can ping my Unraid.

I already copied the files before I found out about the rclone thing when migrating. That being said, how do you migrate files? Or should I delete it and restart my migration using rclone?

Here's the info:
Unraid 7.3.1
OpenCloud container via Docker Compose method
Nextcloud LSIO container.

OpenCloud directory where I copied my files into: /mnt/user/opencloud/storage/users/users/<user id>/Files/data

nextcloud directory where I copied my files from: /mnt/user/nextcloud/<username>/files/Files/data

I run a home-server on a single Raspberry Pi 5, with n8n, a couple of shell scripts, and Beszel sending notifications to me over Slack.

I tried ntfy earlier, but gave up on it because I need two-way communication, such as approving certain actions on my server directly from my phone.

Right now, I've loosely categorized notifications into things like important for today and logs, but I'm not happy with this system. I'm looking for better ways to categorize them.

Here are some of the notifications I receive:

• Daily exercise tracking
• Daily weather forecast (morning and the previous night)
• Any containers unhealthy
• Any server updates (like temperature, RAM or CPU warnings)
• Any automation workflow failed (like switching to powersave at the end of the day if CPU load is below 40%, and back to schedutil in the morning)
• Status updates on backups and Git check-ins
• SSH alerts (still implementing this)
• Any service trying to notify over email (converted into a message and sent over Slack)

For example, when a container becomes unhealthy, Beszel sends me its logs, and an n8n workflow asks me whether I want to restart the container.

How do you organize notifications like these? Do you categorize them by source, severity, required action, or some combination of these? Do you use separate channels, threads, or labels, or keep everything in one feed?

I'm open to different approaches and would love to hear how you organize notifications in your homelabs, especially when using a single messaging app (Slack, ntfy, gotify, etc...) as the notification hub.

I am working on Spedo, a preview single-node RESP runtime for hot, rebuildable KV/JSON data. It is not a cluster or a replacement for a system of record.

For a small self-hosted app, what makes you add a separate cache process instead of keeping rebuildable state in the app? I am interested in the operational trade-offs and the point where the extra service earns its keep.

Recently (the last 2 days), I have been having a major problem with Grimmory not adding the new books/audio that I add to the library. With a lot of persistence, I have to use the CLI to log in to MariaDB to remove the delete record(s) that cause it to hang, and it is a real PITA to try to do from the CLI. I seem to recall seeing a program not too long ago that interfaces with the databases, but I do not recall the name, or if it was what I am thinking it was. Is there such a program or a better method for accomplishing what I need to do? It is not just MariaDB; it is other types of databases as well.

Looking into self-hosting a LLM. I have an elitedesk mini G9 with 32gb ram and an intel i7 that I want to add a eGPU to and I’m trying to decide what GPU/setup is the right one.

I see that Newegg is selling an Aorus box with an RTX 5070 Ti 16gb for about 1000 bucks. Is this worth the deal? I’m trying to budget for this amount exactly and this deal seems too good to be true. But I figure, even if I buy a used GPU, the cost of the additional components would take to my budget limit and beyond anyway. I am an absolutely beginner at this home lab stuff. Just need some help.

I was recommended a V100 but I’ve read that they require a fan that will sound like a lawn mower/vacuum to prevent overheating and I don’t want that in my house

Hi all. I’m building a homelab on an old PC with Proxmox and I want something close to UGREEN’s UGOS Pro (or fnOS): one web UI, one login, and integrated apps (file sharing, Jellyfin, Immich, downloads, backups, remote access).

My hardware: Ryzen 5500, 32gb ram, rx 9060 xt 16gb, 2x 1tb ssd nvme, 2x 4tb hdd.

What I’ve considered:

• Proxmox + ZFS on the host + Samba LXC + Community Scripts for each service, Homarr as the dashboard, and Pocket ID/Authentik for SSO.
• Cosmos Cloud (but it’s not FOSS and doesn’t handle NAS storage).
• ZimaOS or fnOS in a VM (but closed/limited licensing, and they seem unsupported when virtualized).

My priorities are: free, as open source as possible, and avoiding logging in to ten different services.

Questions:

1. Is there any project that bundles this kind of integration on top of Proxmox, or is DIY with SSO the standard approach?
2. If you went the DIY route, which SSO and dashboard combo gave you the least friction?
3. Any gotchas with permissions between the host, LXCs and VMs?

Thanks!

As the title says, I'm curious how everyone tracks or reminds themselves of software to test out that you find here on Reddit.

My problem is that when I come across a piece of software and want to test it, I send myself an email as a reminder and so that I have the link. However the problem I run into is that it could take weeks before I get a chance to actually test out that software and as such my mailbox becomes cluttered. Right now I have 635 emails and about 70% of that is from me as software reminders.

I use gethomepage.dev and have tried to use it for reminders but it isn't very friendly when trying to make modifications on mobile compared to desktop.

I've also tried using iOS' reminders app which is ok but wondering if there is anything better out there.

When the power goes out, your UPS might know before you do.

It sends an email. A few minutes later, your NAS sends another saying it has shut down safely. Power returns, devices come back online, and a few more messages arrive.

The next morning, you open your inbox: What happened last night? And is there anything I still need to deal with?

With one NAS, sending alerts to your regular inbox probably works fine. Add a UPS, another NAS, a router, and a few scheduled backup jobs, though, and you start piecing the story together yourself.

A disk reported the same error five times. Is that five problems or one?

A backup failed, but the next run succeeded. Did that actually resolve the problem, or is there still a gap worth checking?

You marked an alert as read. Did you fix anything?

That got me thinking about an old option sitting in a lot of device settings: SMTP.

Plenty of devices already support it, including older hardware with limited integration options. No agent to install, no vendor API to wait for. They can already tell you something happened.

But a mailbox mostly gives you a sequence of messages. You still have to work out which ones belong together, what recovered, and what remains unresolved.

I’m building LOCUS, a tool that brings local network devices and service links together in one place. Recently, I’ve been adding a local SMTP receiver so devices can send their notifications directly to it.

What I want to see when I open the dashboard is: what still needs my attention, and where do I go to deal with it?

For example, a NAS reports a disk problem repeatedly over several days. I’d like to see one ongoing fault with the related messages available underneath it. Next to it is a link to the NAS management page, so I can actually investigate.

An overnight UPS outage has a different story: power failed, then returned. I still want that history, but a recovered event shouldn’t keep demanding the same attention as an unresolved disk fault.

That’s the part I’m working on:

• Each device gets its own SMTP credentials, so incoming messages are associated with that device.
• Original messages remain available for inspection during the configured retention period.
• For supported message templates, repeated reports of the same fault are grouped, and corresponding recovery messages can close it.
• Unrecognized messages stay in the inbox without automatically being classified as faults.
• Unread messages and unresolved faults are tracked separately.
• Serious faults can optionally trigger an email through your own mail account.

Recovery matching needs care. A successful backup today doesn’t necessarily replace the restore point you missed yesterday. I don’t want a reassuring green indicator to hide something that still deserves investigation.

There’s also an obvious limitation: the receiver needs to stay reachable. If your devices, network, and LOCUS host lose power together, a local inbox can’t tell you what it never received. This doesn’t replace UPS shutdown coordination or an independent way to detect a whole-site outage.

Disclosure: LOCUS is my project, and the SMTP notification feature is currently in development and testing. Project page: locus.casa.

How are you handling device emails today?

Straight to your regular inbox? A dedicated mailbox? Forwarded to a messaging app? Or have you never configured them, then remembered the option only after something went wrong?

Which device notification has actually saved you trouble? And which ones became so noisy that you stopped reading them?

If you had a local inbox for your devices, what would you want it to handle? Grouping duplicate alerts, tracking recovery, temporarily silencing a known problem, pushing important messages to your phone—or something else?

I’d love to hear about your devices, setups, and opinions. I’ll collect the feedback and use it to help shape the LOCUS roadmap.

When something actually goes wrong, what information would save you time figuring out what to do next?

I am new to new hosting stuff, i am trying to get my personal ai assistant to send me a message every morning of my emails , meetings , tasks etc.

So the claude suggest me ntfy i checked it and found out that ntfy is open source. I got an idea to make it super secure why not self host it by downloading the docker image and host it on Render or any other free plaforms?

Is this a good idea? Is anyone using like this? Never used ntfy in my life

Hi everyone!

I'm working on an internal project for our company, and I'm looking for recommendations on existing open-source tools or implementation approaches.

Our goal is to build a task management system where managers can easily see what everyone is working on, track progress, and identify overdue or blocked tasks.

Key requirements:

• Managers need a dashboard showing tasks assigned to each employee, current status, progress, and deadlines.
• Employees should be able to update their progress and report blockers.
• The system should automatically send reminders before deadlines, when tasks become overdue, or when progress hasn't been updated for a while.
• Ideally, reminders should be delivered through WeCom (WeChat Work) or Lark (Feishu), since these are commonly used in our workplace.
• Self-hosting and customization would be a big plus.

I'm considering building this ourselves, but I'd prefer to start from an existing open-source project rather than reinventing everything.

I've looked into Plane, OpenProject, and workflow automation tools like n8n.

My questions:

1. Are there any open-source projects you'd recommend for this use case?
2. Has anyone integrated a task management system with WeCom or Lark?
3. Would you recommend customizing an existing platform or building a lightweight system from scratch?
4. Are there better architectures or tools I should consider?

I'd really appreciate any suggestions, GitHub repositories, or real-world implementation examples.

Thanks!

Hi everyone,

I'm looking for advice from people with experience managing production applications and self-hosting.

I'm running an e-commerce product discovery platform that tracks affiliate products, prices, offers, and product data from multiple sources. It has a database, backend services, APIs, and a relatively large amount of product and price-history data.

I'm still a beginner when it comes to server administration, so I've been using managed services to keep things simple. However, the monthly costs are becoming quite high, and I'm considering moving to a dedicated server or a more affordable VPS.

My current monthly hosting costs are approximately:

• Supabase: $120/month
• Railway: $200/month
• Total: around $320/month

The main issue is handling large amounts of product data, database queries, API requests, and data transfers. Egress and bandwidth costs are also important considerations, especially when working with affiliate products and price data from multiple sources.

I have millions of affiliate product records, several large tables containing product information and price history, and backend services that need to run reliably.

I'm considering self-hosting the database and backend on my own server, but I don't have much experience managing production infrastructure. I want to reduce costs without creating unnecessary complexity or compromising reliability.

A few questions for those with experience:

1. Would you recommend a dedicated server or a VPS for this workload?
2. What specifications would you suggest for a database and backend handling millions of records?
3. Which hosting providers would you recommend if my target is significantly less than $320/month?
4. Would it make sense to run the database and backend on one server initially?
5. How would you handle backups, security, monitoring, and disaster recovery?
6. Has anyone migrated from managed platforms to self-hosting? What were your actual monthly costs after migration, including storage, bandwidth, and backups?
7. Are there any hidden costs or potential problems I should consider before making the move?

I'm comfortable with development, APIs, and deployment configurations, but I'm still learning about server administration and production infrastructure.

My goal is to find a reliable setup that costs substantially less than my current $320/month while leaving room for future growth.

I'd appreciate recommendations based on real-world experience, especially from people who have migrated similar workloads.

Thanks!

I have komodo core in one vm and have komodo periphery in another vm both working fine.

Komodo periphery clones the repo to a folder named repos but copies the hole repo per container.

• Lets say i tried to deploy hommar. It clones hommar to that folder named repos and deploy it under a folder named stacks/homar/<full repo>.
• It should clone the full repo to that repos folder and copy it to stacks folder where hommar should deploy.

I tried using hommar.toml to sync and deploy. I specified a run_directory = "/home/user/docker/komodo/stacks/homarr" but it does not copy from repos folder to that stacks folder.

Running stacks from where it clones does not seem right.
I could do files on host but shouldn't it do what is supposed to do or i am missing something.

Thanks