← statichum.studio

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.
Veeam Backup & Replication / virt-v2v Aimed at enterprise. Licensing math doesn't fit a 5-host shop. Setup time alone exceeds the savings for the smallest tier.
Boutique consultants Available, but priced as project work. SMBs want a fixed-price packaged outcome, not a T&M engagement.
sources (3)
other https://www.starwindsoftware.com/blog/vmware-migration-to-pr... "VMware Migration in 2026: Proxmox, KVM, XCP-ng & Veeam" 2026-03-15
other https://www.libertycenterone.com/blog/4-vmware-alternatives-... "customers reporting net increases of 150% to 1,200%" 2026-04-08
other https://tech-insider.org/proxmox-vs-vmware-2026/ "Proxmox VE saves $44,000+ annually on a 10-host deployment" 2026-03-28
virtualizationsmbvmware-escapeproxmoxmsp

ReciMe jumped to ~$10/mo or $59.99/year and capped its free tier at 5 recipes in early 2026, lighting up Reddit threads and triggering a wave of escape-attempt posts. The structural lock-in is that ReciMe (and Paprika, and Plan-to-Eat, and AnyList) all import recipes from social videos and blog posts but don't export their structured library to each other. Users with 200+ saved TikTok recipes face manual re-entry. Existing 'free ReciMe alternative' posts mostly pitch their own app, not a portability tool.

builder note

Don't take the 'build my own recipe app' bait. The hard, valuable bit is the TikTok/Instagram re-derivation step (the original page often paywalls or removes the recipe). Lean into ASR + a small LLM to reconstruct ingredients/steps from saved video stills... and charge $10 one-time, not subscription, since the whole audience is fleeing one.

landscape (3 existing solutions)

The recipe-app space competes on import features but treats export as a moat. A small, opinionated migrator — point it at your ReciMe account, watch it walk every saved video, OCR/transcribe what's needed, and emit a Paprika-or-Mealie-shaped library — would be loved by exactly the bookmark-rich users who feel most ripped off by the price hike.

Paprika web clipper Excellent at importing from blog URLs. Cannot ingest a ReciMe library export — ReciMe doesn't expose one.
Plan to Eat / AnyList / Deglaze imports Each accepts a few competitors' formats but not all. None handles the TikTok/Instagram-saved video portion of a ReciMe library, where the source URL no longer renders the original recipe metadata.
ReciMe export feature ReciMe offers no structured library export. Users have to screenshot or hand-copy each saved recipe.
sources (3)
other https://www.recipeone.app/blog/recime-app-review "Reddit threads are filled with users looking for alternatives after the price changes" 2026-04-12
other https://recipenotes.app/free-recime-alternative "monthly pricing jumping to approximately $9.99/month" 2026-03-22
other https://www.facebook.com/groups/935086413269446/posts/872938... "Paprika 3 vs Deglaze vs ReciMe alternatives?" 2026-04-08
recipesdata-portabilitysubscription-escapeconsumervendor-lock-in

After the Axios npm worm, the SAP 'Mini Shai-Hulud' campaign, and the litellm/telnyx PyPI compromise, individual package managers are racing to add release-cooldown features. The problem: pnpm calls it minimumReleaseAge, npm calls it npmMinimalAgeGate, uv uses --exclude-newer, pip 26.1 ships another name, Cargo and Bundler each have their own. Andrew Nesbitt counted at least ten different config names. Polyglot repos (ML + frontend, backend + agent runners) have to set the same '3-day delay' policy in five places, with no unified way to audit drift.

builder note

Don't try to be a security platform. Be a 30-line YAML at the repo root and a CLI that prints the diff between intent and reality across all five package managers. Make it boring and Unix-y. Distribute via Homebrew, Cargo, pipx, and npx all at once... eat your own dogfood.

landscape (4 existing solutions)

Every individual package manager is solving its corner of the problem. None aggregates. A cross-ecosystem CLI/config (`cooldown.yml` at repo root) that translates one human policy into npm + pip + cargo + gem + bundler-shaped configs — and nags on drift — would be a small-but-painful tool that polyglot teams adopt instantly.

