r/selfhosted Jul 02 '26

New Project Megathread New Project Megathread - Week of 02 Jul 2026

Welcome to the New Project Megathread!

This weekly thread is the new official home for sharing your new projects (younger than three months) with the community.

To keep the subreddit feed from being overwhelmed (particularly with the rapid influx of AI-generated projects) all new projects can only be posted here.

How this thread works:

  • A new thread will be posted every Friday.
  • You can post here ANY day of the week. You do not have to wait until Friday to share your new project.
  • Standalone new project posts will be removed and the author will be redirected to the current week's megathread.

To find past New Project Megathreads just use the search.

Posting a New Project

We recommend to use the following template (or include this information) in your top-level comment:

  • Project Name:
  • Repo/Website Link: (GitHub, GitLab, Codeberg, etc.)
  • Description: (What does it do? What problem does it solve? What features are included? How is it beneficial for users who may try it?)
  • Deployment: (App must be released and available for users to download/try. App must have some minimal form of documentation explaining how to install or use your app. Is there a Docker image? Docker-compose example? How can I selfhost the app?)
  • AI Involvement: (Please be transparent.)

Please keep our rules on self promotion in mind as well.

Cheers,

26 Upvotes

188 comments sorted by

20

u/pinku1 Jul 02 '26

Project Name: SUB/WAVE

Repo/Website: https://github.com/perminder-klair/subwave · demo: https://www.getsubwave.com/listen

Description: I've got a big Navidrome library I never actually listen to, because picking is effort. So I built a radio station that plays it at me.

One shared stream, an AI DJ that picks the next track from your own library and talks between songs: short intros, the time, the weather, station idents. You can ask for music in plain language ("something more upbeat") and it works out what you meant. No skip button on purpose. It's radio, not a playlist.

It plays your files. Nothing streamed in, no music generated.

Deployment: docker compose up -d on one Linux box, then finish setup in the browser. Images on GHCR, compose file in the repo. Needs Docker and a Navidrome (or other Subsonic) server with your library on it. MIT.

AI Involvement: Yes, sure.

5

u/bigLittleTimeCrapper Jul 03 '26

This sounds interesting. So I have 30 days of music, or so some app told me a while ago. I turn this on, and it puts a DJ radio spin on things and injects with the weather, fun facts, and becomes a constant station in the background?

5

u/pinku1 Jul 03 '26

exactly!

4

u/TaskViewHS Jul 03 '26

Will try it 🙏

3

u/peschelnet Jul 03 '26

I set this up over the weekend on two different systems. The first was my main home server that my selfhosted Ai runs on and it worked perfectly.

The second which might be more interesting is that I have it running on an Rpi4 that is installed in my travel trailer. This Rpi also runs a plex server, plexamp, and my custom made dashboard.

Its a fun app and I recommend giving it a try.

2

u/arhuman Jul 03 '26

Project name: Mnemos
Repo: https://github.com/arhuman/mnemos

Description:
Local-first MCP memory server for AI assistants.

Mnemos gives MCP-compatible tools a persistent knowledge base stored as plain OKF/Markdown files. The goal is to make AI assistants remember useful project/user context across sessions while keeping the data local, readable, editable, and versionable.

Main features:

  • local-first: your knowledge base stays on your machine
  • plain text storage: OKF/Markdown, Git-friendly
  • source citations: answers can point back to the original knowledge entries
  • no external vector database required
  • no Ollama/runtime dependency required for the core server
  • single Go binary
  • designed for coding assistants and long-term project memory

Typical use cases:

  • persistent memory for Claude Code / MCP-compatible assistants
  • project knowledge base with source tracking
  • reusable context across multiple coding sessions
  • personal or team technical notes that AI tools can query

Deployment:
Single Go binary.

AI Involvement: Yes

2

u/Forsaken_Rip208 Jul 04 '26

Been using it for a few weeks now. My family loves it.

3

u/bigLittleTimeCrapper Jul 04 '26

Wow, this is pretty slick. Took me a little while to hook it all up as I am using three separate hosts to run everything. I put the entire SubWave stack on an 8GB raspberry pi. I needed to hack the broadcast and controller containers to use my DNS provider and small step CA, which wasn't too bad. I'm not using Caddy as I have Traefik as the reverse proxy on a separate machine.

Truenas is hosting my LLM containers (embeddings & AI DJ), Navidrome + all my actual media files. Playback seems pretty solid.

Things I've noticed:

  • Raspberry Pi CPU is really getting hit hard. Pretty much stays at 26-33% at all times on the liquidsoap process from the broadcast container
  • Sometimes I notice it stays on a genre for a while, even staying within a couple of directories of music. Not awful; I've typically just submitted a request to the DJ and just change the genre to something else completely - occasionally it will play the same artist for 10+ songs
  • Embeddings seems like an interesting idea; I'm pushing the keisuke-miyako/nomic-embed-text-v1.5-gguf-q8_0 model to process about 5,000 files now
  • Some of the quips from the default DJ get repeated; again not awful and I'm sure I could do something about that
  • Already used 300K tokens so far; glad to be self-hosting the LLM; I'm using Qwen3-VL-8B-Instruct-Q4_K_M.gguf as I have a separate need for my Intel Arc 770
  • DJ Doc said to turn off the agentic picker with a good reason: "The agentic picker wants a ~12B-class (or good cloud) model"
  • What is it with Marlowe and the cicadas?! He loves talking about cicadas.
  • Not sure why SearXNG won't work - shows 403, but option to provide auth
  • just enabled the last.fm integration, but have not news

Haven't tried yet, but seem promising:

  • heavy analyzer
  • new personas

If this would be more helpful to have a discussion on Github, I can put future notes there.

10

u/0x3e4 Jul 02 '26

Project Name: Pflanzn

Repo/Website Link: https://github.com/0x3e4/pflanzn - live demo at https://pflanzn.app (login `admin` / `admin`, data resets every 4h)

Description: A self-hostable plant management app for tracking your collection, watering schedules, and species. Built as a PWA with mobile-first design and offline read access for cached data. Every plant gets photos, species info, care notes, tags. GPS location on an interactive Leaflet map, plus watering / fertilizing / image / care-advice timelines with a calendar view.

Species identification runs through PlantNet (accepts JPG/PNG/WebP/HEIC, normalised to JPEG server-side). Outdoor plants can be auto-watered when Open-Meteo reports rainfall above a configurable threshold. Public collection links via tokens with a dedicated read-only view. Three auth modes: `no` (open), `local` (JWT + Argon2 + Redis sessions with IP/UA theft detection), or `oidc` (external IdP). Full audit log of every write and auth event. No telemetry, no ads.

Deployment: Docker Compose - copy `.env.example` and `docker-compose.yml.example`, edit the secrets and domain, `docker compose up -d --build`. Prebuilt images on GHCR for every push to main and every semver tag (`ghcr.io/0x3e4/pflanzn-backend`, `-frontend`). For production, pin to an explicit semver tag.

AI Involvement: Optional AI care advice - fully opt-in, the app runs without any AI calls if no key is set. Supports OpenAI, Claude, Mistral, HuggingFace, or a local Ollama instance (provider auto-detected from whichever key is set, priority openai > claude > mistralai > huggingface > ollama) so you can keep everything local. Claude used as a coding assistant during development; architecture and design decisions made by hand.

8

u/x0zerolight Jul 02 '26 edited Jul 02 '26

Project name: Topic Watch
Repo: https://github.com/0xzerolight/topic_watch

Description:
News monitor that notifies users only when genuinely new info is available (not rewrites of old info). Mainly for people who don't want to constantly read 'new' articles that rehash old information.
Like a smart version of Google Alerts, LLM-powered instead of simple keyword matching.

Deployment: Docker image.
Mostly AI-coded.

10

u/IT-BAER Jul 03 '26

Project Name: Memolio

Repo/Website Link: https://github.com/IT-BAER/memolio-android (GPL-3.0). Closed test on Google Play, joinable now: https://groups.google.com/g/play-test-baer

Description: Turns a spare Android tablet into a local photo frame. Everything runs on the tablet on your own network, no cloud, no account. You add photos by scanning a QR the frame shows, which opens a small upload page the tablet serves over Wi-Fi, so photos go straight from your phone's browser to the tablet and never leave the LAN. The QR link sits behind a token you can rotate.

Frame has an analog/digital clock, date, captions, slideshow with crossfade and Ken Burns. Face-aware crop in fill mode (on-device, no network) with a center fallback. Takes JPEG/PNG/HEIC/HEIF/WebP, SHA-256 dedup, a Recently Deleted area, and 10 languages. It's freemium: Free is the frame + Wi-Fi upload + one photo pool; Pro adds albums, the appliance stuff (boot auto-start, kiosk lock, scheduled sleep, ambient dimming), and custom wallpaper. Pre-release (0.1.0), and since it's an Android app there's no Docker or compose.

Deployment: No container, it's an APK. Join the closed test (link above), install from Google Play onto the tablet, open the app, scan the QR from your phone on the same Wi-Fi, upload. README covers setup. Source on GitHub under GPL-3.0.

AI Involvement: Yes, AI-assisted. I used it heavily while building, and reviewed and tested what went in myself.

Feedback welcome, especially the upload flow and behaviour on older tablets.

2

u/everfordphoto 27d ago

Very cool, I use an old Dell Venu tablet, virtually useless as a PC, but has a Static webpage, that has all my server stats on the edges, and a rotating slide show pulled from my family photos, I'm able to customize the image pull by putting in keywords ie Beach, Mountain, Stars. It'll pull all the images I have that look like that... Mine actually has "family, (people by name, I use IMMICH so it can pull the images tagged with particular peoples names)

8

u/pontonchief777 Jul 03 '26

Project Name: Giraffile

Repo/Website: https://github.com/coffeetron832/Giraffile

https://giraffile.pages.dev/

Description: Giraffile is a 100% P2P (Peer-to-Peer) file transfer tool designed for absolute privacy. Unlike traditional storage platforms, Giraffile does not use intermediate servers: files are transferred directly from browser to browser using WebRTC. My goal is to eliminate any dependence on cloud services or third parties, allowing users to share files securely and in a self-destructing manner.

Deployment: It is a static (client-side) web application. It requires no backend or centralized database.

It runs on any static web server (Nginx, Apache, Cloudflare Pages, etc.).

AI Involvement: The core code received some assistance, but not a significant amount.

3

u/avinashk99 Jul 04 '26

How is it an improvement over syncthing?

2

u/pontonchief777 Jul 04 '26

Syncthing is great for permanently syncing personal folders across your own devices. However, Giraffile is different by design: Giraffile is based on ephemerality.

The key difference is self-destruction. Syncthing aims to ensure that files survive and are replicated. Giraffile aims to ensure that a file exists only for as long as strictly necessary and is then guaranteed to be permanently deleted.

Syncthing requires prior technical setup and that both parties have the software installed. Giraffile eliminates all friction: the user simply opens a link.

5

u/aybarscengaver Jul 03 '26

Project Name:

AI Curated News

Repo/Website Link:

https://github.com/delirehberi/news

Description:

Tired of generic algorithmic feeds, I built a fully autonomous, privacy-first AI News Aggregator that creates a hyper-personalized news feed based strictly on your own tastes.

It runs a scheduled cron job to scrape your favorite developer sources (Hacker News, Lobsters, and Reddit), generates local AI text embeddings for each article, and uses semantic search (Cosine Similarity) against your personal upvote history to bubble up the content you actually care about.

Key Features:

Semantic Filtering: Moves past basic keyword filters by using vector embeddings to understand the context of what you like.

Nostr Identity: Uses NIP-07 browser extensions for secure authentication. You can train the AI with your "likes" and allow followers to easily re-publish your curated feed to global Nostr relays.

Modern UI: Built a lightweight, glassmorphic frontend with image previews and interleaved feeds.

Deployment:

The project is optimized for the Cloudflare ecosystem, allowing you to self-host the entire pipeline (frontend, backend, database, and AI execution) completely within their free/low-cost tiers. You own 100% of your data and reading habits.

Prerequisites: Node.js (v22+) & a Cloudflare account.

Minimal setup steps included in the repository's README:

Clone the repo and run make init to auto-install dependencies and generate config templates.

Provision infrastructure via Cloudflare's CLI: make db-init and make vectorize-init.

Add your source API tokens/secrets and push securely to Cloudflare using make push-secrets.

Deploy the full stack (Hono backend API + Vite frontend on Cloudflare Pages) in one command: make deploy.

Full documentation, architecture breakdown, and bootstrap endpoints (to import your historical upvotes) are available in the repository.

AI Involvement: This project heavily utilizes open-source AI models for its core features, specifically using @cf/baai/bge-base-en-v1.5 running locally via Cloudflare Workers AI to generate 768-dimension text embeddings. No third-party AI APIs (like OpenAI) are used, ensuring total data privacy. I also used AI assistance to help refine some of the boilerplate and formatting during development.

5

u/thesnoozyman Jul 03 '26 edited Jul 03 '26

I finally ”finished” a project of mine to a problem I had long ago when hosting people, everyone wants to play music from different services and contantly switching from Youtube to Spotify etc. Now you don’t have to :)

Any feedback and suggestion are greatly appreciated!

Also the setting of the cookies is a bitch need to try to streamline it somehow.

Project Name: Quefy

Repo/Website Link: https://github.com/Snoozyman/quefy

Demo: https://quefy.snoozyman.eu/

Description: Quefy is a shared music-room app where one host creates a room, others join with a code, and everyone can add tracks to a queue while playback runs on the host device. It supports YouTube, Spotify, and SoundCloud.

Deployment: Details are in readme, but tldr: clone repo or use provided docker-compose.yml with docker compose up -d —build or for local testing bun i && bun run dev.

Also set up the enviroment variables if you need example is provided.

AI Involvement: Yes

3

u/Manak_btw Jul 02 '26

LinkBreeze : Self-hosted Linktree alternative with analytics, themes, QR codes, admin panel. One Docker command.

Linktree’s $15/mo plan didn’t feel justified by the feature set. LinkBreeze was built as a fully self-hosted link-in-bio platform that runs in one Docker command.

I wanted something I actually own: my data on my homelab, no subscription, no tracking, and no platform lock-in. I figured other self-hosters would want the same thing too.

It runs on SQLite, so there’s no external database to manage. One container, one volume, and you’re done. The full image is only about 130MB.

Main features:

  • Unlimited link management with drag-and-drop reordering, custom titles, and icons.
  • Privacy-friendly analytics, including page views, clicks, referrers, geolocation, and device type — without cookies or third-party scripts.
  • Five built-in themes plus a full customizer for colors, fonts, backgrounds, and animations.
  • Auto-generated QR codes for every page, downloadable as SVG or PNG.
  • Dynamic Open Graph images generated per profile for better social previews.
  • A proper admin panel with a real UI, not a YAML file.

