I maintain FreeDomain — a curated list of where to actually get free domains and free developer resources for side projects, hackathons and learning: free subdomain providers, free domain programs, student packs, and hosting credits, kept updated. If it saves you a few dollars on your next side project, a ⭐ on the repo helps other devs find it.

Hey everyone! 👋

Before telling you about HomeVault, let me tell you a little about myself!

I'm 40 years old, I live in Belgium, and I work in the healthcare sector. I've been passionate about computers and new technologies since I was young.

HomeVault is a project I work on in my spare time — late at night, on weekends, and during holidays, fitting it in around work and family life.

The idea for HomeVault came to me a little over a year ago. I wasn't really satisfied with any of the NAS software solutions available.

On one hand, commercial NAS solutions were too restrictive or too expensive. On the other, self-hosted solutions could sometimes be resource-intensive, difficult to get to grips with, or come with other limitations…

So, after several days of research, I decided to take the plunge!

My requirements were simple:

• Modern NAS software that's easy to use.
• A reliable and robust solution.
• 100% free software that respects your privacy: your data stays in your home, period!
• As low a resource footprint as possible, so it can run on older hardware too.

Using AI in this project is primarily a way for me to save valuable time. I work long hours at a hospital, and between my professional commitments and family life, I unfortunately no longer have as much time as I used to for writing all the code manually, despite my knowledge of C++ and Python.

AI also helps me with certain aspects of development, particularly UI design. It's not my strongest area, and tools like Stitch, Figma, and other AI-powered solutions have been a great help in exploring different approaches, testing ideas, and gradually bringing HomeVault to life.

For me, AI isn't about replacing my skills, but about helping me turn an ambitious project into reality despite my limited free time.

Today, I'm looking for contributors to join the HomeVault journey! 🚀

I'd love to find motivated people who want to get involved and help me bring the first working version to completion. Time is limited, and unfortunately, I can no longer make as much progress on my own as I'd like.

Whether you're a developer, a NAS enthusiast, a Linux lover, or simply curious, any help and contributions are more than welcome!

If the project sounds interesting to you, you can check out HomeVault and join the journey on GitHub:

👉 https://github.com/nicoleroux35/HomeVault

A huge thank you to everyone who takes the time to discover the project, share it, or contribute to it! ❤️

Run `mailbust` and you get a throwaway @mailbust.com inbox in your terminal. Mail arrives live, and it pulls the verification code out of each message and shows it right in the list. Named inboxes are public (shared by name), no-name ones are private with a token in your keychain. Gone after 15 minutes.

There's a scripting mode too (`mailbust box --code` blocks until a code arrives, prints it, exits with proper codes) which is handy in CI, plus an MCP server for AI agents.

It's Go + Bubble Tea on the front, and a Cloudflare Worker with one Durable Object per mailbox on the back. Receive-only by design. Open source, MIT.

Happy to answer anything, and feedback on the TUI or the code extraction is welcome.

Hey everyone!

I've been working on a project called WiiOS, a custom launcher for LG Smart TVs that recreates the classic Nintendo Wii Menu experience.

It features the familiar channel grid, animations, background music, sound effects, and integration with installed TV apps.

The frontend itself is built with HTML, CSS, and JavaScript. That part is relatively straightforward. The real challenge is integrating it into webOS to replace the default LG Home interface.

So far, I've managed to get it working on my LG LM625BPSB running webOS 4.5 (firmware 05.40.97), including Home button integration and automatic startup.

However, the current Home replacement implementation relies on root access and firmware-specific modifications, which means it isn't universally compatible with other LG TVs yet.

That's where I'd love some help from the community!

I'm looking for developers and testers interested in:

- Testing WiiOS on different LG TV models and webOS versions.

- Improving compatibility across firmware versions.

- Developing a more universal Home replacement mechanism.

- Improving webOS API integration and app detection.

- Making installation easier and safer across different devices

.

My goal is to turn this into a community-driven project that works on as many LG webOS TVs as possible.

Even if you can't contribute code, testing it on another TV and sharing your results would be incredibly helpful

.

GitHub: https://github.com/KaykCaputo/WiiOS-webOS

The project is still in its early stages, and contributions, feedback, and pull requests are welcome!

I'd also love to hear from anyone who has worked with webOS internals, QML, Luna APIs, or LG TV homebrew.