pnpm minimumReleaseAge Node-only, defaults are excellent, but no relevance to a repo that also installs Python or Rust packages.
uv --exclude-newer Python-only, configured per-project in pyproject.toml. Doesn't see the Node side of the same monorepo.
Dependabot cooldown groups Solves PR-creation cadence, not install-time blocking. Doesn't protect a developer running `npm i` directly.
StepSecurity / Snyk policy engines Enterprise-priced, focused on org-wide policy enforcement at CI gate. Solo devs and small teams won't deploy them.
sources (4)
other https://nesbitt.io/2026/03/04/package-managers-need-to-cool-... "at least ten different configuration names across the tools that do support it" 2026-03-04
other https://blog.pypi.org/posts/2026-04-02-incident-report-litel... "credential harvesting malware that ran on install" 2026-04-02
other https://www.theregister.com/2026/04/30/supply_chain_attacks_... "ongoing supply chain attacks worm into SAP npm packages" 2026-04-30
other https://docs.bswen.com/blog/2026-04-02-uv-exclude-newer-supp... "How to Use uv exclude-newer for PyPI Supply Chain Security" 2026-04-02
supply-chainpackage-managerspolyglotsecurityconfig-drift

Reddit completed the deprecation of r/all in April 2026, replacing the unfiltered firehose with an algorithmic Home/Popular feed. Power users on Reddit, Bluesky, and tech press are openly mourning the loss of the platform's last uncurated front page — old.reddit.com is the only remaining workaround and Reddit hasn't promised that survives long. There's an opening for a third-party 'real r/all' surfacer that pulls genuine cross-subreddit upvote velocity (no personalization, no engagement bait) the way redditors actually used to discover content.

builder note

Don't build it as a standalone site that has to talk to Reddit's API on every page load — Reddit will rate-limit you out of existence. Make it a browser extension that hits old.reddit.com using the user's own session, decorates the result with cross-subreddit aggregation client-side, and writes nothing back to a server. Zero infra cost, zero API politics.

landscape (3 existing solutions)

The cheap version of this is a public site that hits Reddit's `/r/all/.json?sort=hot` endpoint and renders without personalization. The trick is doing it sustainably under Reddit's API limits (and political mood) — likely via OAuth-the-user, browser-extension-as-aggregator, or scraping old.reddit while it lives. Whoever builds a stable home for 'just show me what's actually upvoted' will inherit the disenchanted power-user crowd.

old.reddit.com/r/all Workaround dependent on Reddit not killing the legacy site. Reddit has signaled this could go away. No mobile parity.
Reddit's official Home/Popular feed Algorithmic. Personalizes against the user, optimizes for engagement and ad-safety, not raw upvote signal. Exactly what r/all was supposed to NOT be.
Lemmy / Bluesky / Digg-2024 Different platforms with different content. Don't help redditors who want to watch what real-Reddit communities are upvoting.
sources (4)
other https://www.themeridiem.com/consumer-tech/2026/4/2/reddit-ki... "Reddit completes shift to algorithmic control" 2026-04-02
other https://www.techbuzz.ai/articles/reddit-kills-r-all-feed-to-... "kills r/all feed to push algorithmic personalization" 2026-04-03
other https://www.webpronews.com/reddit-kills-r-all-the-quiet-deat... "the internet's last uncurated front page" 2026-04-04
other https://www.techradar.com/computing/social-media/reddit-is-c... "still a way to access it if you know how" 2026-04-05
redditdiscoveryalgorithm-freepower-usersanti-personalization

AI-generated recipe slop has overrun Pinterest, Google AI Overviews, and Facebook reels — Defector, Fortune, NPR, and food bloggers themselves are sounding the alarm in 2026. Real cooks (Inspired Taste, Budget Bytes, Smitten Kitchen) are losing search traffic to LLM mashups. Existing recipe apps focus on saving recipes you already have, not on solving discovery in a poisoned search environment. The gap is a curated, verifiably-human-tested directory: a cook's photo, a reproducible test-kitchen note, a comment thread that actually works.

builder note

The temptation is to build another recipe site. Don't. Be the verification layer — a registry + JSON-LD schema + browser extension badge — and let the existing real cooks adopt it. Chrome users hover over a recipe link and see 'Verified human cook, tested 2026-04-12 by Smitten Kitchen.' That's the wedge.