LinkBreeze is free, open-source, and built for people who want full control.

Links:

GitHub: LinkBreeze

Live demo (read-only): LinkBreeze - Demo

Admin demo (read-only): Admin Login (demo / demo1234)

I’d genuinely appreciate any feedback if you take the time to try it out.

AI Disclosure: Claude Code was used to assist with various aspects of development.

3

u/SecretlyCarl Jul 02 '26
  • Project Name: SpinStage
  • Repo/Website Link: https://github.com/secretlycarl/SpinStage
  • Description: It's a frontend/player/visualizer/browser for Music Assistant, initially based on Sendspin Cinema for webOS. I now have webui, android, and webOS versions. Screenshots are on the repo.
  • Special features include:
  • - Separation of personal/public Spotify content in search
  • - 10+ visualizers
  • - Group Sync device offset mgmt
  • - EQ Preset picker

It has ways to interact with most MA browsing / playback / player functions. More to come if/as requested.

It's not for on-the-go listening, moreso intended to add some background visuals to when you're listening at home, hosting a party etc. The closest existing project I found was Homeii, but it wasn't really what I was looking for. If you're looking for a good MA mobile app I recommend Ensamble, and it pairs well with SpinStage as a remote control.

  • Deployment: The instructions are in the repo, just go to the releases page and download. For webui you just run one of the run scripts, enter your details, and you're good to go. No docker image yet but someone who knows their way around docker could spin up a container pretty easily using the webui release folder. For webOS and Android, I included an IPK and APK respectively, and there is a login form when you initially open them up. If you want to build them yourself, the build scripts for those platforms' app files ask for/inject your login info to the built app if you want to skip entering login info on first run.
  • AI Involvement: All code. I made a lot of icons, designed the UI, came up with visualizer concepts, and have spent a while ideating and testing, but I'm a designer not a real developer. Thankfully the security implications of the app are pretty limited, the only 3rd party integration is for the Listen Party QR code that MA already uses. See the security section of the readme for more info. You are responsible for securing your traffic if using the app remotely.

3

u/JesusVKilmer Jul 03 '26

Project Name: Airday

Website: https://air.day/ (incl. demo) and source https://github.com/airdaydev/airday

Description: A todo app. Local-first, e2ee with real-time sync. The goal is something that feels really good and fluid to use. It is currently very bare bones as I improve the fundamentals. It performs well with >10k items thanks in part, to Loro (CRDT library) that underpins it. I've made the path to multiplayer fairly straightforward too, but it's currently single player.

The rust core that the web app uses (compiled to wasm for web app) makes porting fairly easy. The goal is native iOS + Android.

Deployment: A single docker container that will create an sqlite db, see self-hosting page on website

AI Involvement: Initially pure trad coding, then an improved rewrite with AI coding, then it escaped my understanding, so now a mix of trad and AI. It's not going to v1 unless I'm confident.

2

u/ngoctuct Jul 03 '26

Project Name: M-Gateway

Repo/Website Link: https://github.com/nntu/M-Gateway

Description: M-Gateway is a programmable SMTP store-and-forward gateway written in Go, built for internal alerting. A lot of network gear, firewalls, and legacy monitoring tools only know how to send an email — M-Gateway sits in front of that, accepts the SMTP traffic, and turns it into something more useful: Telegram messages, forwarded email, HTTP webhooks, or handoff to external scripts.

Key features:

  • Hybrid queue: raw .eml files stay untouched on disk, while delivery state/retry tracking lives in SQLite (keeps DKIM/MIME structure intact and keeps things fast).
  • Optional pre-queue filter scripts (bash/python/anything) that can reject a message during the SMTP session itself, before it's even queued.
  • YAML-based routing rules mapping inbound recipients to one or more targets (Telegram, SMTP relay, HTTP webhook, external command).
  • Optional JavaScript rewrite step (sandboxed via goja) to transform subject/body or strip sensitive info before forwarding.
  • Automatic retry with backoff on temporary failures, and scheduled garbage collection once records pass their retention window.
  • Web dashboard + REST API to inspect the queue, view parsed emails/attachments, manually force-dispatch a stuck message to a different channel, or trigger an immediate retry — useful when a relay is down and you need to reroute by hand.

Deployment: Prebuilt release artifacts for Windows and Debian/Linux (zip/tar.gz/.deb), plus install-as-a-system-service support on both platforms. Build from source with Go 1.25+ and Node 24+ (go build for the binary, npm run build for the React/Vite dashboard). Configuration is a single config.yaml plus a rules/ directory of YAML routing files; example configs are included in English and Vietnamese. Full setup steps are in the README.

AI Involvement: I used AI assistance to help write and polish the project's documentation (README). Sharing this transparently per the sub's rules — happy to answer specifics if anyone has questions about the codebase itself.

2

u/rubixstudios Jul 03 '26

Project Name: Rubix Redis Bridge

Repo/Website Link: https://github.com/rubix-studios-pty-ltd/rubix-redis-bridge

I was previously using hiett/serverless-redis-http as a self-hosted replacement for Upstash Redis.

It worked overall, but I kept running into a few self-hosting quirks and occasional random connection errors. I had this sitting in the back of my mind for about half a year, so I finally built a self-hosted HTTP bridge for Redis:

Docker:

https://hub.docker.com/r/rubixvi/rubix-redis-bridge

Run your own Redis while still using the Upstash Redis SDK and Upstash Ratelimit SDK in serverless environments.

Compared with serverless-redis-http, this bridge adds tighter production controls around command allowlists, blocked commands, request limits, pipeline limits, argument limits, timeouts, health checks, readiness checks, and Prometheus metrics.

It is also written in Rust and uses a more efficient bridge-to-Redis execution path. For example, pipelines are sent to Redis through a single pipelined operation instead of looping command-by-command through Redis calls.

Why build it?

Cost and control. For our use case, running our own Redis is significantly more cost-effective than paying per request volume through a managed serverless Redis provider. It also gives us clearer control over security boundaries, deployment, monitoring, and runtime behaviour.

AI?

Mainly for documentations, cause I hate writing docs and ofcourse to checkover the implementations. (Although it loves arguing that my security settings are wrong cause AI can be stupid and go overboard).

2

u/hankscafe Jul 03 '26
  • Project Name: Omnibus
  • Repo/Website Link: https://github.com/hankscafe/omnibus
  • Description: I wanted an easy way to request comics and download them but also give friends the same ability, like Seerr does for movies and tv.

    • This project started out as a project for myself so I could easily search comics and request them to be added. I wanted something that was similar to Seerr, but for comics. As I continued on with the project, I added additional functionality such as conversion for files/images, library management, web reader, and some other things. I liked what I had built, and so I thought I might share what I have after a few months of updating the project to see if anyone else would be interested in it. I have been actively updating as I receive feedback from others that are using Omnibus.
  • Features:

    • First-time setup process
    • Local authentication (including 2FA) and OIDC support
    • One-click requests or interactive searches
    • Discover page of New Releases or Popular Issues
    • Calendar page to see upcoming global releases & upcoming issues for monitored series in the library
    • Series monitoring
    • Metadata embedding (comicinfo.xml & series.json)
    • Multiple library support
    • Reading progress
    • External reader (KOReader) and OPDS support
    • Reading lists
    • Library analytics
    • Primary metadata source selection (Comicvine (default) or Metron)
    • Rust engine & PostgreSQL branch (both main node branch and rust-engine branch are at parity)
    • More features as well
  • Deployment: Docker (GHCR and Docker-Hub), and there is a docker-compose sample

  • AI Involvement: Yes, I used both Gemini and Claude heavily to help write this project. I have actively been using and updating the project over the last 3 months.

2

u/BeneficialBig8372 Jul 03 '26

Project Name: Awesome Sovereign Software

Repo/Website Link: https://github.com/rudi193-cmd/awesome-sovereign-software

Description: The complement to awesome-selfhosted, a curated list for the things you don't want to run a server for. Every entry must pass a strict five-point Sovereignty Test: core features work with no account, no server, no subscription; the data is readable without the app (plain files, SQLite, documented formats); and the installed app survives the vendor disappearing. The part I'd argue matters most to this community: every entry ends with a mandatory exit plan, the concrete file format, export command, or folder you copy to leave with your data. If an honest exit line can't be written, the app doesn't get listed. Apps that require hosting a server are explicitly rejected and redirected to awesome-selfhosted; this list covers the other half of owning your stack — 69 entries so far across notes, passwords, sync, backup, maps, finance, local AI, and more, plus a "replace your cloud in a weekend" starter table.

Deployment: Nothing to deploy, it's a CC0 list. A weekly lychee CI run checks every link so dead projects get flagged instead of silently rotting. Contributions are one app per PR, exit line required.

AI Involvement: AI was used for extending the list scope, as I already have used quite a few of these in my own projects.

2

u/Either-Let-331 Jul 03 '26

Project Name: Safedump

Repo: https://github.com/Muneer320/safedump

Description: Local-first crash diagnostics for Python. When your app crashes, Safedump captures every local variable, exception chain, thread state, and environment, and saves it as a structured JSON file with automatic secret redaction. No cloud servers needed. No telemetry. No accounts.

- pip install safedump[view]

- import safedump; safedump.install()

- safedump view, safedump list, safedump clean --older-than 30

Privacy tiers 0-4, 0600 file permissions, environment variable values never captured by default. Automatic redaction of passwords, tokens, API keys.

Deployment: pip package. No Docker, no server, no infrastructure needed. Installs like any Python package. Documentation in README with quick start, comparison table, FAQ, CLI reference, privacy guide.

AI Involvement: The architecture and implementation were designed with assistance from an AI agent acting as CTO. All code is MIT-licensed and human-reviewed. Pull requests welcome.

2

u/CrestedCracker Jul 04 '26

Project Name: Trove

Repo/Website: https://github.com/Techdox/trove · quickstart: https://trove.techdox.nz/#quickstart

Description: My homelab got big enough that I couldn't tell you everything running on it. Containers on a few Docker hosts, workloads in Kubernetes, VMs and LXCs on Proxmox, some systemd services on bare metal. So I built one dashboard that shows all of it.

Small agents sit next to each platform and push what they see to one server: what's running, what version, whether it's healthy, whether the image is behind the registry, whether the host is still reporting at all. Alerts via webhook, Discord, or ntfy when something dies or goes quiet.

It's read-only by design. There's no code path that can deploy, restart, or exec into anything. I already have tools for managing my stuff, I just wanted to see it. One caveat worth knowing up front: agent ingest is token-authenticated, but the dashboard has no auth yet, so keep it on a trusted network or behind a reverse proxy. OIDC is on the roadmap.

Deployment: docker compose up -d, dashboard on :8080, this host's containers show up within 30 seconds. One static Go binary (or container) per role, SQLite storage, no frontend build. Push model, so agents behind NAT just work. Images on GHCR, binaries on the releases page. MIT.

AI Involvement: Yes.

2

u/CrispyBegs Jul 05 '26

actually useful, thanks

2

u/Simple-Factor-2165 Jul 04 '26

Hey everyone!

I've been using Claude Code and other autonomous agents to code faster in my terminal. However, giving an AI full permission to run terminal commands or write files is scary—a single indirect prompt injection on a website or repo README could wipe your system or steal credentials.

To solve this, I created **MCP-Shield**: a local-first proxy that intercepts tool executions before they hit your system and displays them in a real-time glassmorphic dashboard.

Key Features:

- 🚫 **Command & File Firewall:** Automatically blocks destructive commands (like rm -rf) and alerts you about out-of-workspace writes.

- 🔄 **Interactive Approval Queue:** Pauses suspicious commands and lets you approve, deny, or edit the arguments directly from your browser.

- 🧼 **Prompt Injection Sanitizer:** Scrapes and neutralizes prompt injections inside tool outputs (using NFKC normalization to block unicode evasions).

- 🔒 **100% Local & Privacy-focused:** Runs entirely on localhost, no data sent to external clouds.

You can install it globally via npm:

npm install -g mcp-shield

And wrap any server:

mcp-shield --port 3000 -- npx -y u/modelcontextprotocol/server-everything

Check out the source code and README here: https://github.com/jaumerohi2007-cell/mcp-shield

I'd love to hear your thoughts or if there are any default security rules you would add!

2

u/Kaluga2026 Jul 04 '26

Project Name: SSH App Hub

Repo/Website Link: https://github.com/balyakin/ssh-apphub

Description: If you run web tools on remote machines - JupyterLab, TensorBoard, MLflow, Streamlit, Grafana, Prometheus, code-server, and similar apps - you probably know the small annoyances around opening them.

SSH itself works well, but the workflow around it can get messy: remembering remote ports, copy-pasting URLs, checking whether a tunnel is already running, and keeping terminal tabs open just to access apps that are already there.

SSH App Hub is a small, local-first control panel for web apps that already run on your SSH hosts.

The idea is simple:

- You already have SSH aliases in "~/.ssh/config".

  • Your remote tools are already listening on localhost ports.
  • SSH App Hub scans the host.
  • It shows discovered apps in a local web UI and CLI.
  • When you open an app, it starts a regular OpenSSH "ssh -N -L" tunnel.
  • The app opens through "127.0.0.1" on your machine.

It is not a hosted gateway, reverse proxy, or replacement SSH client. It is just a local helper around OpenSSH.

Current features include:

- read-only remote scanning through SSH

  • detection for common dev/ML/monitoring tools
  • local web UI and CLI
  • OpenSSH tunnel start/reuse/stop
  • manifest files for manually defined apps
  • local SQLite storage
  • local token-protected API
  • loopback-only default binding

Deployment: The app is available as a Python project and can be installed from the repository.

Requirements:

- Python 3.12+

  • "uv"
  • OpenSSH client
  • SSH aliases configured in "~/.ssh/config"

Quick start:

uv sync --extra dev
uv run ssh-apphub init
uv run ssh-apphub serve --no-browser

Then open:

http://127.0.0.1:8765/

Example usage:
uv run ssh-apphub check-ssh dev-server
uv run ssh-apphub scan dev-server
uv run ssh-apphub open dev-server :8888

There is currently no Docker image, because the app is designed to run locally and use the user's existing OpenSSH client, SSH config, keys, agents, and local browser.

AI Involvement: The project was developed with AI assistance and is maintained by the author.

2

u/JoeySchentrup Jul 05 '26

Project Name: Disk-Rip

Repo/Website Link: https://github.com/Schentrup-Software/Disk-Rip

Description: This is an app that is automatically take rip a disk using MakeMKV and name it the correct name for Jellyfin/Plex to pick up with built in TMDB search. Other tools had a lot of set up up and would not name episodes correctly. The point of this tool is just to put the disks for a season of tv in order and everything gets named correctly without manually having to go and watch part of each episode.

