Lifters who self-host their training logs in wger want to record structured data on each individual set, like whether a resistance band is single or doubled, distance from a cable anchor, or bench angle, rather than stuffing it into one free-text note per workout. Per-set reps already work, but there are no user-defined custom fields, and four separate users have asked for set-level or per-exercise annotation over the last six months. The value is logs that actually capture the variables band, cable, and calisthenics lifters need to reproduce a set.
builder note
Per-set reps already work (wger combines repeated exercises into set rows), so do not ship another notes box. The gap is user-defined columns per set, like band doubled or anchor distance, which is a small schema and UI feature, not a rewrite.
landscape (2 existing solutions)
wger, the leading FOSS self-hosted strength tracker, logs per-set reps and weight plus workout-level notes, but structured, user-defined per-set fields have no home there. The proprietary cloud apps that come closest are not self-hostable.
wger Self-hosted strength tracker. Per-set reps and weight are loggable (the maintainer notes you can split a set by re-adding the exercise) and notes exist at the workout level, but per its features page and the open issues there are no user-defined custom data fields per set such as band single or doubled, anchor distance, or bench angle. Hevy Proprietary cloud app with per-set RPE, set types, and exercise notes, but it is not self-hostable, and these users specifically want the capability inside their own self-hosted log. sources (3)
fitnessstrength-trainingself-hostedwgerdata-logging
Creators and multilingual organizations on PeerTube -- the federated, self-hostable YouTube alternative -- want selectable alternate audio tracks (e.g. dubbed languages) on a single video instead of uploading one copy per language. PeerTube supports multiple subtitle tracks but only one audio track, so today people duplicate uploads, wasting storage and splitting their view counts, comments, and audience. The long-open request is still drawing fresh interest from multilingual companies, filmmakers, and screen-reader users.
builder note
Frame it as 'one upload, many languages' for dubbed and multilingual channels, not a generic player tweak; the duplicate-upload pain (storage plus split audience) is the real wedge, and since HLS already supports multiple audio renditions the hard part is the transcoding pipeline and a clean track-picker in the player, not the spec.
landscape (3 existing solutions)
Multilingual and dubbed-content channels on the federated, self-hostable YouTube alternative have no way to attach selectable audio tracks; HLS already carries multiple audio renditions, so the gap is PeerTube's transcoding pipeline and player UI, not a fundamental limitation.
PeerTube (current) Supports multiple subtitle/caption tracks but only a single audio track per video; the feature request (#939) is still open and unimplemented after years of demand. Duplicate-upload workaround Uploading one video per language wastes storage on the instance and fragments view counts, comments, and the audience across copies. YouTube multi-language audio The incumbent already offers selectable dubbed audio tracks, setting an expectation PeerTube can't meet -- a concrete reason multilingual creators stay on YouTube. sources (1)
peertubefediversevideoi18naccessibility
A self-hoster with ~30k photos in Immich wants to auto-surface the best shots from each trip/event to print albums, and the thread agrees nothing Immich-native/self-hosted does it. Immich browses, tags, face-recognizes, and de-dupes but does not hand back a best-in-album shortlist; PhotoPrism has automatic quality scoring, but it is a separate library and review queue rather than an Immich-integrated culling workflow. The gap is a local, Immich-integrated tool that groups near-duplicates, scores sharpness and eyes-open shots, and hands back the keepers.
builder note
Resist building a general 'photo organizer' -- the entire job is one opinionated verb, 'pick the keepers from this trip,' so an Immich plugin/sidecar that groups near-dupes and scores sharpness/eyes-open and returns a shortlist beats a feature-sprawl app; on-device vision models make this a local-first feature, not a cloud one.
landscape (4 existing solutions)
Culling is partially solved in standalone photo managers and pro desktop workflows, but not for Immich-centered self-hosters who want a local service to score a trip or album in place and return a keeper shortlist.
Immich Does browsing, face recognition, semantic search, and duplicate detection, but does not rank or cull for 'best shot' within a burst, trip, or album. PhotoPrism Creates an automatic 1-5 quality score and review queue, but it is a separate photo library and low-quality review mechanism, not an Immich-sidecar workflow that selects best shots from a specific event and writes a shortlist back to Immich. czkawka Finds near-duplicates by hashing, which thins bursts, but doesn't judge quality (sharpness, eyes-open, composition) to pick the keeper. Aftershoot / Imagen Dedicated pro culling tools; Aftershoot runs locally/offline, but the workflow is still desktop/pro-shoot oriented and subscription-based, with no self-hosted service that plugs into an Immich library. sources (1)
self-hostedimmichphotoscullinglocal-ai
Owners of Wi-Fi/Bluetooth robot mowers want local, manufacturer-independent control plus portable mapping, zones, and scheduling, because every brand ships its own cloud app and locks the data inside it. Right now this is served only by a swarm of separate per-brand reverse-engineering projects (one repo per manufacturer), so no unified, local, cross-brand control and mapping layer exists. The value is for homeowners and home-automation users who want their mower in Home Assistant and want maps that survive a vendor shutting down its cloud.
builder note
Don't try to boil the ocean across 20 brands at once; pick the 3-4 fastest-growing cloud-locked brands (Mammotion, Eufy, Sunseeker) and nail portable maps plus local scheduling, because the real moat - and the reason per-brand hacks keep dying - is sustained reverse-engineering as vendors rotate cloud auth.
landscape (4 existing solutions)
Robot mowers are as fragmented as early smart plugs: every brand has its own cloud app and no neutral layer offers cross-brand local control or portable mapping/scheduling over mowers you already own, which is why a Home Assistant forum thread tracking 18-20 brands and a swarm of single-brand repos keep re-solving the same problem separately.
Home Assistant lawn_mower entity platform Provides a unified entity type but every brand still needs a bespoke integration, mapping and zones are not standardized, some mowers are mis-exposed (Ecovacs GOAT shows up as a vacuum), and it requires running Home Assistant. OpenMower Excellent open RTK-GPS control, but only for hardware you physically convert yourself, not the retail cloud-connected mowers people already own. sources (3)
smart-homerobot-mowerhome-assistantinteroperabilityiot
Hearing-aid and cochlear-implant users want to stream audio straight from Linux PCs, Steam Decks, and DIY Bluetooth adapters over the ASHA protocol rather than being tied to a phone or forced to buy the manufacturer's proprietary streaming accessory. Today this works only through fragmented, per-brand, GUI-less developer projects that re-break on every device firmware or OS update, so getting sound requires deep Bluetooth debugging. The opportunity is a reliable, multi-brand, GUI-driven ASHA streaming and pairing layer for an audience whose hearing device is their only audio path and who will pay to never lose it.
builder note
The trap is shipping another single-brand hack that dies on the next firmware or BlueZ update; the defensible product is a maintained multi-brand compatibility layer with a real pairing GUI (ideally paired with a certified hardware adapter), because for this audience audio literally stops working without it.
landscape (4 existing solutions)
Streaming ASHA audio from anything other than a phone is served only by fragmented, single-maintainer, GUI-less projects plus an experimental mono-only native stack, so each hearing-aid brand and each OS update silently re-breaks audio for users who have no alternative audio path.
Native BlueZ + PipeWire ASHA support Verified against the developers' own writeup: experimental, mono-only with stereo still 'pending', no pairing/tuning GUI, tested on a single device, and not yet in stable distributions. Pico-ASHA (Raspberry Pi Pico W ASHA bridge) DIY firmware bridge maintained essentially by one developer; per-brand breakage (Starkey never establishes L2CAP, Med-El/Rondo regressed between releases) and a pairing UI still being hacked together. sources (3)
accessibilityhearing-aidscochlear-implantlinuxbluetooth
The May-June 2026 Plex price hikes are pushing a wave of users toward Jellyfin, but many won't switch because the living-room client experience is worse: the free Apple TV client is criticized as slow and 'basically unusable,' the polished alternative gates features behind a paid tier, and there is no native client for PlayStation at all (Xbox has an official open-source client). Households sharing a library with non-technical relatives need a TV/console app as polished and reliable as Plex's first-party apps. This is a UX/platform-engineering opportunity, not a new backend.
builder note
Don't pitch 'another Jellyfin client'; Swiftfin already exists and is FOSS. The actual demand is the unglamorous platform work the FOSS clients keep under-investing in: Plex-grade tvOS polish and speed, plus console reach (PS4/PS5). Whoever does the boring living-room engineering, not the feature list, captures the people who are otherwise stuck paying Plex.
landscape (4 existing solutions)
Jellyfin's server and its remote-access friction are heavily discussed, but the living-room client gap is distinct and under-served: the free tvOS client lags on polish/speed, the polished option (Infuse) gates advanced playback behind Pro and isn't Jellyfin-native, and PlayStation has no native client at all (Xbox has an official open-source client via the Microsoft Store). With Plex actively pushing users away in 2026, a free, fast, Plex-grade Jellyfin client for Apple TV and consoles is the piece that would actually complete the migration.
Swiftfin (official Jellyfin tvOS/iOS client) Free and open source, but multiple users in-thread call it slow, 'not very visually appealing,' and 'basically unusable' on Apple TV compared to Plex's app; polish, speed, and reliability are the blocker, not existence. Infuse Polished and has a free tier that plays media on Apple TV, but advanced video formats, HD/Dolby audio, AirPlay/Cast and advanced sync require Infuse Pro ($1.99/mo, $16.99/yr, or $99.99 lifetime); it is also a general media player, not a Jellyfin-native client, so deep Jellyfin features are second-class. Jellyfin on PlayStation There is no native Jellyfin client for PlayStation 4 or 5 (an open feature request); Xbox has an official open-source Jellyfin client on the Microsoft Store. Console households that access Plex via a PS4/PS5 app have no equivalent, which is cited as a hard blocker to migrating. Plex (incumbent being fled) Its first-party Apple TV and console apps are the polish/'just works for non-technical family' benchmark users measure Jellyfin against; that client quality is the main reason lifetime-pass holders stay despite the price hikes and enshittification complaints. sources (1)
jellyfinapple-tvplaystationmedia-serveranti-subscription
Excalidraw users have spent years asking for a real table element instead of hand-aligning rectangles and lines, and it is the tool's single most-reacted request, still collecting plus-ones this month. Teams that want tables on an infinite canvas are stuck choosing between proprietary SaaS like Miro and FigJam or hacking it together in the open tools. The opportunity is a true table shape or plugin for the open whiteboard ecosystem, or a diagram tool that ships tables natively.
builder note
Excalidraw has no real custom-element plugin API, so the pragmatic first win is a 'generate a table' helper that emits native Excalidraw rectangle and text groups bound together, rather than waiting for upstream to add a first-class table type.
landscape (3 existing solutions)
Tables are table-stakes in the paid whiteboards but absent from the open, embeddable ones, despite being the loudest Excalidraw request for years. The capability exists, just not where you can self-host or embed it.
Excalidraw No native table element. Users manually align rectangles and lines that drift and break on edit, which is what drove this to the top of the request list for four years. tldraw The other major open and embeddable canvas SDK also ships no native table shape, only basic shapes, arrows, sticky notes, and a custom-shape extension API that each integrator would have to build tables on themselves. Miro / FigJam Have polished native tables, but they are proprietary SaaS you cannot self-host or freely embed, and they carry per-seat pricing, so the capability is locked behind the closed tools. sources (1)
whiteboardexcalidrawdiagrammingtablesopen-source
Audiobookshelf users who keep audiobooks and ebooks in one library want their ebooks to sync wirelessly to Kobo e-readers the way Calibre-Web already does, without cables or running a second server. The top Audiobookshelf request, labeled by maintainers as a possible plugin, asks for exactly this. The opportunity is a Kobo-sync bridge for Audiobookshelf, or a unified server that finally covers audiobooks plus ebooks plus native e-reader sync in one place.
builder note
Do not fork Audiobookshelf. The cleanest build is a sidecar that speaks Kobo's sync API and reads an existing Audiobookshelf library, since the issue is literally tagged 'possible plugin' and Calibre-Web already proved the sync protocol is reverse-engineerable.
landscape (4 existing solutions)
BookLore 2.0 now covers both audiobooks and Kobo sync, partially closing this gap. The persisting opportunity is in the Audiobookshelf ecosystem specifically: its mobile apps (Prologue, ShelfPlayer) and plugin community are more mature than BookLore's, so users already invested in that stack still have no native Kobo sync path. The opportunity may be an Audiobookshelf-specific bridge rather than a new unified server from scratch.
BookLore BookLore 2.0 added full audiobook support and bidirectional Kobo e-reader sync, covering the unified-server + Kobo-sync combination this signal describes. The gap versus this signal is primarily ecosystem maturity (Audiobookshelf has a larger plugin/app ecosystem, including Prologue and ShelfPlayer), and BookLore's Kobo sync implementation differs from Calibre-Web's battle-tested OPDS-based approach — builders should assess whether BookLore's sync is feature-complete before treating this as a fully open space. Audiobookshelf The best self-hosted home for both audiobooks and ebooks, but it has no Kobo sync, so ebooks must move over a cable or through OPDS and email workarounds rather than syncing automatically. Calibre-Web Has real built-in Kobo sync (chosen shelves become Kobo collections, with automatic kepub conversion), but it only handles ebooks, not audiobooks, so users who want both end up running two separate servers. Kobo native sync Wireless sync works only from the Kobo store, Dropbox, or an OverDrive library, never from your own self-hosted collection, which is the whole reason people self-host their books. sources (1)
self-hostedebookskoboaudiobookshelfsync
People who moved family photos off Google Photos onto self-hosted Immich keep hitting the same wall, that sharing is clunky compared to what they left. The single most-reacted Immich request is a meta-issue begging for better albums, partner sharing, shared links, and library sharing, and the maintainers openly froze sharing work pending a redesign. The opportunity is a frictionless sharing and collaboration layer for self-hosted photos, or a competitor that nails sharing first.
builder note
The trap is recommending features Immich already ships — it has partner sharing and shared links today, just poorly executed. The wedge is the UX redesign and reliability it publicly froze: seamless cross-device album collaboration, non-technical family member onboarding, and a sharing interface that doesn't require understanding Immich's internal library model. Build that layer on top of the existing Immich API rather than a new server.
landscape (2 existing solutions)
Self-hosted photo apps have nailed ingest, machine learning, and browsing, but sharing is the weakest surface across the board. The leading app publicly froze the feature, which turns a hunch into a validated, well-scoped gap.
Immich Has basic albums, partner sharing, and shared links, but the project froze sharing improvements pending a full redesign, and the 1000-plus reactions show current sharing is the most-felt weak spot. Google Photos The sharing experience everyone is benchmarking against (one-tap partner sharing, collaborative albums, instant links), but it is cloud-only and tied to the privacy and cost concerns that pushed these users to self-host in the first place. sources (1)
self-hostedphotosimmichsharingfamily
People who run their own private or self-hosted food and fitness tracker want their logged calories, water, weight, and sleep pushed back out into the phone's health hub (Apple Health / Android Health Connect) so the OS, their rings/watches, Home Assistant, and clinician apps all see one complete picture. Today these trackers are read-only sinks or standalone, so privacy-minded self-loggers keep a parallel MyFitnessPal account just to feed Apple Health. The opening is a privacy-first tracker that is a first-class WRITER to both platforms.
builder note
The moat isn't the food diary, it's being a reliable WRITER to HealthKit and Health Connect... HealthKit has no backend API, so you must ship a small native companion on each platform that syncs and writes on-device. Nail bidirectional sync and you become the private hub everything else points at.
landscape (3 existing solutions)
HealthKit has no server API (data lives on-device), so any self-hosted tracker needs a thin native iOS/Android companion that holds the permissions and writes to the health store. That platform plumbing, not the food diary, is why FOSS trackers stay read-only and users keep a second MyFitnessPal copy alive.
SparkyFitness Actively developed self-hosted nutrition/fitness tracker, but writing your logged data back to Apple Health and Health Connect is unbuilt (these are the open requests). It is effectively a data sink, not a writer. Open Wearables Self-hosted platform that syncs HealthKit/wearable data INTO your backend (read-in). Solves the opposite direction; does not push your own logged nutrition back OUT to the OS health store. MyFitnessPal / Cronometer Proprietary apps that DO write nutrition to Apple Health and Health Connect, but they are cloud-bound, ad-supported, and not self-hostable... which is exactly what these users are trying to leave. sources (2)
self-hostedhealth-dataapple-healthhealth-connectprivacy
Home Assistant users with LG washers, fridges, and AC units are getting their LG accounts temporarily banned because the popular community integration's polling looks like 'automated script usage,' breaking their automations. They want their appliances to keep working locally without risking a cloud account lockout. This is the appliance sibling of the broader manufacturer-lockdown trend, aimed at white-goods owners rather than car owners.
builder note
This is a cat-and-mouse game against a manufacturer who can change the rules, so do not sell a polished consumer app that LG can brick overnight. The defensible play is a respectful, rate-limited, official-API-first bridge (or local LAN where it exists) sold to the HA crowd as 'won't get your account banned,' and treat ongoing maintenance as the actual product.
landscape (3 existing solutions)
Every path to controlling an LG appliance still routes through LG's cloud, which is now actively hostile to third-party polling. There is no reliable local or sanctioned-API route that exposes full appliance features without gambling your account, and Matter does not fill the gap.
LG ThinQ official cloud app / API Cloud-only and the source of the bans. The official developer API exists but is gated and oriented to vendors, not hobbyists wanting full local control of their own machine. Matter / Home Assistant native LG's Matter support covers only a thin slice of appliance functionality (on/off, basic status), not the cycle/notification/diagnostic detail people actually automate around. sources (1)
smart-homelocal-firsthome-assistantappliancesanti-cloud-lockin
Strava just removed its free API tier (the paid 'Standard' tier caps you at 10 athletes), breaking the third-party tools and self-hosters who relied on it to pull their own activity data. Cyclists and runners want a self-hosted system of record that ingests directly from Garmin/Coros/wearable FIT files without Strava sitting in the middle, plus an optional social layer. The young self-hosted trackers that exist mostly used Strava as a backfill source, which is exactly the bridge that just got cut.
builder note
Don't try to out-feature Strava. Win on being the no-API-rugpull system of record that pulls straight from Garmin/Coros/FIT files, with social as an optional layer, not the point.
landscape (3 existing solutions)
Several young self-hosted trackers exist but none is a polished, full Strava replacement, and the API change just severed the import bridge many of them depended on to backfill data.
Endurain ~2k stars but on a deliberate feature freeze to harden foundations; Garmin Connect integration exists yet direct device sync and social features are thin and immature. FitTrackee Minimalist and lightweight; relies on external bridge scripts (strava-to-fittrackee) to import activities, with no real social/training-feed layer. CubeTrek Built around hiking/GPS track storage, not the social training-log workflow runners and cyclists actually want from Strava. sources (1)
self-hostedfitnessstravadata-ownershipanti-subscription
People who self-host their ebook library with Calibre-Web and read on KOReader can finally sync reading position, but highlights and notes still live on-device or require a separate desktop app plus manual plugins, and progress desyncs across different file formats of the same book. The niche wants one system where annotations and progress follow the reader everywhere and surface back in the web library, without a cloud subscription.
builder note
Do not rebuild progress sync, KOSync already won that. The real gap is a normalized annotation model that survives a book changing formats and renders in the web reader. Build the highlights layer on top of the existing KOSync protocol rather than forking it.
landscape (4 existing solutions)
Reading-position sync is basically a solved, commodity piece now. Unified highlights and notes sync that survives format changes and surfaces inside a self-hosted web library is not, so readers still glue together three or four separate tools to approximate it.
KOReader Sync Server (KOSync) Syncs reading position only, and only between KOReader instances. No highlights, no notes, and nothing for Kindle or web readers. Calibre-Web-Automated Recently added KOReader progress sync, but not highlights or notes, and reading position desyncs across epub, kepub, and pdf copies of the same title. KOHighlights A separate desktop app for viewing and exporting KOReader highlights. Manual, not integrated into your web library, and not tied to progress sync. Readwise Polished highlight syncing but cloud-only, subscription-priced, and built around Kindle and web. Not your self-hosted KOReader library. sources (2)
self-hostedebookskoreadercalibre-webannotations
Privacy-conscious car owners reacting to fresh reporting on how much modern vehicles record and sell are trading DIY hacks on HN (pull fuse 8, yank the cellular/TCU bridge, flip flags in ForScan, even desolder the chips) and one says outright that he would pay for a professional version. They want a plain-language, cross-make tool or service that tells them what their specific vehicle collects and exactly how to disable it, software-only where possible, without breaking OTA updates, eCall, or other safety systems.
builder note
The defensible product is the per-VIN knowledge base plus a vetted local-shop or mobile-mechanic network, not a magic universal off switch. Lead with 'here is what you keep and what you lose on YOUR model' because the trap is that newer cars bake the modem into safety-critical modules with no clean disconnect, and promising total silence will get someone's eCall or ABS killed.
landscape (3 existing solutions)
Disabling car telemetry is possible but the how-to is splintered across brand forums and one-off diagnostic tools, with real risk of breaking safety or CAN-bus functions. Nothing gives a typical owner a safe, model-specific, step-by-step answer for their exact vehicle, and newer cars deliberately make the modem harder to isolate.
ForScan Ford/Mazda/Lincoln only, requires an OBD adapter and comfort editing module configs, throws persistent errors when the TCU is disabled, and kills FordPass / remote start in the process. Useless to the average owner and to anyone not driving a Ford. Privacy4Cars (Vehicle Privacy Report) Built around deleting personal data when you sell or rent a car and showing a transparency report of what a model collects. It does not stop the manufacturer's ongoing telemetry on a car you keep, which is the thing owners in the thread actually want shut off. sources (1)
privacyautomotiveright-to-repairtelemetrydata-brokers
Plex announced on May 19, 2026 that the Lifetime Pass goes from $249.99 to $749.99 on July 1, and the Remote Watch Pass jumps 50% on June 1, triggering an immediate exodus across Hacker News, r/selfhosted, and gaming/tech forums. The pain isn't the existence of Jellyfin, it's the day of lost watch history, broken Trakt sync, kid accounts re-set up, mobile clients reconfigured, and hardware transcoding profiles retuned. There's a five-week window to sell a fixed-price 'do my Plex-to-Jellyfin cutover this weekend' service that preserves every household's actual investment in the server they already own.
builder note
The product is a flat-fee weekend service with a checklist, not new software. The hard part is the long tail: HDR tone mapping on Intel QSV, Roku app pinning, the one Apple TV in the basement, kids' profiles with PIN restrictions, the Sonarr/Radarr stack already pointed at the Plex library. Sell trust and a clean Monday morning, not a tool.
landscape (4 existing solutions)
Migration tools exist but they're maintainer-hobby scripts, not turnkey concierge service. Nobody is selling 'send us your Plex token Friday, wake up Sunday on Jellyfin, kids and spouse still know how to watch Bluey, your NVIDIA transcoder still works' as a flat-fee product.
JellyPlex-Watched / wilmardo's migrate-plex-to-jellyfin Single-purpose CLI scripts that only port watched state, leaving user accounts, client configs, library naming mismatches, and hardware transcoder setup to the household. The owner still has to run a long-running command at 2am and pray nothing 404s. CrossWatch self-hosted sync engine Ongoing sync product, not a one-shot move. Solves the wrong problem for someone who just wants Plex turned off and Jellyfin turned on by Sunday night. Trakt + Jellyfin Trakt plugin Works when it works, breaks silently when episode-matching fails. Requires the user to already trust Trakt with their personal viewing history, which is the exact thing the Jellyfin-curious customer is trying to escape. Jellyfin official + community migration docs Documentation, not a service. Assumes the reader is the same person who set up Plex originally, which is often not true for households where one technical person installed it and the rest of the family just used it. sources (3)
plexjellyfinmedia-servermigrationself-hosted
Founders and indie hackers accumulate AppSumo lifetime deals bought on FOMO and annual SaaS subscriptions they never open, and there's no legitimate way to recover that money: the actual resale happens in sketchy Facebook groups with no escrow and no transfer verification. People keep asking for a real after-market for digital goods. The opportunity is a marketplace that handles escrow and, crucially, verifies whether a given license can legally be transferred at all.
builder note
The storefront is the easy 10%. The real product is license-transfer legitimacy: most SaaS terms forbid transfer outright, so build the vendor-by-vendor 'is this transferable, and how' database first. That compliance layer is the moat and the only reason a buyer trusts you over a Facebook group.
landscape (4 existing solutions)
Plenty of sites sell brand-new lifetime deals; the secondary market for already-owned licenses lives in trust-me Facebook groups with no escrow or transfer-legitimacy layer.
AppSumo Sells new lifetime deals but has no resale or transfer mechanism for deals a user already owns and no longer wants. sources (1)
marketplacesaaslifetime-dealsresaleescrow
Google's forced Gemini-for-Home swap has been a slow-motion disaster... users report 7-to-40-second delays on basic light commands, automations silently failing, garage-door cameras the assistant refuses to acknowledge, and routines that worked for years simply stopping. Reddit and Google's own forums are full of users asking how to revert. There is no official downgrade path, so a paid service that walks a household through factory-resetting devices, pinning firmware, locking accounts to the legacy Assistant path, and rebuilding routines from a YAML-style export would print money among the 'just turn my lights on' crowd.
builder note
Don't pitch yourself as a Home Assistant integrator... pitch yourself as 'we restore your old Google speakers to working order, remotely, in 30 minutes, $79.' The customer doesn't care that Google would prefer you didn't. Document each successful rollback as a public recipe to fuel SEO; Google has already conceded the marketing ground by shipping a broken upgrade.
landscape (3 existing solutions)
The market has either DIY power-user replacements or rebuy-everything migrations. Nothing serves the millions of households that just want their old Assistant back on the speakers they already own.
Home Assistant migration (DIY) Powerful, but the people losing 'turn on the bedroom light' are not the people who will set up Home Assistant on a Raspberry Pi. Wrong audience for a self-serve project. Apple HomePod / HomeKit Means rebuying speakers and re-pairing every smart device. Not a soft path for someone who has six Google speakers and a Nest doorbell. sources (4)
google-homegeminismart-homeconciergedowngrade
Matter-over-Thread devices fail at commissioning when a household has multiple Thread Border Routers from different vendors that refuse to extend the same Thread network. Home Assistant users keep posting failed-pairing logs and the fix is currently 'unplug everything and pray.' The opportunity is a Home Assistant addon (or standalone tool) that maps the actual Thread network state across vendors, identifies fragmented partitions, and offers a guided heal — plus a watchdog that flags partition splits before they break devices.
builder note
Start as a Home Assistant addon that just SHOWS the truth (active partition IDs, which devices joined which router, which routers are refusing to share credentials) and ship the heal flow in v2. The visualization alone will get installs because half the value is being able to say to your spouse 'see, this is why it broke' instead of 'computer says no.'
landscape (3 existing solutions)
Everyone affected can identify the problem (partition split, vendor refuses to share) but no single tool maps it across the household. The fix today is folklore on community forums.
ot-ctl / OpenThread debug CLI Diagnostic-grade but command-line, useless to a normal user trying to figure out why their new Aqara plug won't pair sources (4)
smart-homethreadmatterhome-assistantdiagnostics
Standard SaaS contracts price by seats. They have no language for per-agent attribution, usage ceilings, audit rights, or customer-side budget caps that hard-stop the vendor's meter before the vendor's meter hard-stops them. Procurement teams about to sign the next batch of renewals at ServiceNow, Workday, HubSpot, Salesforce, and SAP need a productized template kit: redline-ready clauses, a vendor-question checklist ('what is your roadmap for agent metering?'), and a benchmark table of what other companies have negotiated.
builder note
Sell this as a one-time PDF + Notion template pack, not a SaaS. Procurement people will pay $499 for a doc that prevents a $50K mistake on the next renewal. The trap is trying to be the legal tool itself. Be the boring, lawyer-reviewed checklist that gets emailed around as the standard.
landscape (3 existing solutions)
Multiple major analysts within the last two weeks have explicitly prescribed exactly this product (cloud-style committed-spend clauses for SaaS). The first credible template pack with named procurement leaders endorsing it becomes the de-facto reference. Distribution: FinOps Foundation, ProcureCon, CFO podcasts.
Vendr / Tropic / Sastrify advisory Help you negotiate seat-shaped contracts. Their playbook is still pre-tollgate. The agent-action clauses don't exist in their template library yet. sources (4)
procurementsaas-contractsfinopsai-agentstollgate
Broadcom's VMware re-bundling has produced reported 150–1200% cost increases, with vSphere Foundation now around $4,500/CPU/year. Proxmox is free and the technical migration path (Veeam restore, virt-v2v, ESXi import in Proxmox 8.x) works — but it requires hypervisor expertise no five-person law firm or dental office actually has. MSPs serving SMB are getting flooded with migration requests, and there's no shrink-wrapped 'plug this USB stick in, click two buttons, get an inventory + migration plan' product aimed specifically at the 3-5 host shop.
builder note
The wrong move is to white-label Proxmox and add a control plane. Proxmox's own UI is fine. The right move is to be the migration-day partner: pre-flight inventory, license reconciliation, customer-facing comms templates, and a Sunday-night Slack channel with a real human. Sell the assurance, not the bits.
landscape (3 existing solutions)
The technology is mature and free. The packaging is missing. The opportunity is a $999 'Proxmox SMB Kit' — a USB stick + scripted inventory tool + remote office-hours support — that lets an SMB IT generalist execute the move in a weekend. Whoever owns this category becomes Acronis-for-Proxmox.
Proxmox built-in ESXi importer Functional but assumes admin comfort with CLI, networking topology, and storage planning. SMB IT folks (often the 'most technical person at the firm') aren't hypervisor admins. Boutique consultants Available, but priced as project work. SMBs want a fixed-price packaged outcome, not a T&M engagement. sources (3)
virtualizationsmbvmware-escapeproxmoxmsp
The Xteink X4 is getting a flourishing community-firmware ecosystem (CrossPoint, CrossPoint++, Inkpot) that delivers KOReader sync, better typography, and freedom from the stock Chinese-cloud OS, but most buyers are scared to flash. There's a real opportunity for a concierge service that sources hackable e-readers, ships them with the chosen open firmware preinstalled, offers a one-year hardware warranty, and provides email support. Plus: a public 'open-firmware-friendly e-reader' buyer's guide.
builder note
This is a System76-shaped business, not a software product. Margin comes from support and warranty, not the install. Start with one model (Xteink X4 + CrossPoint) and one firmware variant. Don't try to be a marketplace.
landscape (3 existing solutions)
Open-firmware e-readers are entering the long-tail-of-1k-buyers stage where Linux laptops were before System76. Nobody is selling preflashed-with-warranty units. Enthusiasts will install themselves, but the curious-but-not-confident buyer (10x larger market) has nowhere to spend $250 with peace of mind.
PineNote Tinkerer-only product; no warranty, no preinstall service, frequently out of stock Boox Page/Note Locked Android variant; community sideloading but no clean open-firmware path sources (4)
e-readeropen-firmwareright-to-repairkindle-alternativeconcierge-service
Adult kids of recently-burgled elderly parents are discovering that SimpliSafe, Ring, ADT, and Frontpoint all assume the homeowner has a smartphone, knows what 'arming a sensor' means, and doesn't panic when the alarm panel announces 'sensor 4 open' at 3am. They want a concierge service that ships a kit, installs it in person, and configures it for an 80-year-old: physical key fob arm/disarm, no app required, calls the adult kid (not the resident) when something trips, and human-monitored false-alarm filtering.
builder note
This is not a hardware company. White-label SimpliSafe or eufy hardware, charge $399 install plus $25/month, and route alerts to the adult child by default. The customer is the adult kid with a credit card and a guilty conscience, not the resident. Sell it where they Google: 'mom got robbed how to set up security'.
landscape (3 existing solutions)
Every consumer brand has a senior-friendly *page* and a key-fob *option*, but none ship as a packaged 'I just got robbed and my mom is 80' service. The product gap is the install service plus the elder-routing rules, not the hardware.
SimpliSafe Self-install from a flat box, app-first. The whole onboarding flow assumes a 35-year-old smartphone user. ADT Has key fobs and pro install but is sold as a 36-month $1000+ contract aimed at homeowners, not a $400 'set up your mom' kit. Also the modern ADT app upsells inside the home screen. Bay Alarm Medical Medical-alert focus (fall detection, button-press). Not actually an intruder/burglary system. sources (1)
seniorssecurityconciergeservicefamily-care
A growing cohort of parents is deliberately keeping kids off smartphones into their tweens but still needs to summon them when running errands. They want a one-tap, no-account light-and-chime puck that sits on a kid's bookshelf and lights up when a parent presses a button from anywhere. No subscription, no kid-side account, no GPS watch — just a 'come to the phone' or 'come home' cue.
builder note
The hardware is the easy part... ESP32 + LED ring + buzzer + LTE-M or Wi-Fi callback. The product win is the brand and the parenting narrative... 'a smartphone-free way to call your kid home.' Sell as a 2-pack with one parent button + one kid puck for $79, no subscription, and you'll out-position Gabb on the values dimension every parent in this thread is screaming about.
landscape (3 existing solutions)
Every existing solution puts a device or account on the child. Nothing exists as a clean SKU for a passive, account-free, parent-controlled summon-light.
Gabb Watch Kid-wearable with monthly subscription. Still gives the kid a wearable device, which is exactly what these parents are avoiding. Bark Watch Same pattern as Gabb. Surveillance-and-call wearable, not a passive room signal. Amazon Echo Drop In Requires Alexa account on the kid's side, full-duplex audio, and is not a discrete 'come here' cue. Parents in the thread say it feels invasive. sources (1)
parentingiotkidsanti-smartphonehardware
Homeowners moving into older houses keep running into the same pain... no labeled breaker panel, no idea which switches control which lights, no map of low-voltage runs or abandoned wiring in the walls. r/homeautomation thread asking 'what if there was a service where some dude shows up, runs tests, and hands back a document' hit 90 comments with enthusiastic demand. This is a local-services-plus-software play... field tech walks the house with a kit (breaker finders, toner probe, thermal camera, WiFi-enabled signal injector), the app logs results room-by-room, output is a searchable map the homeowner keeps forever. Also valuable to electricians and home inspectors as a deliverable.
builder note
This is a services business wearing a software skin. Launch in one metro with one contracted field tech, nail the deliverable (interactive room-by-room map plus PDF), then license the app and kit to home inspectors as a $20/report add-on. The smart-home crowd will pay you directly, but inspectors are the distribution channel that scales.
landscape (6 existing solutions)
Homeowners have a gazillion single-purpose tools and a labor market for electricians but no productized 'map my house' service with a durable digital artifact. The win is packaging the field kit and the app so a non-electrician (handy neighbor, home inspector, property manager) can deliver an 'electrical + network + smart-home topology' report in half a day, priced $200-400 per house.
Sense energy monitor Panel-level load disaggregation. Identifies appliances over time, not 'which switch runs which fixture.' Span Panel Smart electrical panel with per-circuit monitoring. $3,500+ plus installation... replaces your panel rather than mapping the house you already have. Home Assistant + manual YAML What the r/homeautomation crowd does. Enormous DIY tax, no standardized schema for the house itself as a document. Home inspection reports Cover safety/compliance at purchase. Not a maintained living document of the house's electrical and LV topology. sources (2)
home-automationsmart-homeelectricalservice-plus-softwarehomeowner
Home Assistant dominates local smart home with 600K+ installations and 2000+ integrations, but non-technical homeowners consistently bounce off its complexity. Cloud-dependent alternatives are increasingly risky as subscription creep grows and cloud startups brick devices when they go bankrupt. Gladys Assistant positions itself as simpler but has a fraction of HA's integrations. The demand is for something between a single-brand app and Home Assistant's everything-but-the-kitchen-sink approach.
builder note
Do not try to out-feature Home Assistant. Pick the 20 most common devices (Hue, Ring alternatives, Ecobee, smart plugs) and make them work perfectly with zero configuration. Ship as a dedicated hardware hub with a phone app. The business model is the hardware margin, not a subscription. That's the whole point.
landscape (3 existing solutions)
Home Assistant is too much. Brand-specific apps are too little. The middle ground for normal homeowners who just want lights, locks, and thermostats to work locally without learning YAML or Docker doesn't really exist. Cloud startups going bankrupt and bricking devices makes this gap increasingly urgent.
Home Assistant Incredibly capable but the learning curve and YAML-editing reputation deter non-technical homeowners. 600K installs means millions more bounced off. Gladys Assistant Genuinely simpler with zero-cloud philosophy but tiny integration library compared to HA, limiting practical usefulness Hubitat Local processing hub but proprietary, limited integration ecosystem, and the UI feels like enterprise software from 2010 sources (3)
smart-homelocal-firstno-cloudprivacyiot
Navidrome and Jellyfin let you stream your own music library from a home server with privacy and FLAC quality. But the biggest thing missing is music discovery: no 'you might also like' recommendations, no radio stations, no friend activity, no shared playlists. Spotify's algorithm is the primary reason people stay despite privacy concerns. Users want to own their music AND discover new music without feeding their listening habits to a corporation.
builder note
Don't build another music server. Build a recommendation plugin for Navidrome. Use MusicBrainz metadata + Last.fm's public artist similarity data + local audio feature extraction (librosa or Essentia) to generate 'Daily Mix' style playlists from the user's own library. Ship as a Navidrome companion service that runs alongside it. The Subsonic API gives you access to the library. The recommendation engine is the product. If it works, Navidrome might integrate it upstream.
landscape (4 existing solutions)
Self-hosted music streaming solved the playback and library management problem (Navidrome is excellent). But it completely ignores discovery, which is Spotify's real product. The missing piece is a recommendation engine that runs locally: analyze your library's audio features and metadata, suggest similar artists from MusicBrainz/Last.fm data, and generate smart playlists without sending listening habits to any server. Open-source audio fingerprinting and local ML models make this technically feasible in 2026.
Navidrome Best self-hosted music server with Subsonic API compatibility, multi-user support, and low resource usage (runs on Raspberry Pi). But zero music discovery features: no recommendations, no radio, no similar artist suggestions. Your library is a static collection you manage manually. Jellyfin (Music) Full media server with music support alongside movies and TV. But music is a secondary feature. No dedicated music discovery, no smart playlists based on listening patterns, no scrobbling integration out of the box. The music UX is generic media browser, not a music-first experience. Funkwhale Federated music platform with social features (follows, favorites, shared libraries). Closest to adding social discovery to self-hosted music. But development has slowed significantly, the instance count is declining, and federation creates complexity without providing Spotify-like algorithmic recommendations. Spotify Gold standard for music discovery with personalized Daily Mixes, Release Radar, and collaborative playlists. But $11.99/month, collects extensive listening data, pays artists fractions of cents, and you own nothing. Cancel and your playlists vanish. sources (3)
musicself-hostedprivacydiscoverystreaming
SearXNG is the go-to self-hosted metasearch engine, querying 70+ upstream providers. But its default configuration is described as 'total trash' by its own users, single-user instances create a privacy paradox (your IP is uniquely identifiable to upstream engines), and there's no cross-device sync. DeGoog is simpler but also lacks sync. Users want Google-quality results without Google-quality surveillance, and they want it to just work out of the box.
builder note
Fork SearXNG and ship it with three curated engine profiles: 'Developer' (Stack Overflow, GitHub, MDN weighted), 'General' (mixed engines tuned for quality), and 'News' (RSS feeds + news engines). Solve the single-user privacy problem by running a shared SearXNG relay that mixes queries from multiple self-hosted instances. The relay is your SaaS upsell. The self-hosted instance is your distribution.
landscape (4 existing solutions)
Self-hosted search exists but requires expertise to configure well. SearXNG is powerful but ships with bad defaults. The privacy paradox (single-user instances are uniquely identifiable) undermines the core value proposition. Nobody has built a self-hosted search engine that ships with curated, tested configurations for different use cases (developer, general, news) and solves the single-user privacy problem, perhaps via a community relay network.
SearXNG Most configurable metasearch engine with 70+ providers. But default config yields poor results requiring extensive tuning. Single-user instances defeat the privacy model (your searches aren't mixed with others). DuckDuckGo CAPTCHAs block frequent single-IP queries. No bookmark sync or search history across devices. DeGoog Simpler multi-engine aggregator with clean UI and optional AI summaries. But no cross-device sync, no saved searches, single-developer project with uncertain sustainability. Performance is slower than direct engine queries. Brave Search Independent index (not a metasearch), good quality, privacy-respecting. But cloud-hosted by Brave, not self-hostable. Users who want to control their search infrastructure can't use it. Whoogle Self-hosted Google proxy that strips tracking. But entirely dependent on Google's results and rate limiting. Google actively blocks proxy instances. Fragile and frequently breaks. sources (3)
privacysearchself-hosteddegoogleanti-surveillance
Nextcloud is the default recommendation for self-hosted file sync but its complexity and resource hunger frustrate non-technical users. It requires PHP, a database, Redis, and ongoing maintenance. Lighter alternatives are emerging (OpenCloud in Go, bewCloud in Deno, Seafile for pure sync) but none offers a true one-click NAS or VPS install with automatic updates. The gap is Dropbox simplicity with self-hosted privacy.
builder note
Don't compete with Nextcloud on features. Compete on simplicity. Build a single-binary Go application that serves WebDAV + a clean web UI + mobile auto-upload. Ship install scripts for Synology, Unraid, and TrueNAS. The NAS community is your distribution channel. They already have hardware. They just need software that doesn't require a CS degree to install.
landscape (4 existing solutions)
Self-hosted cloud storage is dominated by Nextcloud, which tries to do everything and frustrates users with complexity. Lighter alternatives (OpenCloud, Seafile, bewCloud) solve the performance problem but not the UX problem. Nobody offers a truly plug-and-play self-hosted file sync: install on your NAS or VPS in one click, automatic HTTPS, automatic updates, mobile auto-upload, and selective sync. The Synology/QNAP crowd would pay for this.
Nextcloud Most feature-rich self-hosted suite with 400+ apps. But PHP stack requires database, Redis, and web server configuration. Updates frequently break. Resource-heavy. Trying to be everything (office suite, calendar, chat, photos) makes the core file sync unreliable for some users. OpenCloud (ownCloud Infinite Scale) Rewritten in Go with dramatically lower memory usage and faster performance than Nextcloud. But ownCloud's acquisition by US-based Kiteworks raises sovereignty concerns. Smaller app ecosystem. Still requires Docker or manual binary deployment. Seafile Block-level sync handles large files better than anything else. Runs on Raspberry Pi. But file sync only, no office suite, no calendar, no contacts. If you need more than sync, you need additional services. bewCloud TypeScript/Deno stack, genuinely simple codebase. But very early stage, single developer, limited feature set. No mobile apps. More of a proof of concept than a production tool. sources (3)
self-hostedcloud-storagefile-syncprivacyNAS