landscape (3 existing solutions)

Recipe apps and AI detectors both exist. Neither is a curated, identity-verified directory. The category is wide open for a 'Snopes-for-recipes' aggregator that pays small stipends to verified cooks, attaches their face to every recipe, and ranks by reproducible test-kitchen evidence.

Paprika / Plan to Eat / Recipe Notes / Drizzlelemons All are personal recipe managers — they help you save and organize, they don't solve discovery or provenance. They happily import an AI-generated recipe.
Budget Bytes / Inspired Taste / Smitten Kitchen (individual blogs) Trusted but isolated. No shared 'verified human, tested in a real kitchen' badge that crosses sites. Search engines can't tell them apart from slop farms.
Skipslop browser extension Generic AI-content blocker, not recipe-specific, no provenance signal — purely a negative filter, not a positive index.
sources (4)
other https://defector.com/glossy-gunky-and-ready-in-minutes-ai-me... "Glossy, gunky and ready in minutes" 2026-02-12
other https://www.npr.org/2026/01/25/nx-s1-5680290/adam-gallagher-... "the dangers of AI-recipe slop" 2026-01-25
other https://www.fromachefskitchen.com/ai-generated-food-content/ "damaging food creators' businesses while causing consumers to waste time and money" 2026-03-04
other https://searchengineland.com/google-ai-slop-thanksgiving-foo... "Google and AI slop are ruining Thanksgiving for food bloggers" 2025-11-23
ai-sloprecipestrust-and-provenanceconsumersearch

Multiple HN devs in the December 2025 'developer tool you wish existed in 2026' thread asked for a Source-Insight-style code reader: open a function in window A, click any callee, the new window pops with proper highlighting, struct definitions stick to the bottom, all panels stay open at once. Source Insight is paid Windows-only. Crabviz is LSP-aware but VS Code-only and just renders graphs. Sourcetrail is unmaintained. Source-Navigator NG is dated. Nothing combines persistent multi-pane navigation + LSP language-agnosticism + Linux-native + free.

builder note

Tauri or GTK4 + tree-sitter for incremental highlighting + any LSP backend the user already has installed. Don't re-implement parsers... lean on the LSPs already on the dev's machine. Ship it as a single binary that opens to a shortcut launcher of recent functions, not yet another sidebar plugin.

landscape (5 existing solutions)

The space is littered with half-tools: each gets one axis right (LSP, multi-language, Linux, free, multi-pane, interactive) but never all of them at once. The exact UX a kernel-source reader wants — a tiling-window 'browser for code' — doesn't exist on Linux as a free LSP-driven app.

Crabviz VS Code-only, generates static call graphs, doesn't have the multi-pane stay-open exploration UX. Useful for one-off graph rendering, not for sitting in the codebase reading it.
Sourcetrail The closest spiritual successor, but the company shut down and the project is unmaintained. New language support requires forks. No active LSP wiring.
Source-Navigator NG Pre-LSP era. Custom parsers, limited language coverage, dated UI, sporadic maintenance.
Understand by SciTools Excellent UX but commercial, expensive seat license. Useless for hobbyist OS-source-reading like xv6 or Linux kernel.
Woboq Code Browser Web-only, static HTML, C/C++ focus. Designed for reading published source on a website, not interactive in-IDE exploration.
sources (3)
hn https://news.ycombinator.com/item?id=46345951 "VSCode Peek definition but with a different visual style... source insight but free and in Linux" 2026-02-09
hn https://news.ycombinator.com/item?id=46352468 "experimented with this... using the Language Server Protocol to make it somewhat universal" 2026-02-10
other https://alternativeto.net/software/source-insight/?platform=... "best Linux alternative is Understand. However, it's not free" 2026-04-10
code-readinglsplinuxdeveloper-toolsopen-source

Atlassian stops new Data Center license sales on March 30, 2026, MQB peak-headcount billing has rolled out to monthly Cloud subscribers, and renewals are reportedly jumping 119–153% per Atlassian's own community forums. The 'Atlassian Ascend' migration program is built to funnel Data Center users onto Atlassian Cloud, not let them leave the ecosystem. Teams that want to land on Plane, Outline, GForge, or self-hosted Confluence forks have to stitch together half-finished open-source importers that drop comment history, sprint state, and granular permissions on the floor.