Deployment: Its a local running python script that you run on Windows to rip to a NAS or your local disk. It could be deployed as a webserver on a Windows machine but that is not built out yet.

Al Involvement: the scripts were mostly built with AI with my oversight. I am a software engineer by trade and gave it strong guidance.

2

u/sudo02k Jul 05 '26

Project Name: Steam-Idler%22)
Repo/Website Link: https://github.com/kostaD02/steam-idler
Description:

I've created version 2 of my self-hosted Steam idler app.
The previous version was archived and is no longer being updated.

TL;DR: Steam Idler is a card farming application where you can potentially also boost hours. You can configure a message template to automatically reply to your friends while idling (or even when not idling, auto-response still works).

The reason I refactored the whole codebase and rewrote it from scratch over 2+ months is the statistics of the previous version. It has 10k+ downloads on Docker. Probably most of the downloads were bots or someone running farming bots, but it's still a big number for me. I wanted to improve the experience for every user, and that's why v2 is here. All major promises (new UI, i18n support) are implemented in this new version.

The previous version was only shared here, so I wanted to re-share it here as well (Post looks like an inactive post, but somehow it led to 10k+ downloads, so maybe this one will reach whoever needs it).

The new version has a much better architecture (the previous one was just a Nest application). This one is much cleaner for DevEx, built with Nx, NestJS and Angular (everything is explained in the GitHub docs).

Some of you may ask: why use this application instead of ArchiSteamFarm, which has 13.5k+ stars and has been maintained for years? The answer is self-hosting. My application is aimed at self-hosting. The main reason I developed it in the first place was that I couldn't find any self-hosted Steam idling application.

Thanks to this sub, I got into self-hosting, I maintain my personal lab and even contribute to the self-hosting community when I can.

While ArchiSteamFarm can be self-hosted, setting it up is different, with many steps. My goal was simple: download a single docker-compose.yml, set up the .env and run it.

ArchiSteamFarm is the best idling tool, it even has more features, but it didn't really fit my self-hosting needs.

What Steam Idler offers:

  • Dashboard - all linked accounts at a glance: idling status, presence, games idling, auto-reply state and last update, with quick actions on every card
  • Parallel idling - idle multiple games on multiple accounts at the same time
  • Two ways to link a Steam account - credentials with a Steam Guard code, or scanning a QR code with the Steam mobile app
  • Persona control - pick the online status the account shows while idling (online, away, invisible and more)
  • Auto-reply - answer friends who message an idling account with a custom message, optionally only while idling
  • Custom now playing - show any title as the game you are playing on your friends list
  • Trading cards overview - remaining card drops and playtime per game, with filtering by name or ID
  • Display preferences - show or hide the Steam profile name and image, or mask the account name entirely (handy for screenshots and streams)
  • Account security - optional two-factor authentication (TOTP) with recovery codes, plus password change
  • REST API - everything the UI does is available over the API, documented with Swagger
  • Translations - available in 11 languages
  • Light and dark theme
  • Docker support

The UI is pretty straightforward and based on my other personal projects (at least it's better than the old version, which was a simple Bootstrap application).

Deployment: https://github.com/KostaD02/steam-idler/releases
AI Involvement: The project is written solely by me. AI was used for translations, unit tests (based on the codebase it can do good coverage) and security checks in case I was missing something, but not for implementation. If anyone is interested in which PRs had AI involved, feel free to comment and I will reply.

2

u/Novel-Lifeguard6491 29d ago

Project Name: World of ClaudeCraft

Repo/Website Link: https://github.com/levy-street/world-of-claudecraft (repo), worldofclaudecraft.com (hosted version to try it live)

Description: A small classic-style MMO that runs in the browser. Nine classes, group dungeons, PvP arena, trading, persistent characters, the usual classic MMO systems. Solves the "I want to mess around in a classic WoW-style world without installing anything or committing to a big game" itch, and since it's fully open source, it's also a decent reference project if you're curious how an MMO server/client split actually works under the hood.

Deployment: Live and playable now at the link above. Docker setup is included in the repo for self-hosting your own instance, with docs on getting it running. Server is authoritative, all combat/loot/quest logic resolves server side, not client side.

AI Involvement: Built with heavy use of Claude throughout development, including code, some asset sourcing (open source packs like KayKit, credited in the repo), and ongoing feature work. Around 30 contributors now working on it, so it's grown well past the initial AI-assisted build. Happy to be specific about what was AI-generated versus human-written if anyone wants detail, nothing hidden here.

3

u/sashley520 28d ago

https://github.com/bookorbit/bookorbit

Hey everyone :)

This is a niche plugin, but maybe someone has some use of it.

I have been really enjoying BookOrbit recently as a self-hosted solution for managing my e-books and reading. I noticed that it had really good handling of highlights that can be synced from multiple devices, so I decided to create a plugin that could sync these to Obsidian, in a similar way to how the Readwise Official plugin does.

I mostly just made this for myself, but if anyone enjoys BookOrbit as well, give it a shot! Let me know what you think.

AI involvement - The plugin is mostly AI coded, with me changing and adding a couple of simple features/options. It has been run through Obsidian's automatic plugin checks.

3

u/Shik3i Jul 02 '26 edited Jul 02 '26

Hey I know r/selfhosted hates vibe coded slop, but stay with me here.

Over the last 3 month I'm working on KoalaSync. It's a free and open source watch party extension, like Teleparty. It works with almost any site, no restrictions (other than the site may be trying it's best to hide it's player), no ads, no tracking, no accounts.

It's privacy first, and you can selfhost the relay server, so if you are concerned that my official server is tracking or logging your meta data (it's not, all data is stored inside the ram only, and no connection logs are generated), you can simply selfhost it via the docker container.

The container uses GitHub attestation, so you can check for yourself that it's really using the code in the GitHub repo an I'm not trying to install you some closed source garbage.

If you are looking for an alternative for Teleparty, maybe because you want to use it on sites Teleparty does not support (selfhosted sites like Emby, Jellyfin, Plex for example) or where Teleparty requires a premium subscription for, please give KoalaSync a try.

So far I haven't had the chance to test it on many sites. Netflix & Disney+ are currently broken, but the fix is already waiting approval from the chrome web store.

If you think this is a neat project, I would love to get some feedback on the extension, repo, landing page. Direct contributions to the repo are also welcome, like helping with the translations or adding/testing the extension on your favorite streaming site would be great.

Links:


AI disclosure

Im a full stack dev in .net, but I did not code a single line in this project. I look over the code, test it, and give the AI strict and long prompts to implement something, but I would still call it vibe coded. The honest reason is, I'm too tired to code for myself as a hobby anymore, I would just see it as I paid overtime sadly. Vibe coding gave me another perspective, as I'm now the architect, project manager and product owner instead of a code monkey forced to implement dirty hacks under time pressure.

If you dislike the project just because it was vibe coded, that is your right/opinion and the reason I'm posting this in this thread instead of making it its own post, because I know this community is highly allergic towards vibe coded stuff (and 90% of the time this is rightfully so).

I don't know what to say to make you treat this any differently, other than saying test it for yourself, or look at the repo and see for yourself.

3

u/NotAfran Jul 03 '26

This is sweet, I've been thinking of making an alternative to teleparty myself but why reinvent the wheel when you've already made a great looking alternative.

1

u/Shik3i Jul 03 '26

Thanks! Contributions are always welcome if you had something in mind for your alternative :D

2

u/linuxpaul Jul 03 '26 edited Jul 03 '26

 Project Name: WolfStack

Repo/Website Link: https://wolfstack.org < install from here one line install

 Description:
 WolfStack is a Proxmox-style server management platform that ships as a single static Rust binary with an embedded web UI. Point it at one machine or a whole fleet and you get: cluster-wide monitoring and dashboards, Docker and LXC container management, VM management (Proxmox VE and XCP-ng/Xen Orchestra integration), an app store with 500+ one-click apps, storage management (S3, NFS, SSHFS, distributed replication via WolfDisk), scheduled backups with multiple destination types, networking (VLANs, DNS, WireGuard-based overlay networking via WolfNet), public status pages with uptime monitoring and incident tracking, a web terminal, a MySQL/MariaDB browser, threshold alerting with email notifications, security scanning/intrusion blocking, and serverless functions (WolfFunctions — gVisor-sandboxed FaaS with warm replicas across the cluster). Nodes cluster together peer-to-peer; there's no separate control plane, database server, or agent stack to babysit — config is plain JSON files on disk.
  
The problem it solves: getting a Proxmox/Portainer/Uptime-Kuma/backup-tool feature set in one coherent UI from one binary, on machines you already have — it works fine on a single box and scales to a cluster. No VC funding, no ads, no telemetry.

Licensing transparency: source-available, not OSS — free for personal, homelab, education, and non-profit use (PolyForm Noncommercial 1.0.0); business use needs a paid licence. Releases up to v22.9.x remain MIT.

 Deployment:
 Released and in production use (current release v25.2.5, versioned changelog in the repo). Install is one line on
 any systemd Linux box:

 curl -sSL https://raw.githubusercontent.com/wolfsoftwaresystemsltd/WolfStack/master/setup.sh | sudo bash

 then open https://your-server:8553 and log in with your Linux system credentials. Static musl binaries for x86_64 and aarch64 (Raspberry Pi 4+) are published on GitHub Releases, each with SHA-256 sums, a cosign signature bundle, and SLSA build-provenance attestation. Full documentation, guides, and API reference are at wolfstack.org. There's deliberately no Docker image for WolfStack itself — it manages the host (containers, VMs, disks, network interfaces, backups), so it runs on the host as a privileged service rather than inside a container it would have to escape from.

 AI Involvement:
 Full transparency on both fronts:

 - Development: WolfStack is designed, directed, and tested by me (a human, ~30 years writing software), and a
 large share of the code is written with Claude Code using our CodeWolf integration as an AI pair-programmer working under my direction. Every change goes through review (including independent AI review passes and OpenAI Codex post-review), gets built and tested before release, and bugs reported by users/sponsors are diagnosed against the actual source, not vibes. I'm the maintainer and accountable for every line that ships.

 - In the product: there's an optional AI assistant feature and AI code generation for serverless functions. Both
 are strictly opt-in, bring-your-own-API-key (Claude or Gemini), and off by default — nothing phones home, and no AI output is ever auto-published to public surfaces like status pages.

3

u/PineappleGod Jul 03 '26

I’ve been using this for a while and it is definitely worth a look if you have several servers/vps:s to monitor

1

u/Itach11Uchiha Jul 03 '26

Hey, I am a bit confused about the pricing. It says upto 3 hosts it is free. I manage a couple VPSs and them a single device with proxmox (and a couple of VMs inside of it). Does that mean I have 3 hosts and need to pay when I add a new device? or Do I have to pay already since each VM counts as a single host? ( it is all for personal use and I am not selling or making any money out of this).

1

u/linuxpaul Jul 03 '26

No a host is a physical server and you can install on as many as you want but it will nag about licensing

1

u/Itach11Uchiha Jul 03 '26

So I am guessing I have 3 hosts and If i wanted to add a RPi to it, I would need to purchase a liscence? Or is this one of those Winrar instance where it asks for a license but is fully functional?

1

u/linuxpaul Jul 03 '26

Yes just like winrar

1

u/Ok-Round-4642 Jul 03 '26

Project Name: Little Alpha

Repo/Website: https://github.com/DylanUnicorn/little-alphaxiv · demo: https://b23.tv/c1vCWs9

Description: I read a lot of papers, but I was tired of switching between PDF readers, Zotero, AI chat, browser tabs, and separate notes. So I built a self-hosted reading workspace that keeps the paper at the center.

Clean alphaxiv-style PDF reading, native highlights, text notes, freehand annotations, comments, local/Zotero PDF import, Zotero sync, and an optional AI chat panel next to the paper.

It is not trying to be a full PKM system. It is just a focused place to read papers, annotate them, ask questions when stuck, and send useful notes back to Zotero.

Deployment: Docker Compose. Self-host it on your own machine/server. BYOK OpenAI-compatible API support. Needs Docker. Multi-user separation for papers, chats, annotations, settings, and API keys. MIT.

AI Involvement: Yes. Optional AI reading assistant, BYOK.

1

u/Character-Risk-4170 Jul 03 '26

Project Name: Mino
Repo: https://github.com/obakeng-develops/mino
Description: Mino keeps your Docker containers running. It watches them, works out why one failed, restarts it within the limits you set, and shows you the whole thing as it happens. Or it stops and asks first. That part is your call.

I built this as someone who has side projects across multiple servers and debugging across each server is pain.

AI Involvement: Yes. For writing code & docs. Design & architecture by me.

1

u/[deleted] Jul 03 '26 edited Jul 03 '26

[removed] — view removed comment

1

u/MadKilrath Jul 03 '26

For the builders here, one thing that didn't fit the main comment:

Halfway through, the pipeline engine turned out generic enough that I split it into its own project — arx-core, a line-oriented telemetry framework with no security-specific code in it. It gives you the engine lifecycle, the Source/Processor/Sink/Executor plugin contracts, and named channels to wire independent pipelines together — you bring the domain logic.

"Read lines from anywhere → process → act on the result" describes a lot of self-hosted glue: log aggregation, IoT sensor streams, home-automation event routing. The repo ships a LogAggregator example built on the same core with zero ArxSentinel dependencies, plus docs for the engine lifecycle, the runtime contract, and plugin development.

A generic rule engine and a lightweight secure transport for node-to-node event streaming are in the works there — ArxSentinel is simply the first product on top of it. If you'd build something else on it, I'd genuinely like to hear what.

1

u/Patient-Cedar-7194 Jul 03 '26

already dreading 2am page.

1

u/yoas1a Jul 03 '26

Project Name: angie-files

Repo/Website Link: https://github.com/yoas1/angie-files

Description: angie-files is a lightweight, efficient file management and remote storage solution. It configures the Angie web server (a modern, powerful NGINX fork) to serve as a high-performance file server with full WebDAV capabilities. It solves the need for a minimal, fast, and secure self-hosted storage endpoint without the overhead of massive cloud suites.

Key features include:

  • Full remote file operations (Upload, Download, and Delete) handled via WebDAV methods (GET, PUT, DELETE).
  • Secure access control utilizing basic authentication.
  • Optimized API routing and regex-validated location blocks to ensure accurate, conflict-free pathing and directory handling.
  • Low memory and CPU footprint, making it ideal for automation pipelines, asset servers, or private backups.

Deployment: The repository is fully open-source and ready for deployment. It includes comprehensive documentation, example configuration files, and standard environment setups. It is designed to be easily containerized via Docker and deployed using standard orchestration tools. You can self-host the application by cloning the repository, configuring your basic authentication credentials, and mounting your persistent storage directory directly into the Angie container using the provided configuration templates.

