<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mohit || Dev</title>
    <description>The latest articles on DEV Community by Mohit || Dev (@mohitdebian).</description>
    <link>https://dev.to/mohitdebian</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1342509%2F88f9f8ac-5d92-4416-bae1-724e94bcab5f.png</url>
      <title>DEV Community: Mohit || Dev</title>
      <link>https://dev.to/mohitdebian</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mohitdebian"/>
    <language>en</language>
    <item>
      <title>I Built Relay_: The Open-Source Layer Between Your API and the Internet</title>
      <dc:creator>Mohit || Dev</dc:creator>
      <pubDate>Thu, 17 Sep 2026 11:30:58 +0000</pubDate>
      <link>https://dev.to/mohitdebian/i-built-relay-the-open-source-layer-between-your-api-and-the-internet-g5m</link>
      <guid>https://dev.to/mohitdebian/i-built-relay-the-open-source-layer-between-your-api-and-the-internet-g5m</guid>
      <description>&lt;p&gt;I almost rage-quit my own side project last month because I spent 14 hours fighting AWS API Gateway just to validate a single API key. &lt;/p&gt;

&lt;p&gt;Actually, I didn't quit. I just got so unbelievably frustrated with the extortionate pricing and miserable UX of modern API tools that I rage-built my own Gateway in Go instead. &lt;/p&gt;

&lt;p&gt;If you've ever built a public-facing API, you already know the nightmare. You write your core business logic in a weekend, and then hit a massive brick wall. &lt;/p&gt;

&lt;p&gt;When you look at the existing solutions to protect your API, they are universally painful:&lt;/p&gt;

&lt;p&gt;❌ &lt;strong&gt;AWS API Gateway:&lt;/strong&gt; The pricing is extortionate if you actually get traffic. Plus, the AWS Console UX is a nightmare, and setting up simple API key validation requires digging through IAM roles and CloudWatch just to see basic logs.&lt;/p&gt;

&lt;p&gt;❌ &lt;strong&gt;Kong / Tyk:&lt;/strong&gt; Incredibly powerful, but completely enterprise-bloated. You need a PhD in Lua and YAML just to configure a basic route. It's massive overkill for 99% of projects.&lt;/p&gt;

&lt;p&gt;❌ &lt;strong&gt;DIY (Express/FastAPI middleware):&lt;/strong&gt; You end up re-inventing the wheel every single time. It's slow under heavy load, and building a UI to manage your users' API keys is a miserable distraction from building your actual product.&lt;/p&gt;

&lt;p&gt;I got sick of choosing between "expensive," "bloated," or "DIY," so I built &lt;strong&gt;Relay&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why you should switch to Relay
&lt;/h3&gt;

&lt;p&gt;Relay is a lightweight, open-source API infrastructure layer. It sits right in front of your actual backend and handles all the annoying stuff automatically.&lt;/p&gt;

&lt;p&gt;Here is why it actually beats the alternatives:&lt;/p&gt;

&lt;p&gt;✅ &lt;strong&gt;Sub-millisecond latency:&lt;/strong&gt; The core gateway is written purely in Go. It uses Goroutines to handle thousands of concurrent requests with almost zero overhead. It blows Node.js proxies out of the water.&lt;br&gt;
✅ &lt;strong&gt;Instant API Keys &amp;amp; Auth:&lt;/strong&gt; No writing database lookups in your app. Relay intercepts the request, validates the key in-memory, and forwards the clean request to your API.&lt;br&gt;
✅ &lt;strong&gt;Built-in Redis Rate Limiting:&lt;/strong&gt; Enforce sliding-window rate limits globally or per user without writing a single line of Redis logic yourself.&lt;br&gt;
✅ &lt;strong&gt;A Gorgeous Control Plane:&lt;/strong&gt; Instead of crying over AWS CloudWatch logs, Relay comes with a sleek Next.js dashboard. You can generate keys, revoke access, and see real-time analytics instantly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Take it for a spin
&lt;/h3&gt;

&lt;p&gt;Relay is completely open-source, but if you want to skip the deployment headache, I've got a fully managed cloud version you can use right away.&lt;/p&gt;

&lt;p&gt;If you're building an API and don't want to deal with auth, rate limits, or AWS bills, you can start using Relay right now for free.&lt;/p&gt;