builder note

Don't pick a target product (Plane, Outline, etc) — be the source-side intermediate. Output a structured 'Jira-IR' (intermediate representation) JSON that any target can ingest, and partner with the destination tools to claim the assist. The MSP and consultancy channel will pay for this; end customers won't.

landscape (3 existing solutions)

Atlassian invests heavily in Cloud migration tooling. Off-Atlassian destinations exist but have shallow importers focused on attracting greenfield teams, not preserving a decade of Jira metadata. The integration math gets ugly fast for any single vendor to own — which is exactly why an independent migrator could charge real money.

Atlassian Ascend Designed exclusively to push Data Center customers onto Atlassian Cloud. Useless for teams trying to actually leave.
Plane Notion/Confluence/Linear importers Each importer is one-shot and one-source. None handle Atlassian Data Center directly. Custom-field mapping, attachments, and history get truncated.
Outline import flows Wiki-shaped tools assume documents, not issue trackers. Sprint state, board view, and JQL automations have nowhere to go.
sources (4)
other https://community.atlassian.com/forums/App-Central-articles/... "your bill now ties to peak usage, not end-of-month headcount" 2026-02-10
other https://www.onpointserv.com/post/atlassian-data-center-price... "legacy Advantaged pricing increases range from 18% to 40%" 2026-02-04
other https://plane.so/blog/11-jira-alternatives-you-can-self-host... "11 Jira alternatives you can self-host" 2026-04-08
other https://gforge.com/atlassian-alternative/ "Best Atlassian Alternative 2026" 2026-03-30
atlassianjiramigration-toolself-hosteddata-center-eol

GummySearch shut down November 30, 2025, after Reddit denied it API access, leaving 140,000+ founders and indie hackers without a way to do affordable subreddit pain-point mining. The replacements are either narrow keyword pingers (F5Bot), enterprise-priced (Octolens, Awario), or thin AI overlays scraping the same data. Nothing replicates the original 'curate a list of subreddits, see distilled pain points and trends' loop at the price point indie founders can stomach... because Reddit's official API tier is the bottleneck.

builder note

Don't try to be GummySearch v2. The cost-of-API moat killed the original. Build it as a 'subreddit researcher' that aggressively caches Pushshift-mirror data and lets the user point it at their own approved Reddit OAuth credentials for live updates... that pushes the cost-per-user back onto the user's rate limit, not your AWS bill.

landscape (4 existing solutions)

The structural reason no one has fully replaced GummySearch is that Reddit's enterprise API tier costs more than a $29/mo indie tool can sustain. Anyone re-entering this market has to solve the API economics first... by either federating with subreddit mods, batching to fit free-tier limits, or running on Pushshift-style historical data plus Bluesky/Lemmy mirrors.

F5Bot Free, but it's strictly keyword email alerts. No subreddit clustering, no pain-point summarization, no audience demographic view.
Syften Multi-platform keyword monitoring (Reddit + HN + IH + 15 others) but priced for B2B SaaS marketing, not solo indie founders. No pain-point ranking.
PainOnSocial Closer in spirit but skews toward 'we'll do the research for you' deliverables instead of letting a founder explore subreddits themselves. Limited subreddit catalog.
Octolens Strong on GitHub + HN, weaker on Reddit. Pricing aimed at funded SaaS, not bootstrappers.
sources (3)
other https://reddinbox.com/blog/best-gummysearch-alternative "GummySearch is gone... over 140,000 founders, marketers, and indie hackers used it" 2026-03-15
other https://devtoolpicks.com/blog/best-gummysearch-alternatives-... "nothing in 2026 replaces it exactly" 2026-04-22
other https://reddily.io/blog/gummysearch-alternatives "no new tool can legally replicate exactly what it did at the same price point after Reddit's API changes" 2026-03-20
indie-hackersdemand-researchreddit-apiaudience-toolsfounder-tools