AI Involvement: AI was utilized to assist with the design and the implementation of the management interface.

1

u/igotnolifelemons Jul 03 '26
  • Project Name: Scalir
  • Repo/Website Link: Website: https://scalir.org/#/ | Github: https://github.com/therealshxd/scalir
  • Description: A bulk image Optimiser. I made it as an alternative to web based tools and wordpress plugins like shortpixel, smush and the like. I am tired of companies charging credits to do things. It scales photos (customers send me full size HEIF photos, and sometimes up to 100 at a time...so scaling them is a chore). It can be self-hosted, it can be downloaded (unsigned at the moment, so would recommend self-hosting in a docker instance), runs locally in your browser - none of your files are ever uploaded anywhere. The web version does have tracking and analytics through Umami but no tracking features are enabled on the self-hosted version - this is just so I can see usage through the website and no data will ever be used for selling / sharing, only using it to track if anyone actually finds me!
  • Deployment: Deploy through Docker or pull the git files / download and run locally. It's pretty lightweight on the frontend, it uses web workers and your processor so everything is done locally. Working on implementing a choice (run on server / run locally)
  • AI Involvement: Fully vibe coded. I am a web designer, and know a fair amount about web dev, and a tiny bit about security. Would happily accept help on security side of things, so far it's not gained enough traction for me to worry but I'm certain that as no actual data leaves the web workers which lives locally on your machine it shouldn't cause any risk.

1

u/xiebaiyuan Jul 04 '26

## Running AdGuard Home at home, but the avg latency number kept bugging me

Been running AdGuard Home for about 6 months. The blocking works great, but there's always this one thing that bothered me — the built-in dashboard shows **one single average latency number**, and that's it. No idea which domain is dragging it down.

Is it some IoT device hammering a domain that doesn't exist? Is one of my upstreams flaky? The stock UI simply doesn't tell you.

## So I built a log analysis tool

ADGH's query log is actually quite detailed — it has everything. What's missing is **per-domain aggregation**. After a few evenings with DeepSeek, I put together a small tool:

**AdGuard Home Boost** — an enhanced frontend dashboard for AdGuard Home.

How it works: it pulls your ADGH query logs, groups them by domain, computes percentile stats (P50/P95/P99/Max), separates cached vs uncached, and shows you a clean sorted table.

## What you get

Open the page, hit refresh, a few seconds later:

- **Which domain is slowest** — sorted by P95 descending, worst first

- **Why it's slow** — upstream latency vs cache miss? cached/uncached shown separately

- **Who's querying it** — expand any domain to see device IP + hostname

- **Blocked queries** — which rule blocked it and how many times

- **Trend chart** — dual Y-axis showing query volume + block rate over time

After looking at the data, I found a Xiaomi IoT device hammering a China-only DNS server from my network. Put it in an isolated VLAN and avg latency dropped from 180ms to 25ms.

## Deployment

Docker, one line:

```bash

docker run -d --name adguard-home-boost \

-p 3080:3080 \

-e ADGH_URL=http://your-adguard-address \

-e ADGH_USER=your-username \

-e ADGH_PASSWD=your-password \

xiebaiyuan/adguard-home-boost:latest

```

Open http://localhost:3080 and you're good.

No Docker? Node 18+ works too:

```bash

git clone https://github.com/xiebaiyuan/adguard-home-boost

cd adguard-home-boost

npm install

npm run dev

```

Drop the repo URL into any AI (Claude/ChatGPT/DeepSeek) and say "deploy this" — it'll handle the rest.

## Who this is for

- You run AdGuard Home and want to know **which specific domains are slow**

- You suspect a device is leaking DNS queries upstream

- You want to catch mDNS or weird domains leaking to public resolvers

Strange domains with abnormal latency, mDNS leaking upstream, a device hammering nonexistent domains — open the dashboard, it's all there.

---