&lt;p&gt;🔗 Start using Relay: &lt;a href="https://relayapicloud.vercel.app/" rel="noopener noreferrer"&gt;https://relayapicloud.vercel.app/&lt;/a&gt; &lt;br&gt;
🐙 GitHub Repo: &lt;a href="https://github.com/mohitdebian/relay" rel="noopener noreferrer"&gt;https://github.com/mohitdebian/relay&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
      <category>backend</category>
      <category>go</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I was tired of OSS PRs going nowhere — so I built a tool that tells you what to work on and how to solve it</title>
      <dc:creator>Mohit || Dev</dc:creator>
      <pubDate>Fri, 06 Mar 2026 03:44:29 +0000</pubDate>
      <link>https://dev.to/mohitdebian/i-was-tired-of-oss-prs-going-nowhere-so-i-built-a-tool-that-tells-you-what-to-work-on-and-how-to-5b38</link>
      <guid>https://dev.to/mohitdebian/i-was-tired-of-oss-prs-going-nowhere-so-i-built-a-tool-that-tells-you-what-to-work-on-and-how-to-5b38</guid>
      <description>&lt;h1&gt;
  
  
  I was tired of OSS PRs going nowhere — so I built a tool that tells you what to work on and how to solve it
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;code&gt;opensource&lt;/code&gt; &lt;code&gt;github&lt;/code&gt; &lt;code&gt;webdev&lt;/code&gt; &lt;code&gt;productivity&lt;/code&gt;&lt;/p&gt;




&lt;p&gt;I've been contributing to open source for a while now.&lt;/p&gt;

&lt;p&gt;And for a long time, my workflow looked like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Browse GitHub issues for an hour&lt;/li&gt;
&lt;li&gt;Pick something that looks doable&lt;/li&gt;
&lt;li&gt;Spend a weekend on it&lt;/li&gt;
&lt;li&gt;Submit the PR&lt;/li&gt;
&lt;li&gt;Wait&lt;/li&gt;
&lt;li&gt;...still waiting&lt;/li&gt;
&lt;li&gt;Move on feeling defeated&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Sound familiar?&lt;/p&gt;

&lt;p&gt;The problem was never the code. It was that I had no system for picking the &lt;em&gt;right&lt;/em&gt; work.&lt;/p&gt;




&lt;h2&gt;
  
  
  The real problems nobody talks about
&lt;/h2&gt;

&lt;p&gt;When you're contributing to open source, there are three invisible problems killing your momentum:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Issue selection is a black box&lt;/strong&gt;&lt;br&gt;
You pick something that looks interesting. But you have no idea if the maintainer is even active, if someone else is already working on it, or if this type of PR ever gets merged in this repo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Competition is higher than you think&lt;/strong&gt;&lt;br&gt;
Those "good first issue" tags? Everyone sees them. By the time you finish, three others have already submitted. You never had a chance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. You don't know when to submit&lt;/strong&gt;&lt;br&gt;
Maintainers are humans with schedules. Submitting at the wrong time means your PR gets buried before it's even seen.&lt;/p&gt;




&lt;h2&gt;
  
  
  So I built AlgoMerge
&lt;/h2&gt;

&lt;p&gt;🔗 &lt;strong&gt;&lt;a href="https://algomerge.vercel.app" rel="noopener noreferrer"&gt;algomerge.vercel.app&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It's a contribution command center that solves all three problems.&lt;/p&gt;

&lt;p&gt;Here's what it actually does:&lt;/p&gt;

&lt;h3&gt;
  
  
  🔮 Merge Probability Score
&lt;/h3&gt;

&lt;p&gt;Before you even start working, AlgoMerge shows you the probability that a PR in this repo will get merged — based on maintainer patterns, repo behavior, and PR state. No more guessing.&lt;/p&gt;

&lt;h3&gt;
  
  
  🏆 Competition Score
&lt;/h3&gt;

&lt;p&gt;See how contested an issue is before you claim it. Low competition + active maintainer = high value work.&lt;/p&gt;

&lt;h3&gt;
  
  
  🎯 Issue Fit Discovery
&lt;/h3&gt;

&lt;p&gt;It matches issues to YOUR stack and bandwidth. Not just "beginner friendly" — actually relevant to what you know and how much time you have.&lt;/p&gt;