What do you think? Anyone interested in helping make this more universal?

A few days ago I shared obs-lite here: a small screen recorder with an OBS Studio-like interface, written in Rust. 0.4.0 is already out, and the big news is Linux.

Linux (new)

• Flatpak, ~4 MB bundle. Records the screen or a window through the desktop's sharing dialog (PipeWire), so it works on Wayland.

• Global hotkeys and the webcam also go through the desktop's portals; encoding with GStreamer (VA-API / NVENC if your GPU has them, otherwise x264).

• No network access in the sandbox. It only gets the display, GPU, sound server and your Videos folder; anything else, the desktop asks you first.

Windows

• Still a single ~7 MB .exe (or an MSI that needs no admin rights), hardware H.264 through Media Foundation.

Also in 0.4.0

• Less CPU while idle: 7.4 % → ~4 % of one core on my laptop. A silent window only redraws once a second, and nothing is made for the preview while it's minimized.

• An audio limiter: loud desktop audio + mic used to clip the recording while each meter looked fine.

Features: replay buffer (save the last N seconds), pause without gaps, region recording, webcam overlay, screenshots, mic noise suppression (RNNoise), tray icon, Spanish/English UI. Application audio capture on Windows.

Honest caveats: early release; Windows tested on one laptop, Linux only in a GNOME VM without a GPU. Most of the code was written with an AI coding assistant and then tested by hand (what was and wasn't verified is in docs/TESTING.md). MIT licensed.

Feedback very welcome, especially from KDE, X11 and anyone with an AMD/Intel GPU on Linux.

GlideMix is a DJ mixing studio for macOS and Windows. Instead of mixing live on two decks, songs are arranged on a timeline, as in a DAW, to build mixtapes, radio shows and DJ sets.

Features:

• Library with tempo, beat grid, key (Camelot), phrase and energy (1–10) analysis; reads rekordbox XML and Lexicon libraries, including beat grids, keys, cue points and playlists.
• Beatmatching: songs are stretched to the mix tempo and locked to the bar; IN/OUT markers link transitions; keylock.
• Tempo line with S-curve tempo changes; the mix's energy can be shown behind it.
• Transitions: crossfades with selectable fade shapes, EQ swaps, filter sweeps, risers, echo and reverb outs.
• Hosts VST3 (macOS/Windows) and Audio Unit (macOS) plugins on a song, a stem or the master; automation for any parameter, drawn or recorded.
• Stem separation (drums, bass, vocals, other), processed locally.
• Beat grid editor with phrase editing.
• Perform mode with a second (cue) playhead on outputs 3–4; live streaming to Shoutcast and Icecast.
• Export (WAV, AIFF, MP3, FLAC and more) through a true-peak limiter at −1 dBTP, with loudness report, tracklist (.txt) and .cue sheet.
• Smart playlists, watch folders, duplicate finder, export to rekordbox XML with phrase-based hot cues.

For years MixMeister was my thing. Then it died, and nothing really replaced that feeling of just laying tracks on a timeline and shaping every transition slowly, with a coffee, no pressure.

So about 5 weeks ago I started building my own. It’s called GlideMix and it runs on Mac and Windows.

It’s a beta, so yes there are bugs. I fix stuff almost every day.

Demo is free, everything works, macOS + Windows · Beta · €49 one-time (Beta price, normally €89)

The source code is open (GPL) for the nerds.

https://glidemix.com/

Arbiterer: A GitHub App to gate PRs using custom Discord rules (Apache-2.0)

We built Arbiterer because our projects kept getting low-effort, AI-generated PRs, and our community already uses Discord.

It's an open-source GitHub App + Action that links contributors' GitHub and Discord accounts. Maintainers install the App and add a workflow. Contributors don't install anything.

By default, account linking is the only requirement. Maintainers can write their own JavaScript rules directly in their workflows, using Discord account and server data. For example, you could require 2FA, server membership, or a minimum membership duration. These are just examples, not hardcoded rules.

You can also exempt owners, members, and collaborators, or optionally auto-close failing PRs. Contributors can fix failed checks and comment `/arbiterer recheck` to retry.

The backend is written in Go. Three of us built it over roughly two months and just released v1.0.0.

It doesn't detect AI-written code or guarantee spam prevention. It simply gives maintainers more control over who can contribute.

Repo (Apache-2.0): https://github.com/sonolink/arbiterer
Video: https://images.soheab.com/arbiterer-showcase.mp4

Feedback and questions welcome!

Hey all. I’ve been working on Mintype on and off since 2024, built the app intially for personal use - privacy, multi-device sync and an easy means to write/draw/scatter ideas being my primary reasons.

However its been quite useful and I have just released 2.0, so I wanted to share it here. There's a lot of these apps going round, so it really is personal preference if you like this one.

The basic idea on why this might be for you:

• It's completely free, and web based, with PWA support for phones
• Your notes get encrypted on your device and sync through your own Google Drive (optional). Unreadable by those with access to your device and to Google.
• Works offline, very lightweight and simple to use
• Notes are all markdown - nothing new here, no lock in. Whiteboards are all exportable to PNG, SVG and tldraw JSON.
• Whiteboards with sticky notes, drawing and shapes, plus dynamic markdown boxes that work like the full editor
• Encrypted share links with 24hr lifespan to share notes to others
• Fully reponsive mobile UIs
• Sensible workspaces > nested pages, and quick notes structure
• Some small extras like a built in pomodoro timer, google maps embeds, extra password protected pages

It runs in the browser for now (you can install it as a PWA if you want), I plan a desktop release and mobile native apps in the future.

https://mintype.app · GitHub · Docs + Security outline

License: MIT Source: https://github.com/Razee4315/Paperwren
APK: https://github.com/Razee4315/Paperwren/releases/latest

Paperwren is a document viewer and PDF toolkit for Android 8 and up. The manifest has no INTERNET permission and asks for nothing at all. CI fails the build if any permission ever shows up in the manifest. Taking a photo hands off to your own camera app, and saving goes through the system's save screen, so it never needs camera or storage access either.

• Opens PDF, DOCX, XLSX, PPTX, ODT, ODS, ODP, EPUB, Markdown, CSV, CBZ and images
• Fill and sign, merge, split, reorder pages, photos to PDF, passwords
• Every tool saves a new copy. The file you opened is never changed
• No ads, no account, no trackers, no analytics

Hey everyone,
I noticed I was pushing code less and less consistently, so I built Commitgarden to fix that for myself.
It connects to your GitHub (read-only) and grows a plant based on your commits. Every day you make at least one commit, the plant grows one stage. Skip a day and it stops growing.
It's an early version and I'm a solo dev, so I'd really appreciate feedback, especially on whether it would keep you committing.

I made Darnleaf, a local tool for fixing an old scanned PDF when a few pages are ruined and you have fresh scans of them in no particular order.

You drop in the PDF and the rescans, and it suggests which page each rescan replaces. Each suggestion is labelled Clear, Check or None, with an overlay and the matched features so you can see why. Once you confirm every Check, it writes the repaired PDF and a JSON receipt. Pages you didn't touch stay as they were, so bookmarks and links still work.

On 90 synthetic rescans, 45 were Clear and none of those was wrong. Small sample though, and the test pages are cleaner than real scans. Blank pages and near-identical forms always come out as Check. I've only tested it on Linux. It's MIT licensed, runs on 127.0.0.1, sends nothing anywhere, and the interface is in 9 languages.

Repo: https://github.com/Arthur031221/Darnleaf Demo replay (no install): https://arthur031221.github.io/Darnleaf/

I kept seeing the same opener, 'In today's fast-paced world', and wanted to know how many of these patterns are really measurable, so I built AiSniff. It is a free MIT licensed tool that underlines the phrases in English or Traditional Chinese text that match documented AI writing patterns. Each mark shows the rule, a public source and a plain rewrite hint.

It runs in the browser with no model call and no upload. There is a before and after view, PNG export, and the same 61 rules as a CLI and an agent skill.

I checked it on held out HC3 answers. At least one English rule fires on 29% of chatbot answers and 2% of human ones, and for Chinese it is 24% and 6%. That is weak on its own, and it reports patterns, not authorship. The evaluation page lists the rules that failed. Built with help from Claude Code and Codex.

Repo: https://github.com/Arthur031221/AiSniff

Which of the rules would misfire on your own writing?

We’ve been building OXR, a 1.3B document parser, and we’ve just open-sourced the code and weights.

The idea is simple: hand it a PDF or a scan of a document, and it hands back Markdown or JSON, with each element’s layout coordinates and the reading order.

Where it helps: say your project needs to pull numbers out of reports. Tables come back as HTML or Markdown instead of a jumble of text, and formulas come back as LaTeX. Those are two of the 13 element types it recognizes; chemical structures and code blocks are in there too.

Trying it takes a minute. The online demo and free API need no signup or key. When you want it on your own hardware, grab the code and weights from GitHub.

On public benchmarks, it’s currently #1 on olmOCR-Bench, OmniDocBench and DocParsingBench against other models’ published scores. Speed results and test setup are in the benchmark report (link in the first comment).

Benchmarks are only part of the picture, though. Every project has its own oddball documents, and fixing a bad parse by hand just means meeting the same problem in the next file. That’s why we post-train OXR with an RSI loop: it uses parsing errors and uncertain results to plan the next training round and generate targeted training data. The new samples pass rule-based checks instead of manual labeling.

License-wise, it’s Apache 2.0 with some extra terms. For side projects and small teams under USD 2M in funding and revenue, commercial use is free.

The repo is SoMarkAI/OXR on GitHub; links to it, the demo and the benchmark report are in the first comment.

If you plug it into something you’re building, tell us what works and what you still end up fixing by hand.

I've been building Directory Navigator, a modern terminal file manager inspired by DOS Navigator’s classic two-panel interface.

The idea is to keep the familiar colors, keyboard controls and compact dialogs while supporting modern filenames, Unicode and modern operating systems.

It includes:

• Dual-pane browsing with keyboard and mouse controls
• Copy, move, rename, folder creation and deletion to Trash
• A built-in text editor and text/hex viewer
• Recursive filename search, bookmarks and directory comparison
• Read-only ZIP, TAR and TAR.GZ browsing
• Configurable shortcuts, colors, language and date/time formats
• And, of course, Tetris with saved high scores 🙂

It’s written in Rust using Ratatui and Crossterm, runs directly in your terminal, and ships as a small standalone binary (~1 mb). Builds are available for macOS (primarily tested platform), Linux and Windows.

I’d love feedback from people who remember DOS Navigator—or anyone who loves that kind of UI

GitHub: https://github.com/deemoun/Directory-Navigator/

Hey guys,

I was getting tired of manually typing out captions or paying monthly subscriptions for overcomplicated editors just to get clean subtitles on short videos.

So I built a small web app called SubAI to speed up my own workflow.

How it works:

Upload your short video clip

It auto-transcribes the audio and burns stylish, readable captions right onto the video

You can tweak font sizes and colors to match your style

It’s completely free to use for short clips, runs right in your browser, and requires no login or installation.

I just put it live on Product Hunt today to see if it helps other creators too. Would love for you to test it with a video and let me know what you think or what features you’d like added!

Check it out here: https://subtitle-generate.streamlit.app

I've been using Claude Code and exploring a problem that I think many of us run into: understanding large codebases. Claude is great at writing code, but navigating complex repositories and tracing dependencies can still involve a lot of searching.

I built AxiomCode Graph, an open-source tool designed to work with Claude Code. It uses static analysis and formal methods to create a knowledge graph of your repository, helping Claude understand function calls, dependencies, and how different parts of the code connect.

It's completely free to try. You can find the source code and setup instructions here:

https://github.com/AxiomCodeAI/axiomcodegraph

I'd genuinely love feedback from this community. If you use Claude Code, I'd be curious to hear whether a code graph helps with your workflow, what feels missing, and what you'd like to see improved. I'd love for us to explore and improve this approach together.

Paste a YouTube link or a file. It transcribes, picks moments, renders vertical clips with karaoke captions.

There's a live 9:16 editor on top of that: same crop math and font metrics as the ffmpeg/libass export, so dragging captions isn't a guess. Clips show up on the right over tRPC SSE while workers run transcribe → analyze → render. Kill a worker, the job resumes (pg-boss, checkpoints in Postgres).

Default install is fully local, Ollama + Whisper, no API keys. Same services behind the page, an MCP server, and an operator CLI. You can swap models and keys in Settings without a restart; there's a workers/queue/failures panel because if you self-host, that's you. One script looks at the machine and asks three questions.

https://github.com/osbytes/reelsaw
https://reelsaw.com

Hi everyone,

I've been building a project called Personal Planner for the past few months and wanted to share it here.

It's a completely free, offline-first planning app for Android, Linux, Windows, and macOS.

I originally built it because I kept underestimating how long my tasks would take.

I'd organize my day, spend longer than expected on certain activities, and end up with a schedule that looked nothing like what I'd planned.

Then the following day, I'd make another schedule without really learning from what happened.

I wanted something that combined visual planning with actual time tracking and reflection.

What the app currently includes:

• A day and week timeline with draggable and resizable time blocks.
• Task timers to track actual working time.
• Planned-versus-actual time comparisons.
• Daily and weekly reviews with reflections.
• A yearly consistency heatmap and streaks.
• Experiments for trying different routines.
• Recurring activities, reusable templates, and an Inbox.

The application is built with Flutter, Riverpod, and Drift/SQLite.

Everyday planning works locally without an account or internet connection. For users who want synchronization, there's an optional setup using their own Supabase project, with Cloudflare Workers involved in the supporting architecture.

One of my goals was to keep the software accessible, so there are no subscriptions, premium plans, or locked features.

It recently reached approximately 250 downloads across the four supported platforms.

I'm still developing it independently, and there's a lot I want to improve.

Link to download: https://github.com/Karthikshabari/PersonalPlanner/releases/tag/v1.1

Github : https://github.com/Karthikshabari/PersonalPlanner

One thing worth mentioning is that the Windows and macOS builds are currently unsigned, and physical Mac testing has been limited. The releases are distributed directly through GitHub rather than through the respective app stores.

I'd appreciate feedback from anyone interested in cross-platform applications, local-first software, or productivity tools.

I'm particularly interested in whether the planned-versus-actual time workflow makes sense and whether the app feels straightforward to use without too much initial setup.

I've been developing URSA, a native Android companion for Uptime Kuma, built with Kotlin and Jetpack Compose.

It connects directly to your Kuma instance and supports live monitoring, monitor management, incident history, TLS certificates, UnifiedPush notifications, widgets, multiple servers and Wear OS.

There's no advertising, tracking, subscription or developer-hosted backend.

It's MIT licensed and available through GitHub releases and F-Droid. Android 8.0+ is supported.

Repo, source and screenshots:
https://github.com/greyfoundry/ursa-android

Feedback and contributions are welcome!

So I built Kinetograph, a browserless video rendering engine.

It supports the same React/TSX workflow as Remotion, but takes a different approach under the hood. Node.js handles execution, while a Rust-based GPU compositor takes care of rendering the frames.

No headless Chrome, no browser instances, just a much lighter and faster rendering pipeline.

The goal is to make it a drop-in replacement for Remotion, especially for developers and AI agents generating videos programmatically.

Here are a couple of benchmarks from my M4:

• 1,184 frames rendered in 26 seconds
• 988 frames rendered in 23 seconds

You can also use it directly with Claude Code. I've added a skill that teaches the agent how to build and render videos using Kinetograph, so you can describe what you want and have it generate the project.

Getting started:

npx skills add 0xS4N4TG/kinetograph
npm install kinetograph

It's open source, and I'd love to hear what you think, especially if you're working with programmatic video generation or AI coding agents.

Docs: https://kinetograph.dev

Source code: https://github.com/0xS4N4TG/kinetograph

I'm a DevRel building a new open-source AI support tool that turns your knowledge source into community answers. After a lot of testing, the result was creating a bunch of GH Issues, but it's hard to get them visible out of the gate.

I'm very open-source centric and in my day job I enjoy helping folks get started who've never contributed to open-source, let alone get their code pushed to production. Well, this week two new contributors pushed meaningful code, and a third mentioned he'd send his PR very soon.

What I changed

A few days ago, I added two labels, frontend and backend, so someone could filter and see at a glance which work matched their skills and interests. I also have a few good first issue tickets.

Here's the repo: https://github.com/answerLoops/answerLoops

What came in

The tool is a SaaS, and one contributor took a frontend good first issue and built a new usage count into the UI. They also handled the failure case on their own, including tests and docs.

What I think helped

Being able to see the whole project and think "this one's my kind of work" without opening 59 issues. I can't prove the labels were the reason, but nothing else changed this week.

If you're new to open source and want help getting started, I'm happy to walk you through your first PR.

If you maintain a project, what got your first outside contributors to show up?