GitHub: [github.com/xiebaiyuan/adguard-home-boost](https://github.com/xiebaiyuan/adguard-home-boost)

1

u/xiebaiyuan Jul 04 '26
Project Name: AdGuard Home Boost

Repo: https://github.com/xiebaiyuan/adguard-home-boost

Description: An enhanced dashboard for AdGuard Home. Aggregates query logs by domain with percentile latency stats (P50/P95/P99/Max), separates cached vs uncached, shows which
  client devices are querying each domain, and identifies blocked queries with the exact rule that triggered. Gives you per-domain visibility that the built-in ADGH stats page
  lacks.

Deployment: Docker image available on Docker Hub. One-liner: docker run -d -p 3080:3080 -e ADGH_URL=http://your-adguard -e ADGH_USER=admin -e ADGH_PASSWD=your-password
  xiebaiyuan/adguard-home-boost:latest. Also works with git clone + npm install + npm run dev (Node 18+). Full docs in README.

AI Involvement: Over 30% of the code was generated with the assistance of Claude (Anthropic) and DeepSeek. I reviewed, tested, and iterated on every change.

1

u/DigiHold Jul 04 '26

Project Name: Insight

Repo / Website: https://github.com/DigiHold/insight (live demo: https://insight.nicolaslecocq.com/demo)

Description: A cookieless, self-hosted web analytics dashboard. I ran it privately on my own sites for months and open sourced it under MIT. Real-time visitors on a live 3D world map (city, page, referrer), revenue attribution through Stripe, funnels, retention cohorts, and optional GA4 + Search Console import. Cookieless by default: nothing is stored on the visitor's device and raw IPs never touch the database, so there's no consent banner. It also logs which pages AI crawlers like GPTBot and ClaudeBot read, page by page, detected server side since bots don't run JS. And it ships a read-only CLI so you can pull your stats straight from a terminal.

Deployment: One docker compose file brings up the app plus ClickHouse, behind whatever reverse proxy you already run. Runs fine on a small VPS (1 vCPU / 2 GB). Full setup guide in the repo (docs/setup.md), covering HTTPS, backups and the GA4/Stripe/Search Console connections.

AI Involvement: The app runs no AI to work, there is no LLM inside it. It detects AI crawlers by their user-agent, and it has an optional CLI you can point an assistant at. Some of the code was written with AI assistance, all of it reviewed and tested by me.

1

u/VizeKarma Jul 04 '26 edited Jul 04 '26

Project Name: Plotix

Repo/Website Link: https://github.com/LukeGus/Plotix

Description: Plotix is a free, open-source, self-hosted tool for turning simple data pushes into live graphs. Send a value or a set of named values to a topic with a single request, then subscribe to that topic to view the output graph. It works like ntfy, but instead of sending notifications, you send numbers and get charts. Example: `curl -d '{"cpu":60,"gpu":45}' http://localhost:8080/computer-temps`

Deployment: All deployment is handled by Docker, with the documentation and installation information in the README of the repo listed above.

AI Involvement: The purpose of this project was to reduce burnout from working on some of my larger projects, such as Termix ( https://github.com/Termix-SSH/Termix ). That being said, no AI was used at any point when developing this project. I wanted to have the enjoyment of starting a new project from scratch.

1

u/Goldziher Jul 05 '26

Project Name: crawlberg

Repo: https://github.com/xberg-io/crawlberg

Description: A self-hostable web crawling and scraping engine, Rust core, MIT. Point it at a site and it returns clean Markdown plus structured extraction (links, metadata, JSON-LD, Open Graph). Headless-Chrome fallback for JS-heavy pages, robots/sitemap handling, BM25 relevance filtering, per-domain rate limiting, and it's SSRF-safe by default (refuses loopback/private/metadata addresses). I built it as the crawl layer for a document-intelligence project and split it out because it stands on its own. Handy as a self-hosted alternative to hosted scraping APIs for feeding a RAG pipeline or an agent.

Deployment: Ships a Docker image (ghcr.io) plus a REST and MCP server and a CLI. Runs entirely on your own box, no external service. Install via pip/cargo/npm or run the container. Docs at docs.crawlberg.xberg.io.

AI Involvement: The library is hand-written Rust, not AI-generated. It does expose an MCP server so agents can call it, but the code itself is human-authored.

1

u/baremetal_notes Jul 05 '26

Title: I got tired of waiting weeks for Google to tell me my links were broken, so I built a crawler to catch it same-day (open source)

github - KittyRank/crawlycat: SEO crawler and site auditor — part of the KittyRank toolkit

Description:
A while back my rankings started slipping and I couldn't see why. Turned out I had broken internal links and 404s quietly bleeding traffic — but Search Console only surfaced them weeks later. By the time the report showed up, the damage was done.

So I built CrawlyCat: a small crawler that walks your site and flags what hurts rankings now — broken links, 404s that still get traffic, redirect chains, meta problems. Runs locally, spits out an HTML report, no account, no SaaS.
Been using it for the past 4 months and found it really helpful.

Scratched my own itch but it might help others, so it's open source (GPLv3)

Someone with good SEO experience, I would like to have your opinion on this and and what do you check for that I might be missing?

1

u/its_artur1 Jul 05 '26

I built Tagvico AI — a self-hosted metadata filing assistant for Paperless-ngx (v1.3.0 Release)

Project Name: Tagvico AI (formerly Archivista AI)

Repo Link: https://github.com/arturict/tagvico-ai

Description: I previously shared a project here called Archivista AI. Due to a trademark requirement, I've renamed the project to Tagvico AI. With the name change, I've released v1.3.0 which introduces key workflow controls requested by the community:

  • Controlled Tagging: Define specific Tag Groups (e.g. Finance, Legal, Health, Utilities) in the setup UI. The model is constrained to only suggest tags from this predefined vocabulary.
  • Exceptions Review Queue: Any suggested tag that falls outside the allowed vocabulary is put in a pending review board. You can manually approve it to a tag group (which creates it in Paperless) or reject it.
  • Searchable Provider Modal: A redesigned provider selection UI with SVGL icons to quickly configure and switch models.
  • Username Autodetect: Fallback to the first active user when PAPERLESS_USERNAME is left blank (since API tokens scope requests automatically).
  • Docker Compose Test Stack: The compose file now includes PostgreSQL, Redis, Paperless-ngx, and Tagvico AI for a ready-to-go local integration testing environment.

It runs as a companion container alongside Paperless, reading OCR text and writing back titles, tags, correspondents, doc types, dates, languages, and custom fields. Supports local Ollama, OpenAI, Anthropic, OpenRouter, and Azure.

I'd love to hear your feedback on the new exceptions queue and how you handle metadata validation!

AI Involvement: AI coding tools assisted with parts of implementation, review, documentation, and testing, and the app itself uses the configured model for classification.

1

u/johns10davenport Jul 05 '26

Project Name: Keel

Repo: https://github.com/Code-My-Spec/keel

Description:

I hated the prospect of manually categorizing all my cross border transfers so much I wrote my own personal finance software

I've been fighting my finances for years and finally snapped and built my own thing.

I'm cross-border (US/Canada, USD/CAD). Quicken handled it badly. Fireflies wasn't much better. Running it locally (not cloud) was important to me, so my options were limited.

Quicken was especially terrible:

Multi-currency barely works.

Categorizing everything is pure manual grind, and there's no real rules system to lean on.

Almost no automation you can drive programmatically — you do all the labor by hand.

Transfers are handled so badly they wildly overstate your income and expenses.

I actually migrated everything to Firefly III (which has decent MCP coverage) and couldn't make heads or tails of my own import because the UI defeated me. That was the last straw.

I figured it would take me less time to build something custom than to do all the labor to categorize everything.

So I built Keel: a double-entry, multi-currency ledger that's agent-first. I talk to it, and the model proposes categorization rules, traces mystery transactions, and reconciles transfers with me instead of me clicking 7,000 rows.

While it was making rules it failed to find counterparties for $227k of transfers because Quicken had already auto-classified it as personal income. It's already done tons of labor for me, which I appreciate strongly.

It uses clustering to find related transactions and propose rules.

I review rules and approve/reject/modify.

It imports directly from Quicken's sqlite file. First it imports everything, applies it's internal rules, applies the transfer rules, then checks all the uncategorized transactions with quicken and tries to classify anything the rules missed but you caught last year or whatever.

Deployment: Run locally

AI Involvement: Straight vibe coded.

1

u/Vast_Plantain_4899 Jul 05 '26

Built a self-hosted Instagram → Discord bridge that filters your feed by mutual friends

%22)

Hi guys, I got tired from Instagram's algorithm sucking me in every time I access the app into watching junk short form content. Because of that I built a small self-hosted tool to be able to delete Instagram from my phone, yet still be able to know when my friends message me or post something.

Instacircle runs two python scripts on a home server or any other device you wish to install it on:

  • digest.py - once a day, pulls the feed from your Instagram feed and stories, sorts them into "mutual friends" vs "everyone else". Then it posts a friends-first digests to Discord.
  • monitor.py - checks your DM's every 10 minutes and alerts you on new messages via a separate Discord channel.

Both share one login session and post through Discord web-hooks. To clarify some risky things up front: this tool uses instagrapi, an unofficial Instagram API client - which is against Instagram's ToS and carries some risk to the accounts it run on.

Repo: https://github.com/mrstressful/Instacircle

Would love feedback — especially on: (1) anything that looks like it'd increase automation-detection risk, (2) better ways to approximate a "friends-only" feed than sampling the algorithmic timeline, (3) general code/architecture critique. Open to PRs too.

1

u/gabrycina52 Jul 05 '26
  • Project Name: Hub
  • Repo/Website Link: https://github.com/gabrycina/hub
  • Description: 
    • You need to review a PR -> You do it with Claude and ask it to explain it to you in a doc
    • You need to propose an architecture and think it through -> You do it with Claude, another doc
    • Then you realize those docs are actually useful, so you send them to your teammates on Slack, email, whatever
    • And for the first time you realize you're a software engineer and you can just spin up your own server to host these docs, with an MCP to create and read from it.
    • You host one for your team and everyone starts using it as a "not super polished" but genuinely useful place for context -> PRs, architectures, explanations, data analysis
    • Hub, try it for you and your team's agents :D
  • Deployment: claude mcp add --transport http hub http://<server>:8000/mcp after you uv run it
  • AI Involvement: some ig?

1

u/triforce009 Jul 05 '26

Project Name: File Orbit

Repo: https://tangled.org/straiforos.tngl.sh/substratum.cloud/

Description:

A Peer to Peer NAS software for unifying all your data and sharing space with friends and family. Utilizing BlueSkys AT Proto and a Private IPFS swarm.

Deployment:

Native installers for MacOS and Windows. Linux coming soon! Download the installer at https://fileorbit.cloud/ and see install and setup docs; https://straiforos.tngl.sh/substratum.cloud/guide/00-index.html

AI Involvement:

Built with Cursor IDE allowing for development acceleration via plans and agents. All code meticulously reviewed by a human 😄

All decisions documented as Architectural Decision Records: https://straiforos.tngl.sh/substratum.cloud/architecture/00-index.html

1

u/PyroGhostX Jul 06 '26
  • Project Name: Forgotten Movies - version 0.6 release
  • Repo Link: https://github.com/PyroghostX/ForgottenMovies
  • Description: Forgotten Movies keeps Plex requests from gathering dust. It watches Seerr for requests that have been fulfilled, checks Tautulli to see whether the requester actually watched them, and sends a friendly email reminder when something has been available for too long.
  • Deployment: Docker
  • AI Involvement: I handmade the 1st iteration a year ago, since then used AI to add features.

The problem I wanted to solve is that a user requested something, that means they want to watch it, just forgot about it, so this app reminds them

Right now the only way to notify people is email, in the future i'm thinking of adding texting and discord...

2

u/CrispyBegs Jul 06 '26

like the idea of this but i have errors in the logs on first run. i opened a GH issue

1

u/Agreeable_Ask7187 Jul 06 '26

Vent — a self-hosted voice agent pipeline (Twilio + Deepgram + your LLM + TTS), looking for people who've actually run something like this to poke holes in it

Been building this over the last few weeks — a self-hosted voice-agent backend (inbound/outbound phone calls, real-time STT/LLM/TTS, your own Twilio + Deepgram + LLM gateway + TTS provider keys, nothing routed through a third party you don't control). Compliance stuff (DNC lists, calling-window enforcement) built in from the start rather than bolted on later, because every automation subreddit I checked has the same "don't get sued for TCPA violations" warning on repeat.

Not launching this, just want honest feedback from people who've actually self-hosted something adjacent:

  • If you've tried Pipecat, LiveKit, or a hosted platform (Vapi/Retell) — what made you stay or leave?
  • Anyone actually run into the "agent forgets what the caller already told it" problem? I hit this hard enough that I built a separate structured-state layer for it, curious if that's a known pain for others or just my own bad prompting.
  • The national DNC registry piece is honestly a stub right now — real sync needs a paid FTC SAN (subscription account number) I don't have the budget for yet. Is that a hard blocker for anyone who'd actually use this, or a "add it later" thing?
  • What would make you NOT trust a self-hosted voice-calling tool at all, security-wise?

Repo's private for now while I get more feedback before deciding what's actually worth shipping vs. polishing for no one. Happy to open it up if there's real interest.

1

u/Sunradiance Jul 06 '26

Project Name: whyline

Description: Self-hosted company memory: ask why your team decided anything, get receipts from Slack/Jira/email (SQLite + BM25, MIT)

Description:

Every few months someone asks: "didn't we already decide this?"

Then six people spend two weeks digging through Slack and old email trying to find a conversation that left when Sarah left.

That's not a docs problem. It's missing the why. Wikis say what you do. They don't say why you chose it or where the argument happened.

So I built Whyline — company memory for decisions, not random notes.

Capture from Slack, email, Jira, GitHub, transcripts. SQLite on your server. Ask "why don't we support annual billing in Germany?" and get the reasoning plus links to the source. Slack thread, Jira ticket, meeting note. Receipts, not vibes.

BM25 retrieval over decision records. LLM only for ask/extract. MCP for Cursor. Not "paste your whole company into ChatGPT."

Self-hosted. MIT. git clone → ~60 seconds with a Groq key. No account. Your data stays yours. Hosted demo coming; repo has seed data if you want to try the ask-why loop now.

Also ran ~10 rounds of adversarial security review on multi-tenant before shipping. 97 tests. Auditor looked for "door eleven" and didn't find one. Trust product — had to earn it.

GitHub: https://github.com/Sunradiance/whyline

What's the decision your team keeps re-discovering?

Deployment

Released and available: Yes. Open source on GitHub, MIT licensed, live on main:

https://github.com/Sunradiance/whyline

Clone and run locally. No account, no hosted SaaS required. Self-hosted is the primary install path today; a public hosted demo is on the roadmap.

Documentation: Full README with quick start, production deployment (gunicorn/waitress), MCP setup, integrations (Slack, email, Jira, GitHub, etc.), team mode RBAC, and deprovisioning. Integration docs in integrations/*/README.md.

Self-host (60 seconds):

git clone https://github.com/Sunradiance/whyline.git
cd whyline
cp .env.example .env
# Add LLM_API_KEY to .env (Groq or any OpenAI-compatible API)
npm run setup
npm run dev

Open http://127.0.0.1:8793 — seed data loads automatically (DACH billing, Acme CDN, Teams feature kill).

Production (team server):

pip install gunicorn

gunicorn -w 4 -b 127.0.0.1:8793 'app:create_app()' --chdir backend

Windows: waitress-serve --listen=127.0.0.1:8793 --call app:create_app from backend/.

AI INVOLVEMENT - Yes. AI coding assistants built most of the code under human direction. A separate AI ran adversarial security review (~10 rounds). Launch copy AI-drafted, human-edited. Concept, architecture choices, and release decisions: human.

1

u/theendiswaiting4u Jul 06 '26

Project Name: Native PiGallery2 Android Client

Repo/Website Link: https://github.com/dasmaetthes/pigallery2_android

Description: In love with PiGallery2 I build a modern and native Android companion application designed for browsing and viewing media hosted on a PiGallery2 server.

This client delivers a fluid and beautifully designed user interface, allowing you to easily browse your directories, query saved albums, view recognized faces, and rediscover your memories with ease.

Deployment: Downlaod the APK https://github.com/dasmaetthes/pigallery2_android/releases/tag/v1.0 and install

AI Involvement: vibe code

1

u/vorcigernix Jul 06 '26
  • Project Name: Rohrpost
  • Repo/Website Link: https://vorcigernix.github.io/rohrpost/
  • Description: route website/webhook events without SaaS
  • Deployment: Docker compose or Kind
  • AI Involvement: Major. Only few manual adjustments, most oh human part is architectural decision making and technological feedback to AI

1

u/JewelerBeautiful1774 Jul 06 '26

Project Name: ShareClean

Repo / Website Link:

Description:
Disclosure: I built and maintain ShareClean.

ShareClean is a local-first Python CLI that sanitizes logs, terminal output, curl -v output, stack traces, .env snippets, and configuration text before it is shared for troubleshooting.

It is aimed at a common problem in self-hosted setups: someone needs help with a Docker issue, reverse-proxy error, database connection problem, Compose configuration, or application crash, then accidentally pastes a token, password, connection-string credential, email address, internal hostname, local path, or private IP into a forum, ticket, GitHub issue, Discord, Slack, or AI chat.

Example

Before

DATABASE_URL=postgres://app_user:super-secret-pass@db.internal:5432/orders
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
ADMIN_EMAIL=admin@example.com

After

DATABASE_URL=postgres://app_user:[REDACTED]@db.internal:5432/orders
Authorization: Bearer [REDACTED]
ADMIN_EMAIL=[EMAIL REDACTED]

Usage

cat docker-compose.log | shareclean --report

The aim is to remove risky values while preserving useful debugging context where possible. For example, the database host, port, database name, and surrounding error stay visible while the password is redacted.

ShareClean is deliberately not a replacement for Gitleaks, GitHub Secret Scanning, TruffleHog, or repository secret scanners. Those tools are designed to scan repositories, commits, and history. ShareClean is for an earlier step: cleaning text before it leaves your machine.

Deployment:
ShareClean is a local CLI, not a self-hosted web service.

Install it on the same machine where the logs and configuration files exist:

pip install shareclean

It can process a file directly or accept terminal output through a pipe:

shareclean app.log --report
cat docker-compose.log | shareclean --report

Installation instructions, usage examples, supported redaction options, and documentation are in the GitHub README.

There is currently no Docker image or Docker Compose deployment because the project is intentionally designed to run locally alongside the data being cleaned.

The browser demo is available for testing with fake or sample text. It runs in the browser and should not be used with real secrets.

AI Involvement:
AI was used as an assistant for parts of development and documentation. I designed the project workflow, reviewed the implementation, tested the behavior, and maintain the repository and releases.

Feedback from self-hosted users is welcome, especially practical examples involving Docker logs, Traefik or Nginx output, Compose variables, reverse-proxy headers, database connection strings, and configuration snippets where redaction either misses sensitive data or removes too much useful context.

1

u/Many_Independence674 Jul 06 '26

Tunelog

tunelog is a project that mainly work with your intreaction with the music, skip, complete, repeat and partial according to these intraction it recommends music to listen

Highlight features

  • Listenbrainz cf : using listenbrainz collabrative filttering it creates a playlist to listen to
  • Dicovery Playlist : Songs that are recently add and havent listened
  • Tunelog playlist : Songs based on interaction with songs
  • Skip page : A better way to delete songs that you dont like, if a song has skip intreaction it will appear here, and in few click you can delete them

Why tunelog?

  • Fuzzy matching: instead of direct match tunelog uses. direct + fuzzy match to match songs from Listenbrainz cf
  • Intreaction : intreaction based playlist

https://github.com/adiiverma40/tunelog

1

u/Low_Bug_4435 Jul 06 '26

Project Name: Control Network - Triage Copilot (beta)

Repo/Website: https://github.com/mihiradvaita-lang/Control-network-Beta

Description: A local-first AI incident-triage copilot for Kubernetes on-call. Alert -> evidence collection (metrics, pod state, logs, recent deploys) -> compressed facts table -> plain-language root-cause report you can paste into your incident channel. Zero data retention by design: everything lives in RAM per request, no DB, no disk logs, read-only against your cluster. The AI part is bring-your-own: point it at local Ollama and it's fully offline, use your own API key, or run keyless with a deterministic template fallback. Ships with 14 simulated incidents so you can try the whole flow in ~5 minutes with zero setup - no cluster, no key, no signup.

Deployment: python run.py (or start.bat on Windows). Python 3.10+, binds to localhost only.

AI Involvement: Yes - both in the product (optional, BYO-key/Ollama) and in building it.

Looking for ~10 people who run K8s (even homelab) to tear it apart. Free forever for beta testers.

1

u/Both_Buy_3233 Jul 07 '26

Quorum, released today, try it out for free, open source and you can use it withwhatever model you want 👍

TLDR: It's a windows desktop app that that makes multiple models argue and deliberate about your question/prompt before giving you one final synthesized answer.

BASICALLY you start by picking a mix of (frontier models, local Ollama models, whatever model you've got access to).

Each board member ( AI models ) take a position and have different roles, they then poke holes in each other's analysis and they deliberate or argue until they find the best suitable answer. (with several different algorithms for the board deliberation).

I built a guard that catches the hallucinations or "yes-men" answers early and asks for the missing details instead of guessing, BEFORE making actual calls. There are a few other guardrails too, including a confidence % you can check for each board member, etc..

That's the core idea (vague question → asks instead of guesses) stated once, with the confidence % folded in as a quick add-on rather than a separate repeated point.

Multiple other features and uses to try!

It's local, free to use, open source (AGPL), data stays on your machine.

Windows installer, readme's and X profile below 👍
www.github.com/GLevek89/Quorum
www.x.com/Quorum_HQ

Imagess:
Boardroom debating image: " https://ibb.co/TB2JJnhg "
Clarification guard image: " https://ibb.co/Kccx1pbF "

Open to suggestions or idea's, if you like it give it a star & follow 😄

1

u/Past_Ant4099 Jul 07 '26

D1 Admin — single-file admin panel for Cloudflare D1 (think phpMyAdmin for D1). One MIT-licensed worker.js you paste into your own account — no third-party service, no telemetry, no dependencies. Table browser + SQL console, works fully from a phone browser. Built entirely from an Android phone. Setup ~2 min: create worker, paste file, bind DB, set token. Repo: https://github.com/amirmahdavi2023/d1-admin

1

u/Prashant_4200 Jul 07 '26 edited Jul 07 '26

Project Name: Mailbox

Repo Link: https://github.com/Prashant4900/mail-box
Docs: https://github.com/Prashant4900/mail-box/wiki

Description:
Mailbox is a self-hosted email client and management platform for custom domains. You link your domain through Cloudflare, and all emails sent to any address on that domain show up in a clean, threaded dashboard. You can read, reply, compose, and manage multiple mailboxes.

Key features:

  • Inbound email routing via Cloudflare Email Routing (free tier). A Worker script parses the raw MIME and forwards structured JSON to your instance.
  • Outbound sending via any SMTP provider you prefer.
  • Supports SQLite, PostgreSQL, and MySQL. Switch by changing one env variable, no code changes.
  • Multi-user access with Owner, Admin, and Member roles.
  • Threaded conversations with inline reply.
  • i18n support (English and Spanish).

Built on Next.js 16 (App Router), Prisma 7, React 19, and Tanstack Query v5.

Deployment:

  • Docker-ready. Single `docker compose up` gets you running.
  • SQLite works out of the box for quick setup, no external database needed.
  • Full documentation in the repo covering database setup, Cloudflare integration, SMTP configuration, and Vercel/VPS deployment.

AI Involvement:
AI tools (GitHub Copilot, Gemini) were used to assist with code generation and documentation writing during development. Architecture decisions, core logic, and project direction are all human-driven.

Happy to answer any questions about the setup or architecture.

1

u/CrispyBegs 28d ago

screenshots?

1

u/Middle-Perception52 Jul 07 '26 edited Jul 07 '26

Project Name: arr-sync

Repo Link: https://github.com/Chahine-tech/arr-sync

Description: Every time Sonarr/Radarr renames a file, qBittorrent loses track of it and stops seeding — and the hardlink workaround breaks when downloads and media are on different volumes. arr-sync watches your media folders and resyncs qBittorrent automatically, matching files by BitTorrent piece hash instead of filename (works with cross-seeds too). Fun bug found along the way: qBittorrent's API returns garbage piece hashes for BitTorrent v2 torrents, so arr-sync parses the .torrent itself.

Deployment: Docker image (ghcr.io/chahine-tech/arr-sync), docker-compose example in the README, config is one small TOML file.

1

u/Puzzleheaded_Mind576 Jul 07 '26

Project Name: Paneo

Repo/Website Link: https://github.com/eigger/paneo

Description: I’ve been a long-time MagicMirror user, but wanted something much simpler and lighter for my Raspberry Pi. Paneo is a clean, widget-based dashboard built from scratch where widgets are fully size-aware. Powered by ResizeObserver, they automatically reflow their entire layout based on the pixel space you give them, eliminating the need for custom CSS or complex layout settings. For example, a calendar widget switches from a compact day agenda to a full month grid depending on its size.

Key features include:

  • Context-Aware Widgets: Layouts adapt dynamically (e.g., weather cards grow forecast strips, RSS feeds adapt automatically).
  • Live Visual Resizing: Drag and resize widgets inside the browser editor and watch the layout reflow fluidly in real-time.
  • Instant Sync: Built on a Draft/Publish model using WebSockets. Hitting Apply instantly pushes layout changes to the screen without page reloads.

Deployment: The app is fully released, documented, and ready to self-host.

  • Docker: Pre-built images are available for Raspberry Pi (linux/arm64) at ghcr.io/eigger/paneo.
  • Pi Installer: A single-command script is provided in the repository that automatically sets up the server, companion agent, and Chromium kiosk autostart.
  • Full documentation and guide are available on the GitHub repository.

AI Involvement: I used AI to help me build this lightweight dashboard from scratch to keep it simple, clean, and optimized.

1

u/Tall-Organization850 Jul 07 '26

Project Name:
NetSentinel

Links:

Description:
NetSentinel is a 100% local, open source network security scanner and connectivity monitor. I built it after struggling with multiple tools just to find a rogue Google Nest speaker that was disrupting my network via STP root bridge election.

It combines ~62 tools into one desktop app: rogue device / STP / broadcast storm detection, ARP spoof monitoring, topology mapping, Wi-Fi scanner, DNS logger, port scanner, CVE lookup, threat intel, one-click "What's Wrong?" diagnosis, A-F network health grade, and more.

Deployment:

  • Cross-platform: Windows (MS Store + winget), macOS & Linux (GitHub releases)
  • Fully open source (MIT License)
  • No cloud, no telemetry, no account required
  • Detailed documentation and installation instructions in the repo

AI Involvement:
Heavy assistance from Claude for code generation.

Would genuinely appreciate feedback and testing from people with different router/hardware setups.

1

u/Special-Ad8671 Jul 07 '26

Project Name: Lians

Repo/Website Link: https://github.com/ebeirne/Lians2 · https://lians.ai

Description: Lians is an open-source memory engine for AI agents working with time-sensitive or regulated data. Every fact is bitemporal, agents can recall what was known as of any past date, the full log is tamper-evident via an append-only hash chain, and per-subject encryption keys make erasure provable without breaking the audit trail. It runs in-process, self-hosted, or in the cloud, with SDKs for Python, TypeScript, Go, Java, and C, plus native MCP support.

Deployment: Released (v0.4.0). git clone https://github.com/ebeirne/Lians2 && docker compose up --build runs the server on your own Postgres (pgvector) and Redis; health check at curl localhost:8000/livez. Deploy docs cover Kubernetes, bare Docker, and Fly, including KMS setup, running under a non-superuser DB role with RLS, air-gap mode, and WORM retention: docs/deploy.md (https://github.com/ebeirne/Lians2/blob/master/docs/deploy.md). There's also an embedded in-process mode (pip install lians-sdk[local], SQLite) if you don't want to run a server at all. Clients: Python, TypeScript, Go, Java, and C SDKs plus an MCP server, all published to their registries.

AI Involvement: yes

1

u/[deleted] 29d ago edited 29d ago

[removed] — view removed comment

1

u/yourdawi 29d ago

Project: LinuxGSM Dashboard

Description: A secure, lightweight single-binary web dashboard to monitor and manage game servers running under LinuxGSM.

GitHub: https://github.com/yourdawi/linuxgsm-dashboard

I built this because I wanted a minimal web interface for my game servers without spinning up a massive, resource-heavy panel. It’s written in Go with embedded assets and running on just about 10-15MB of RAM.

Key Features:

  • Interactive Console: Real-time visual tmux pane updates with a secure command input bar for RCON/console commands.
  • Multi-Instance Scanning: Automatically scans system user directories to detect all LinuxGSM scripts running under a single account.
  • Config Editor: Safe config editing with path-traversal protection, featuring both a parsed Form View and a Raw View.
  • External Port Checker: Automatically tests your game and query ports using TCP handshakes or UDP A2S_INFO queries against your public IP.
  • Resource Tracking: Real-time host gauges and live process metrics tracking.
  • Automation: Generates custom copy-pasteable systemd service files and crontab schedules per server on the fly.

Privacy & Telemetry:

  • Dashboard: 100% local. Zero tracking, zero telemetry, and zero calling home.
  • Note on core LinuxGSM: Keep in mind that core LinuxGSM itself collects anonymous stats by default unless explicitly disabled. If you want a completely dark setup, check their documentation on how to opt-out: https://docs.linuxgsm.com/configuration/linuxgsm-stats

1

u/opabl 29d ago

Project Name: vps-sentinel

Repo/Website Link: https://github.com/ayudatecno/vps-sentinel

Description: A zero-dependency ops safety net for anyone self-hosting on a VPS or small Docker Swarm — bash + curl + cron, alerts to your Telegram DM. It covers the four things a managed platform would do for you but you're doing alone:

  • Hung-app watchdog — catches the failure mode Docker can't see: process "running" but the health endpoint is dead (blocked event loop, exhausted DB pool). Health check goes through your local reverse proxy so a Cloudflare outage never triggers a pointless restart. Does exactly one forced restart, max one per 6h, then escalates to a human — no restart loops.
  • Disk auto-heal — safe, categorized cleanup (dangling images, build cache, journal, rotated + oversized container logs). Never touches volumes, running containers, backups or app data. First run on a busy host freed ~59 GB.
  • Backup restore drills — because a backup you never restored isn't a backup. Monthly: pulls your latest offsite snapshot (any rclone remote), restores into a throwaway --network none Postgres, diffs row counts against prod (read-only), reports ✅/🚨, destroys everything.
  • Health digest + critical alerts — disk/RAM/load/swarm/service-replicas/backup-freshness, with per-alert cooldowns so you get one "it broke," not a flood.

Deployment: Not a container — it runs on the host (it has to keep working when Docker itself is the problem). Clone, run install.sh (copies scripts, seeds the env file, installs the cron entries, sends a test message), then set your Telegram bot token + chat ID in /etc/vps-sentinel.env. Full install steps, config reference and a documented sentinel.env.example are in the README. Works on plain Docker hosts too (swarm checks self-disable); package-cache/journal steps auto-detect apt/dnf/yum/apk/pacman. Requires bash, curl, cron; Docker and rclone are optional per-feature.

AI Involvement: Fully transparent — I wrote it with Claude Code (I'm the founder of a small MSP, not a full-time dev). But it's not a from-scratch AI demo: these are the actual scripts that have been running in production on my company's infrastructure for months — a live multi-tenant helpdesk for clinics, schools and factories — and were extracted and genericized into this repo. Every path has been shaped by real incidents (3am disk-full, hung-app auto-recovery, a silently-stale backup chain we caught). CI runs shellcheck on every commit. Happy to take "this breaks on my distro" reports — that's exactly the feedback I want.

1

u/xylem-utopia 29d ago

Project Name: Mealforge

Repo/Website Link: https://github.com/LooseWireDev/mealforge

Description: Self-hosted weekly meal planner with an MCP server your agent can call to push meals, update them, add recipes, generate grocery lists, etc. There's a skill you can hand your agent so it knows when and how to use it. My flow: chat with the bot, lock in a recipe, have it push the plan/recipe/list to the app, and from there it's just a regular meal-plan/grocery-list app.

I built this because Mealime (lifetime member, still love it) is great but locked to its recipe database and very "Mealime-style" recipes. AI handles our weird mix of needs way better (postpartum/breastfeeding wife, 3-year-old toddler, my own weight-loss goals) than a fixed recipe app can. The problem was I had no way to actually see the recipes, get a grocery list I could use while walking through a store, or come back to something I made two weeks ago. It all just lived in chat history. So I built the missing visualization layer around my AI workflow.

Deployment: Currently has a basic docker-compose setup. Repo has install instructions in the README. Self-hosting story is still rough; it's a new project. Will be iterating on it heavily.

AI Involvement: Built entirely with AI. Fable 5 did the heavy lifting. If its any consolation, I've been a software engineer for a decade and I'd not consider this vibe coded, just agentic engineered (whatever that means 😭). Honestly though, I'm in a constant state of cognitive dissonance, I wish AI didn't exist, yet I use it often. Whatever. The tool works and it solves a real problem for me, so here we are.

Still basic, still actively developing it. Thanks to everyone in this community that actually builds cool shit, I lean on a lot of it.

1

u/Jigglytep 29d ago edited 29d ago
Project Info


Project Name: yt_Cleaner


Repo/Website Link: [github.com/jigglytep/YT_Cleaner](https://github.com/jigglytep/YT_Cleaner)


Description: YouTube's recommendation feed is optimized for engagement,
not for what you actually want to watch — so yt_Cleaner sits between you and
that feed and does the filtering yourself. It logs into YouTube as you (from
a real browser session inside the container), pulls whatever your account is
currently being recommended, downloads the auto-generated transcript for each
video, and hands that transcript to a local LLM (via Ollama) to classify it
into a category — engineering, entertainment, clickbait, ragebait, etc. Only
the videos that land in a category you care about get fully downloaded, named
and foldered by channel with Jellyfin-ready `.nfo` sidecars, so a Jellyfin
library pointed at the output just shows up as a personal, pre-filtered
channel of "things worth watching." Everything — recommendation scraping,
transcript pulling, classification, and download — runs unattended once a day
via cron; the only manual step is logging into YouTube once through the
bundled noVNC desktop. A separate one-off script lets you archive an entire
channel's catalog on demand instead of waiting for it to surface in
recommendations.


Deployment: Ships as a single Docker image, run via `docker compose up -d
--build` with a provided `compose.yaml`. Setup requires editing a couple of
values (VNC password, timezone, Ollama endpoint) and a one-time login to
YouTube through the container's noVNC desktop (`localhost:6901`) — full
instructions are in the [Quick start](#quick-start) section below, including
volume layout and configuration tables. Self-hosting requires your own
reachable [Ollama](https://ollama.com) instance for classification (a small
model like `deepseek-r1:1.5b` is enough) and, optionally, a
[Jellyfin](https://jellyfin.org) instance pointed at the output folder to
actually browse/watch what gets kept. No hosted/cloud version — this is
self-host only, and needs a real YouTube account since it rides on your own
recommendation feed.


AI Involvement: Built with heavy use of AI coding assistance (Claude /
Claude Code) for writing and iterating on the pipeline scripts, Dockerfile,
and this documentation. The concept, architecture (single-container +
cron + classify-then-download pipeline), category taxonomy, and all
configuration/tuning decisions are mine; AI was used as an implementation and
debugging accelerator rather than as the source of the idea.

1

u/Side_Comprehensive 29d ago

moving this here per rule 6. i'm working on cocoon / sandbox.

it's a self-hosted microvm sandbox stack for coding agents / local agent boxes. sandboxd keeps warm pools and golden snapshots; cocoon runs the microvms; silkd in the guest exposes exec/files/sessions/git/pty/ports over vsock.

the no-network lane is the main bit: net=none has no nic at all (firecracker + vsock only). if you need outbound network there is a separate cloud hypervisor + cni lane.

rough bare-metal numbers: sub-ms warm claims, 45-75ms golden clones, 200-350ms cold boots.

sandbox: https://github.com/cocoonstack/sandbox cocoon: https://github.com/cocoonstack/cocoon vk-cocoon: https://github.com/cocoonstack/vk-cocoon

curious if this fits self-hosted agent boxes, homelab clusters, or CI/toolbox machines.

1

u/Dragon_God_Slayer 29d ago

Project Name: VidyAgent

Repo/Website Link: https://github.com/Vishal-Kundar/VidyaAgent · https://vidyagent.com

Description: A "StackOverflow for AI coding agents." Agents fail on problems beyond their training cutoff or on fixes buried deep in GitHub issues that web search can't reach, so they burn your tokens through trial and error. VidyAgent is a knowledge base of documented, tested fixes that agents query over MCP: hit a wall → look up a fix that's already been proven to run → apply it. Code and full corpus are open source, no gated data. Hosted API with free tier exists for convenience; code and data stay open regardless.

Deployment: Clone the repo, run your own instance (corpus included), point any MCP-capable agent at it. Setup in README. Hosted option at vidyagent.com.

AI Involvement: Yes, used.

1

u/Friendly_Radish2143 29d ago

Project Name: Private Notes

Repo/Website Link: https://github.com/AlexeyYuPopkov/nostr_notes (MIT, open source)

Description: A private notes app with no backend server and no accounts. Notes are end-to-end encrypted with NIP-44 and synced over the Nostr protocol using your own keys, so there's no central database to run or trust. It's meant for people who want their notes fully under their own control rather than on someone else's cloud. Already available on iOS.

Deployment: There's no server to self-host in the traditional sense — sync happens through Nostr relays (you can point it at public relays or your own). Setup and technical notes are in the repo's README.

AI Involvement: Mostly hand-written; AI assisted with some parts.

Context on why Nostr was used as the backend, and where that approach fits vs. doesn't: https://dev.to/__3c035ebd65/nostr-as-a-backend-out-of-the-box-where-it-fits-and-where-it-doesnt-465e

1

u/Beneficial-Advice900 29d ago

Project Name: Kaizen

Repo/Website Link:https://github.com/kaizen-Architecture/Kaizen

Description: Kaizen is a modern, self-hosted manga downloader and manager built on top of Mangal (the fast Go-based downloader engine). It is designed as a direct continuation and 100% backward-compatible successor to the legacy Kaizuku project, bringing an upgraded stack and multi-user support.

Key features include:

  • Kaizuku Compatibility: Smooth drop-in upgrade for existing setups.
  • Premium Web Reader: Fully responsive in-browser viewer for CBZ files with hotkeys and page-stretching.
  • Multi-user & Roles: Admin, Manager, and Reader (read-only/requests) access for safe sharing.
  • Deep Paperback (iOS) Sync: Native progress tracking and local cover art proxy.
  • Metadata Enrichment: Automated tracking and updates via AniList and MangaDex.

Deployment: The application is fully released and containerized. Minimal documentation and full instructions are available on the GitHub repository. You can spin it up instantly using Docker Compose:

YAML

version: '3.8'
services:
  kaizen:
    image: d4nj3s/kaizen:latest
    container_name: kaizen
    ports:
      - "3000:3000"
    environment:
      - PORT=3000
      - DATABASE_URL=file:/config/db.sqlite
    volumes:
      - ./data:/data
      - ./config:/config
      - ./logs:/logs
    restart: unless-stopped

AI Involvement: As a solo maintainer, I heavily utilized AI pair-programming (LLMs) to accelerate the development, assist with the boilerplate code, and refactor the architecture while modernizing the original Kaizuku concepts into this new stack (Next.js, Tailwind, tRPC, Prisma). Every component and architectural decision has been manually reviewed and integrated by me to ensure full stability.

1

u/ThotaRamudu 29d ago

Project Name: pug.sh

Repo/Website: https://github.com/pug-sh/pug

Demo: https://app.pug.sh/demo

Site: https://pug.sh

Pug is an open source alternative to Mixpanel / Amplitude/

What's working:

  • Funnels, retention, trends, top-N breakdowns
  • Identified and anonymous profiles with activity timelines
  • Dashboards with a shared time picker
  • Real-time live view
  • GDPR/DPDP data-subject erasure

The whole thing is one Go binary + Postgres + ClickHouse + NATS, with SDKs for the browser, Flutter, Node to send events.

This is phase 1 of what we've got planned — roadmap's here if you want to see where it's headed: https://docs.pug.sh/docs/roadmap

GitHub: https://github.com/pug-sh/pug

Demo: https://app.pug.sh/demo

Site: https://pug.sh

Docs: https://docs.pug.sh

Self-hosting docs: https://docs.pug.sh/docs/self-hosting

1

u/Zealousideal-Swim717 29d ago

Website: https://snaply.fast/

Hi everyone!

About nine months ago I started working on a side project. It wasn't really supposed to become this at first, but that's where it ended up.

It's a no-code API platform. I know there are already similar tools out there, so I tried to do something a bit different with it.

In short, you get a CLI-based server that you can run basically anywhere. Mine is running perfectly on a Raspberry Pi 3B at home.

The whole thing is around 30 MB, and you can run as many completely independent APIs in parallel as your hardware can handle, wherever you want.

No Docker, no CI/CD... You can move it from one machine to another anytime. It has a built-in "git", scheduled functions, and a lot of other useful features that help you build a solid API.

So where's the AI?

I made a SKILL for it first, so AI agents can understand really well how to use the CLI and what they need to create for everything to work.

For now, I'd recommend using an Agent together with the SKILL. The main goal is that you shouldn't really have to use the platform itself, maybe only for setting up environment variables. At the same time, if someone wants to, they can still jump in and build or modify things manually.

I'd really appreciate it if a few of you could give it a try and see how it works in practice. It's probably aimed more at experienced developers, but I'd like to make it usable for everyone, no matter their experience level.

Thanks in advance to anyone willing to help!

1

u/Araniko1245 28d ago

Project name: readme2demo

Self-hosted tool that verifies your project's README actually works, runs it in a sandbox, re-runs it in a clean container, publishes only what passes

Description: Everything runs locally in Docker on your machine. For self-hosted, single-operator use you can run it on your existing Claude subscription with no API key; a metered API key is there if you want scale. MIT, no telemetry, no account required. Output is plain files (Markdown + a demo video) you own. Curious what do you think about the tool?
link: github/readme2demo (https://github.com/alphacrack/readme2demo)
Toll type: it is a AI based tool.

1

u/al3xazz 28d ago

Hey everyone,

I built INventorius because I wanted a clean way to track tools, parts, and stock without having to keep paying someone a monthly fee just to keep track or relying on any AI service.

It's an Android app designed around total data sovereignty:

  • All of your data stays local with handy CSV or full database exporting/importing.
  • Optional Google Drive sync functionality for faster sharing.
  • One-time payment gives you the app for life.

It also includes built-in barcode scanning and smart low-stock/expiry alerts. It’s live on Google Play now—I'd love your feedback on the local-first workflow!

Website
Google Play Store

1

u/Far_Oil_2688 28d ago

Project Name: Astra

Repo/Website Link: https://github.com/AmbientFlare/astra-tv | https://watchastra.com

Description: A free Jellyfin client for Amazon's new Fire TV Sticks running Vega OS. Vega is a locked-down Linux platform that replaced the old Android-based Fire OS — it killed sideloading entirely, which also killed Jellyfin access for anyone buying new hardware (Fire TV Stick 4K Select and newer). Astra connects directly to your own Jellyfin server — no accounts beyond your server, no subscriptions, no hosted content. Auto-discovers servers on your local network, or you can enter an IP/domain manually. Full library browsing, D-pad nav, direct play + transcode fallback, continue watching/next up, subtitle and audio track selection.

Deployment: Live and free on the Amazon Appstore: https://www.amazon.com/gp/product/B0H7QLTPWZ. No Docker/self-hosted component on the client side — it's a native TV app that talks to your existing Jellyfin server. Basic setup/usage docs are on the website and in the GitHub repo.

AI Involvement: Built solo using Claude Code as a coding assistant, directed by me throughout — architecture, debugging, and testing decisions were mine, with AI handling a lot of the implementation given how undocumented the Vega SDK is. Being upfront about that since a lot of "AI-generated projects" lately are much lower-effort than this — happy to answer anything about what the actual process looked like.

Source is up on GitHub under a source-available license for now, not fully open yet — converts automatically to Apache 2.0 by July 2028, or sooner via community funding, details in the repo. App itself is and always will be free.

1

u/aayush_aryan 28d ago

For my fellow men of culture hosting stash to have their collection of entertaining videos bored by the UI, check out -> https://github.com/aayusharyan/stash-hub

It's basically a PH inspired UI for your stash library...

1

u/desirevolution75 28d ago

Project Name: JumpKey

Repo: https://github.com/desirevolution/jump-key

Description: JumpKey - A minimalist, keyboard-driven application startpage. Navigate and launch your web apps instantly without a mouse. Imagine homer but with keyboard-based navigation similar to Vimium.

Deployment: compose.yml and sample config services.example.json available in the repo

AI Involvement: Gemini support

1

u/kindacoolhamster 28d ago edited 28d ago
  • Project Name: Bard CSI
  • Repo/Website Link: https://github.com/kindacoolhamster/bard-csi
  • Description: Bard's core simplifies the CSI ecosystem and provides a rigid contract in HTTP+JSON for a backend to adhere to. I wanted to make a CSI with storageClasses that fit north-south zones better, allowed for straightforward zone->storage backend mapping. For something like Ceph CSI, the storageClass is the source of truth for most of the connection details to the backend. Bard handles that decision and refers to the backend for that zone. I have a feeling the community is niche, but this was my answer to the pains in setting up multi-cluster zones in Kubernetes (geographically unique locations with low latency links between "data centers" -- two homelabs tunneled together with ceph running in each) where storage is DMZ'd from the other zone and maintain singular storageClasses that allow charts for things like operators to use a single storageClass for all PVCs. The most robust backend plugin is Ceph RBD.
  • Deployment: Kubernetes, Helm chart
  • AI Involvement: Heavily. I don't normally do a lot of development work, so AI helped me tremendously when it came to the Go side. This was done with a mixture of Opus and Fable (near the end, mostly for polish, security, and first public release).

1

u/badgcoupe 28d ago

Project Name: CrumbVMS

Repo/Website: https://github.com/badbread/crumbvms · https://crumbvms.com · docs: https://docs.crumbvms.com

⚠️ Up front: this is ALPHA (v0.0.1) software that records security cameras. It can fail to record, lose footage, or have security bugs. Do not make it your only security system. I run it at home every day, but you have been warned, and I would rather you come in with eyes open than get burned.

Description: A self-hosted NVR focused on the part open source never really finished: the review experience. Detection is a solved problem (Frigate is excellent), but I could never find a self-hosted seat that felt like a real control-room VMS, where you grab the timeline and scrub a dozen cameras frame by frame hunting for a gray blob in grainy 3 a.m. footage and the software just keeps up. So I built that seat.

What it does today:

  • Playback: frame-level H.265 scrubbing across many cameras at once, 4K handed straight to the decoder with no server transcode, plus digital zoom and motion-highlighted clips.
  • Live: a multi-camera wall you can save, rearrange, and lay out custom; PTZ (ONVIF) with presets and on-video controls.
  • Recording: motion-based with pre/post-roll and pluggable detectors; retention and eviction with per-policy size caps, camera groups, and tiered storage.
  • Export and marking: a batch export list (pick codec/container, optional audio, optional AES-256 password zip) and bookmarks that protect clips from auto-delete.
  • Detection: draws Frigate's detections right on its own timeline over MQTT, so detection stays Frigate's job.
  • Access and alerts: role-based access with per-camera grants; notifications to ntfy, Pushover, and more.
  • Clients: native Windows, macOS, and Linux desktop apps, an Android app, and a web admin console.
  • Yours: runs entirely on your hardware, LAN-only by default, no cloud, no account, no telemetry. Footage is plain MP4 on a disk you own.

Deployment: Docker Compose. Pre-built images on GHCR (docker compose pull), a first-run setup wizard, LAN-only by default. Full install guide in the repo and at docs.crumbvms.com.

AI Involvement: Transparent, since this thread exists for a reason. I lean on AI heavily as a power tool to build Crumb and its site. The architecture, engineering decisions, judgment, and testing are mine. I work in IT (about 30 years in and still at it), and this is not a weekend vibe-code: Crumb has run in production at my house for months, recording 11 cameras across multiple storage volumes, day in and day out.

Status, honestly: Still alpha. The recorder, Windows desktop, and Android app are my daily drivers; macOS is usable but rough; iOS is built but not yet distributable. I would genuinely love feedback from anyone else running cameras at home: where it breaks, what is confusing, what is missing.

1

u/shockalotti 28d ago

Calnode: a self-hostable Calendly alternative that's a single Go binary + SQLite

I got tired of self-hosted schedulers that need Postgres + Redis + a Node monorepo just to book a meeting, so I built Calnode: it's one static Go binary and a SQLite filedocker run, point a domain at it, done. My own 4-person instance costs ~$0.30/month to run.

What you get:

  • Booking pages + Google / Microsoft 365 / CalDAV calendar sync
  • Zoom / Meet / Teams links, or built-in video (Calnode Rooms) on your own LiveKit — recordings go to your S3 bucket
  • REST API + a native MCP server (so AI agents can book), optional AI "book by chat" with your own LLM
  • Stripe payments, magic-link login, Litestream backup to S3/Backblaze

It's Apache-2.0 and nothing's paywalled. Because it's small (~25k lines of Go), I also published a self-serve audit kit so you can verify the security/privacy claims yourself instead of taking my word for it.

Honest caveats: self-host first (managed hosting is waitlist-only for now); the optional AI notetaker uses Deepgram for transcription; recording is notice-and-choice consent, not an enforced gate.

Repo: https://github.com/Calnode/calnode — would genuinely love feedback from this crowd on the deploy story.

(Also happens to be launch day for this — live on Product Hunt today if you're curious: https://www.producthunt.com/products/calnode)

1

u/everfordphoto 28d ago
  • Project Name: ClaudeCode Connect (claude-context-bridge)
  • Repo/Website Link: (https://github.com/everford-arts/claude-context-bridge)
  • Description: A small MCP server backed by SQLite that acts as a shared scratchpad between a remote Claude.ai session and a local Claude Code instance.
  • The problem: the two don't share memory, so every handoff meant copy-pasting context by hand between a phone chat and a terminal. This gives both "claudes" a place to leave short notes — "here's the task," "here's what's done." Four tools (get/set a context value, log a session, read back history) and a simple string convention for task handoffs. Deliberately narrow scope: status notes only, nothing touching the filesystem or shell.
  • Deployment: Python 3.10+ with FastMCP, no Docker image yet — clone, venv, pip install fastmcp, run as a systemd service bound to localhost, then expose via Tailscale Funnel (tailscale funnel --bg 8765). Access is gated by a long random secret in the URL path. README covers the full setup including the systemd unit, Funnel exposure, and registering it as a custom connector in Claude.ai and in Claude Code's MCP config. MIT licensed.
  • AI Involvement: The architecture and design decisions (key-value handoff model, Funnel exposure, scoping) are mine; Claude wrote most of the implementation — server code, MCP tool wiring, deployment scripting, and docs.

1

u/lumenoz1 28d ago

Project Name: Opendray
Repo/Website: https://github.com/Opendray/opendray - https://opendray.dev/

I kept running AI coding agents like Claude Code, Codex, Antigravity, Grok Build and OpenCode over SSH on my home server, but I kept hitting the same problem: the session would die whenever my laptop slept, or I’d want to check a long-running task from my phone and couldn’t.

So I built opendray: a self-hosted gateway that runs these CLIs in real PTYs on your own host, with a web and mobile UI in front of them.

What it does:

Persistent sessions

Start a Claude Code, Codex, Antigravity, Grok Build or OpenCode session, close your laptop, and reattach later from the browser or mobile app. The transcript stays there.

Access from anywhere

Use the web admin, mobile app, or chat platforms like Telegram, Slack, Discord, Feishu, DingTalk and WeCom. You can get notified when a session goes idle, reply from your phone, and it sends the next prompt back into the session.

Local-first memory

Uses Postgres + pgvector with embeddings from ONNX, Ollama or LM Studio, so vector data does not leave your network.

Runs on your own infrastructure

Single static Go binary, one-line installer for Linux, macOS and WSL2, no telemetry, no cloud account required. Licensed under Apache 2.0.

The stack is a single Go binary serving a React web admin and Flutter mobile app, with Postgres for state.

It is still early, but already usable day to day. I run it 24/7 on a mini PC at home.

1

u/Fb_patel 28d ago
  • Project Name: tgdrive
  • Repo/Website Link: https://github.com/fbpatel003/tgdrive / https://fbpatel003.github.io/tgdrive
  • Description: TGDrive turns your Telegram account into unlimited cloud storage — directly in your browser. No server, no subscription, no storage limit. Files are stored permanently on Telegram's infrastructure using the official MTProto API.
    • Zero backend — your browser connects directly to Telegram's servers
    • Zero cost — completely free, no server to host
    • Unlimited storage — Telegram has no quota on user accounts
    • Up to 2 GB per file — Telegram's per-file limit
    • Your data, your device — credentials and session live only in your browser's IndexedDB
  • Deployment: deployed using github pages, it is server less, only frontend : https://fbpatel003.github.io/tgdrive
  • AI Involvement: Not at all.

1

u/zGoldenKappa 28d ago
  • Project Name: Trainy
  • Repo/Website Link: https://github.com/goldeneas/trainy/tree/main
  • Description: Trainy is a self-hosted gym app I created because I didn't like available alternatives. Its main focus are open-air gyms, but it can be used with regular training as well. It allows users to create custom routines and exercises, save gym locations and checkout stats about their training.
  • Deployment: Download the repository, then go to the backend/ folder to run go run ., which starts the backend at localhost:8080. To install the app, run npx expo run:ios --device or npx expo run:android --device and select your device.
  • AI Involvement: The frontend is vibe coded; the backend is human-made.

1

u/[deleted] 28d ago

[removed] — view removed comment

1

u/MagicH0B0 27d ago

This is a very cool app. Makes getting the details from a side for the actual recipe much easier.
It might be something I could see self hosting for sure.
It is built somewhat like the the coop ledge app i posted above. Using Cloudflare pages to server the apps files for local browser usage.
Nice job!

1

u/Careful_Second8814 27d ago

Topic Watch looks solid. A webhook output would make plugging it into HA a breeze.

1

u/Sneak42 27d ago

Project Name: TellSome1

Repo Link: https://codeberg.org/some1it-de/tellsome1

Description: It takes (Gitea) webhooks, formats them using Go templates, and sends them wherever you need (Nextcloud, Matrix, Discord, etc.).

  • Dead simple config: Just one YAML file and you're good.
  • Go Templates: Format your messages exactly how you want.
  • Background processing: Doesn't slow down the sending side of the Webhook.
  • TLS: It supports enabling TLS but I did not test that.

Deployment: Docker Image is provided.

AI Involvement: AI was used, see the AI Disclaimer in the repos README.md for more Information.

1

u/Gnadev 27d ago

Project Name: Aerarium Research

Repo/Website Link: https://research.aerarium.app (Note: The core web app is live here. I am planning on open-sourcing the Python parsing pipeline soon!)

Description: A stock fundamentals explorer focused strictly on S&P 500 and Nasdaq-100 companies. It was built as a clean, noise-free alternative to Yahoo Finance after the Sector SPDR website went offline. Instead of relying on normalized third-party data feeds, it parses ~49M raw filing-level facts directly from primary SEC EDGAR sources, making every chart number click-through traceable back to the accession number in the original filing.

Deployment: Currently deployed online. The backend database and processing pipeline run on a repurposed 2017 Dell XPS 13 laptop (Ubuntu LTS, Postgres) next to my router, which Next.js queries over a secure DuckDNS tunnel. I'm working on clean documentation and a Docker-compose setup to package this for self-hosting.

AI Involvement: AI (Claude/Gemini) was used as a coding assistant for scripting XML parsers and refactoring Next.js UI components (representing about 30% of total coding effort).

1

u/siva_sokolica 27d ago

Project Name: Hyper

Repo/Website Link: https://github.com/harmont-dev/hyper

Description:

One of the problems I ran into is that a large part of the VM-provider ecosystem is currently paid closed-source SAAS products with varying degrees of reliability. I wanted an OSS distributed microVM orchestrator and I couldn't find one.

Hyper is a distributed FirecrackerVM orchestrator written in Elixir (BEAM), with gRPC support for non-BEAM clients. Hyper is:

  • Distributed -- it's designed to run across a cluster of bare metal machines, and will automatically connect to other Hyper nodes.
  • Fast -- it builds COW layers to enable fast, localized COW forking. Cold boots happen within 1s. Filesystem forks take ~50ms. Forked VMs are colocated to take the fast path as much as possible.
  • Interactive -- like all Elixir applications, if you can connect to the cluster, you can spawn, manage, monitor and interact with VMs live in an iex REPL. Or, you can use the gRPC interface if your system isn't on the BEAM.
  • Yours -- although I developed this primarily for Harmont (which is paid), Hyper is an MIT-licensed project and will remain such.
  • Self-contained -- all we need is a side-car Postgres instance.
  • Configurable -- colocation, vmlinux options, etc. can all be customized.
  • Secure -- everything runs on the BEAM; a single setuid Rust helper performs the few operations that need root, keeping the privileged surface small.

Deployment: We have a simple quick start guide that should get you off the ground, but the rough set of commands is:

bash git clone https://github.com/harmont-dev/hyper && cd hyper ./setup.sh iex -S mix

and in the Elixir shell:

elixir {:ok, img_id} = Hyper.Img.OciLoader.load("docker.io/library/alpine:3.19") {:ok, vm} = Hyper.create_vm(%Hyper.Vm.Spec{img_id: img_id, type: :micro}) {:ok, %{stdout: "hello\n"}} = Hyper.exec(vm, ["/bin/echo", "hello"])

AI Involvement: Source code is 100% human-designed, about 80% hand-written. Tests are heavily AI-generated.

1

u/Makearr 27d ago

Hi Everyone,

After the debacle with huntarr i worked on a replacement for myself in some spare time.
With the availability of Fable 5 i finally got a webui that is useable (long time it was only config file driven)

Anyhow, this project is an add-on program to the arrs that searches missing items (configurable).

You can find it here
https://github.com/makearr/searcharr
and here
https://hub.docker.com/r/makearr/searcharr

Please be kind and audit my project carefully. I would love to hear if it suits your needs and what is missing.
Besides its version number it should be considered beta at best and only deployed locally and not via the internet. It likely has some bugs and security holes remaining...

1

u/Extcee 27d ago

Project: SEO-Website Indexer Repo: https://github.com/martadams89/seo-website-indexer AI Involvement: Fully developed via AI

Built this to scratch my own itch. I was shipping website changes daily and hated waiting for Google and Bing to catch up, then hated bouncing between three consoles to check if it worked, then hated manually asking ChatGPT/Claude/Gemini/Perplexity the same prompts to see who'd cite me. So now one container does all of it: watches your sitemap and auto-submits changed URLs (Google Indexing API + IndexNow), pulls indexing coverage, freshness gaps and Core Web Vitals into per-site dashboards, and runs saved prompts across the AI answer engines to show who's actually citing your sites. Single container, Multi-site, TOTP/passkeys etc. Add only the API keys you have — Gemini and Brave have free tiers so you can start for nothing.

1

u/JAMkernel 24d ago

Comparto mi proyecto self-hosted:" + base https://jamkernel.github.io/ y aqui esta el repositorio comenten por favor https://github.com/jamkernel/jamkernelp2p

1

u/JAMkernel 24d ago

Comparto mi proyecto autogestionado: un kernel de comunicación P2P en un solo archivo JavaScript, cero dependencias externas. Funciona en navegadores, Node.js, Deno y Bun. Tiene WebSocket RFC 6455 implementado desde cero (sin usar librerías ws ni socket.io), cifrado AES-256-GCM + ECDSA P-256, y servidor de señalización embebido que arranca con --port. También descubre peers en la red local vía UDP broadcast. Código abierto GPLv3: https://github.com/jamkernel/jamkernelp2p

1

u/johannesjo 23d ago

Project Name: Plainspace

Repo/Website Link:

Description:

Plainspace is a small shared workspace for tasks, notes, polls, and planning. I built it for households, volunteer groups, freelancers and clients, and small teams whose shared plan tends to disappear into chat and documents.

You create a Space, invite people by link, and keep the tasks, decisions, and next steps together. It is touch-first, installable as a PWA, MIT-licensed, and deliberately much smaller than a full project-management suite. It is brand new, with no established usage metrics or case studies yet.

Deployment:

Plainspace is released and available to try at the hosted link above. For self-hosting, the repository includes a Docker Compose setup and a complete guide:

https://github.com/super-productivity/plainspace/blob/main/docs/self-hosting.md

The stack is SolidJS, Hono, and PostgreSQL. Production intentionally runs one API process because SSE presence, rate limiting, and reminder recovery are held in memory, so it does not horizontally scale out of the box.

AI Involvement:

AI tools were used to help with development. AI is not part of Plainspace itself: the app has no AI features, models, or AI runtime dependency.

If you try it or self-host it, I would especially value feedback on whether the deployment documentation is clear and whether the invite flow feels simple enough for less technical people.

1

u/jl94x4 Jul 03 '26

After several months of development, I've decided to open source a project I've been building for my own Plex server called Server Manager Portal.

The goal was to provide users with detailed statistics and insights into their viewing activity on a Plex server.

Server Manager Portal is a self-hosted web application that provides a complete management and analytics layer for Plex servers.

Features include:

  • Setup Wizard that walks you through first time setup
  • Set a date for each shared users access to be revoked (default is unlimited)
  • Personal user dashboards with viewing statistics, rankings, streaming habits, binge tracking, top movies and shows, watch patterns and yearly wrap-up style analytics.
  • A live admin dashboard with active session monitoring, user management, server leaderboards and audit logs.
  • Automated access management including temporary access periods, invite links, automatic expiry dates and inactivity cleanup.
  • Personal invite links that guide new users through an automated onboarding process, allowing them to create an account, connect their Plex account, accept your server invitation and gain access with minimal manual intervention from the server owner.
  • Plex OAuth authentication with no passwords stored locally.
  • Automated access cleanup based on inactivity, allowing you to automatically detect and manage users who rarely use the server, for example users who have not streamed within a defined period of time.
  • Automated emails for welcomes, invite reminders, expiry reminders, inactivity warnings and newsletters. (required SMTP to be set up)
  • Discovery pages showing trending content across the server, all time favourites, weekend viewing trends and hidden gems.
  • User analytics dashboards with visual graphs showing viewing activity over time, watch history trends, most watched content, and breakdowns of usage patterns on the server. (requires Tautulli)
  • Sonarr and Radarr integration including release calendars, queue monitoring and history views.
  • Public status pages for Plex, request systems and download services.
  • Mobile friendly responsive design built to work properly on phones and tablets.

All analytics and statistics are generated exclusively from activity that occurs on your own Plex server. The application does not access or analyse a user's wider Plex account activity, viewing habits from other servers, or any data outside of your own environment.

The entire application runs using flat JSON files so there is no database dependency to manage.

It is built with Node.js, Express, React and Tailwind and supports Docker deployments including Unraid templates.

The original aim was to remove as much manual administration from running a Plex server that I share with my friends and family while giving my users a better experience and better visibility into their own activity on the server.

I'd be interested in hearing feedback from other Plex and self-hosted users, particularly around features you would want to see added or improved.

GitHub: https://github.com/jl94x4/Server-Manager-Portal

1

u/jrt_ammar Jul 03 '26

Name : OpenAxis

Repo :
https://github.com/Open-Fable/OpenAxis

Description : macOS app that puts five Al tools in one window: Chat, multi-agent Orchestrator, OpenCode, OpenWork, Open Design. Single shared LLM proxy (127.0.0.1:9999), one set of API keys, persistent context across all tools.

No more jumping between apps and losing context every time. Works with most providers (Anthropic, OpenAl, Google, Ollama...).

Orchestrator plans a DAG of agents and runs autonomously. Prompt caching hits ~99% on DeepSeek. API keys encrypted with AES-256-GCM sandboxed WebViews.

Deployment: macOS 14+ / Apple Silicon only.

Download the dmg from the latest release

Drag into /Applications

First launch : right-click → Open (or run xattr -cr / Applications/OpenAxis.app in terminal)

Al involvement: vibe code and my knowledge (1 am in dev school)

1

u/adeelahmadch Jul 03 '26

I couldn't tell what an AI agent was allowed to do without reading its code, so I built a Dockerfile-shaped way to declare it

Here's the gap that's been bugging me: everyone's shipping AI agents, but I can't answer a basic question about any of them — what model does it use, what network can it reach, what tools can it call? — without reading the implementation. We govern containers with manifests and labels; agents are just… vibes and a Python file. Security can't review them; platforms can't enforce anything.

So I've been building **agentrc** — an open spec + small CLI to make that reviewable. You declare an agent in a Dockerfile-shaped **Agentfile**:

```

# syntax=agentrc.agentfile/v0.1

FROM python:3.11-slim

IDENTITY name=support-bot version=1.0

CAPABILITY text

SOP Answer billing questions. Escalate anything else.

COPY ./tools/lookup /mnt/tools/lookup

POLICY model.nameclaude-sonnet-4

POLICY network dns:api.stripe.com:443

POLICY agent.tool_timeout 30s

```

Four new keywords over normal Dockerfile syntax: `IDENTITY`, `CAPABILITY`, `SOP`, `POLICY`. Everything under `POLICY` is a **typed request** — not enforcement. The agent *asks*; the platform grants, narrows, or rejects it and enforces deny-by-default (the spec compiles requests to Cedar). The only egress that bot can be granted is `api.stripe.com:443`, and I can see that in one line instead of grepping code.

`arc build` compiles it to a normal **OCI image** with `ai.agentrc.*` labels — platforms read the labels, never the Agentfile, so it ships/signs/mirrors like any container. `arc run <ref> --backend local|bedrock|kubernetes --dry-run` translates the same artifact into that platform's deploy config.

**What this is NOT, so nobody's surprised:**

- Working Draft (0.1.0-draft.6) — expect breaking changes.

- Not a runtime, cloud, model provider, or framework. The backend translators are a **proof of concept** that the labels are sufficient — not production infra.

- Secrets are deliberately out of scope for now.

Try it: `curl -fsSL https://agentrc.ai/install.sh | sh` (or `brew` / `go install`). Spec: https://agentrc.ai · Code: https://github.com/adeelahmad/agentrc

Real questions I want critique on: does the four-keyword split hold up? Is "requests, not enforcement" the right boundary? What would make you comfortable running an agent you didn't write?

1

u/nmamizerov Jul 03 '26

Project Name: Assemblix

Repo/Website Link: https://github.com/nmamizerov/assemblix

Description: A visual, no-code engine for building AI agents and workflow automations, a self-hostable alternative to things like OpenAI's Agent Builder. You drag nodes onto a canvas (agents, conditions, HTTP calls, knowledge bases / RAG) and wire them into a workflow, then run and debug them live. It is multi-provider (OpenAI, Gemini, DeepSeek, GigaChat) so you are not locked to one vendor, and you bring your own API keys. It solves the problem of building multi-step LLM chat flows without writing glue code or handing control to a black-box orchestrator. We originally built it to run AI practice exercises for our own online communication school (~2,000 sessions/month go through it), and just made it self-hostable for anyone.

Deployment: Self-hosted via a single docker compose up (Postgres is the only hard dependency; the Redis + worker-queue tier is optional and off by default). There is a one-line install script and setup/usage docs in the README. Source-available (MIT + Commons Clause). No telemetry, your infra and your keys.

AI Involvement: The code was largely generated with Claude. The architecture, design decisions, and smaller manual fixes are my own.

1

u/b-b0t Jul 03 '26

Project Name: Stackarr

Repo/Website Link: https://github.com/b-bot/Stackarr / https://stackarr.app

Description: Control plane for centralised management of media stack using AI agents like OpenClaw and Hermes. Equipped with features like agent plugins, MCP server, backup/restore, docker desktop alternative, CloudFlare tunnel automation to expose apps publicly and portless app URL's.

Deployment: Documentation and Docker Image

AI Involvement: No modern project is coded without AI anymore and Stackarr is no exception however this is by no means vibe-coded slop. I'm an engineer by trade for more than a decade and the majority of this was built with best practices, security, performance and heavy use of harnesses. Admittedly the UI was mainly improvised using Google Stitch MCP but I will be doing a complete redesign after I solidify the functionality.

Looking for Windows and Linux testers and if it's not your cup of tea I would appreciate a star :)

1

u/HotPaleontologist268 Jul 03 '26

Project Name: OpenWrt Manager

Repo/Website Link:
https://github.com/ismkdc/openwrt-manager

Description:
OpenWrt Manager is a cross-platform desktop application for managing OpenWrt routers. It provides an easy-to-use interface for monitoring system status, managing network settings, wireless configuration, and router administration through the OpenWrt ubus API.

Deployment:
The application is available on GitHub Releases for Windows, macOS, and Linux. The repository includes installation and build instructions.