&lt;h3&gt;
  
  
  🤖 AI Analysis + Implementation Plan
&lt;/h3&gt;

&lt;p&gt;For each issue, you get an AI-generated breakdown of the problem AND a step-by-step implementation plan. So you walk in already knowing exactly what to do.&lt;/p&gt;

&lt;h3&gt;
  
  
  ⚡ Actionable Queue
&lt;/h3&gt;

&lt;p&gt;A ranked list of exactly what to work on next — built from your real contribution data and repo signals.&lt;/p&gt;




&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Connect GitHub&lt;/strong&gt; — one click, takes 2 minutes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Import your context&lt;/strong&gt; — PR history, issue patterns, repo data pulled automatically&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Get your queue&lt;/strong&gt; — ranked, prioritized, ready to ship&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;No config. No spreadsheets. Just signal.&lt;/p&gt;




&lt;h2&gt;
  
  
  Who it's for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Developers who contribute regularly and want to maximize impact&lt;/li&gt;
&lt;li&gt;Students building their OSS portfolio and need a smarter starting point&lt;/li&gt;
&lt;li&gt;Engineers who've had PRs ignored and want to stop wasting weekends&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Try it free
&lt;/h2&gt;

&lt;p&gt;🔗 &lt;strong&gt;&lt;a href="https://algomerge.vercel.app" rel="noopener noreferrer"&gt;algomerge.vercel.app&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Free to try. Sign in with GitHub and you're up in under 2 minutes.&lt;/p&gt;

&lt;p&gt;I'd love brutal feedback from this community — what would make this actually useful for how you contribute? Drop it in the comments 👇&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>[FOR SALE] PixelMagic – AI Image Generator SaaS (Live, Monetized) – Asking $199</title>
      <dc:creator>Mohit || Dev</dc:creator>
      <pubDate>Sat, 07 Jun 2025 19:02:30 +0000</pubDate>
      <link>https://dev.to/mohitdebian/for-sale-pixelmagic-ai-image-generator-saas-live-monetized-asking-199-2h85</link>
      <guid>https://dev.to/mohitdebian/for-sale-pixelmagic-ai-image-generator-saas-live-monetized-asking-199-2h85</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;I'm selling my micro-startup, &lt;a href="//pixelmagic.vercel.app"&gt;PixelMagic &lt;/a&gt;[&lt;a href="https://pixelmagic.vercel.app" rel="noopener noreferrer"&gt;https://pixelmagic.vercel.app&lt;/a&gt;] , a fully complete, AI-powered image generator software as a service (SaaS) for creators who desire quick, high-quality, watermark-free images at a far lower cost than rivals.&lt;/p&gt;

&lt;p&gt;🔧 What’s Included:&lt;/p&gt;

&lt;p&gt;Live Website: Fully deployed on Vercel, ready for scale.&lt;/p&gt;

&lt;p&gt;AI Image Generation: Uses a reliable third-party API.&lt;/p&gt;

&lt;p&gt;Frontend: Built in React.js + TypeScript for clean, modern UX.&lt;/p&gt;

&lt;p&gt;Authentication: Secured via Firebase Auth.&lt;/p&gt;

&lt;p&gt;Analytics: Integrated PostHog for user behavior tracking.&lt;/p&gt;

&lt;p&gt;Payments: Credit-based model with integrated payment gateway – monetization ready.&lt;/p&gt;

&lt;p&gt;No Watermarks on generated images.&lt;/p&gt;

&lt;p&gt;User Base: 100+ monthly active users and growing organically.&lt;/p&gt;

&lt;p&gt;📈 Why It's Valuable:&lt;br&gt;
Priced ~50% cheaper than Midjourney, ChatGPT, etc.&lt;/p&gt;

&lt;p&gt;Unique value prop: Free credits + no watermark&lt;/p&gt;

&lt;p&gt;Perfect for content creators, social media marketers, agencies, or indie hackers.&lt;/p&gt;

&lt;p&gt;Strong foundation – just needs traffic or community to scale.&lt;/p&gt;

&lt;p&gt;Great launchpad for someone looking to break into AI tools or bootstrap a creative SaaS.&lt;/p&gt;

&lt;p&gt;💰 Asking Price: $199 (Open for negotiations)&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