Rackspace cranked email pricing from $2.99 to $10/mailbox in January 2026, with some reseller bundles hitting a 706% jump and contract-day fury all over r/rackspace and Web Hosting Talk. The painful piece isn't the IMAP-to-IMAP move (tools exist); it's that small IT shops resell to dozens of micro-businesses, each with their own DNS, autodiscover, mailbox aliases, calendar shares, and 27-year-old shared mailboxes. They need a turnkey reseller-aware migrator that maps customers in bulk, not another single-tenant 'switch to us' wizard.

builder note

MSPs aren't going to pay $50/mo SaaS for this... they want a flat per-mailbox bounty, like $1.50/mailbox, with white-label customer email templates. Pricing the obvious way (per-seat subscription) is how every existing tool already missed this market.

landscape (3 existing solutions)

Plenty of consumer-grade IMAP-copy tools exist. Zero of them are aimed at MSPs and email resellers who need fleet-scale orchestration: pre-flight DNS audit, customer comms templates, parallelized cutover, and post-move spam/deliverability validation.

SysTools IMAP-to-IMAP Migrator Single-mailbox-at-a-time tooling. No reseller-orchestration layer, no DNS cutover automation, no per-tenant billing reconciliation. Resellers running fifty client domains have to babysit each migration manually.
BitRecover / Adviksoft Rackspace migrators Functional but assume an admin doing one tenant at a time on a Windows desktop. They don't handle the reseller's catalog, customer notification, calendar/shared-mailbox topology, or autodiscover/DKIM cutover in batch.
Rackspace's own migration page Pitches Office 365 transformation services (Rackspace upselling to itself). Not relevant for resellers trying to leave the Rackspace ecosystem entirely.
sources (4)
reddit https://www.reddit.com/r/rackspace/comments/1qd0nee/comment/... "monthly bill just went from $2,400 a month to $5,100 a month" 2026-01-19
reddit https://www.reddit.com/r/rackspace/comments/1qd0nee/comment/... "this is how they treat long-term clients?" 2026-01-19
other https://www.theregister.com/2026/01/20/rackspace_price_chang... "400 percent price increase with little over a month's notice" 2026-01-20
other https://www.webhostingtalk.com/showthread.php?t=1953149 "464% price increase announced today" 2026-01-15
mspemail-hostingmigration-toolvendor-lock-insmb

Oracle is shutting down GloriaFood on April 30, 2027, with no successor product, no data retention, and a long tail of independent restaurants and white-label partners who built years of menus, customer profiles, and POS/webhook plumbing on top of it. Existing GloriaFood-replacement vendors want to sell their own SaaS, not migrate the customer cleanly off vendor lock-in entirely, so there's a gap for a vendor-neutral migrator that exports the schema, replays it onto a self-hostable or commission-free stack, and rewires the printer/POS connections.

builder note

The trap here is building yet another ordering platform. The actual leverage is being the Switzerland-of-migration: charge a flat per-location fee, output a tarball of menus + customer CSVs + a Cloudflare Worker that proxies the old GloriaFood iframe URLs to wherever they land. Whoever owns the off-ramp gets to refer the operator to whatever platform pays the best kickback... that's the real business model.

landscape (2 existing solutions)

Every alternative in the comparison guides is a competing platform pitching itself, not an exit tool. The actual painful work — exporting menus, photos, customer profiles, hours, modifiers, webhook URLs, and POS bindings, then replaying them onto a chosen target — is something every restaurant has to figure out alone.

Deonde / Hyperzod / Flipdish / UpMenu / Restolabs All of these are replacement SaaS platforms, not migrators. Each wants the operator to sign up to their own stack and re-enter menus, photos, and customer data manually. Nothing automates the export-and-replay step or carries forward the existing iframe/POS/printer integrations.
Oracle GloriaFood self-export Oracle has explicitly confirmed no archival service beyond April 30, 2027. The platform is feature-frozen and there is no first-party migration tooling planned.
sources (3)
other https://beststartupbusiness.wordpress.com/2026/05/07/why-glo... "operators rethinking how they build their digital infrastructure" 2026-05-07
other https://www.icoderzsolutions.com/blog/what-to-do-after-glori... "menus, customer records become permanently inaccessible" 2026-04-15
other https://www.enacton.com/blog/gloriafood-shutting-down/ "rip and replace everything... no successor product" 2026-04-10
restaurant-techvendor-shutdowndata-portabilitysmbsaas-escape