<?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: buvn08</title>
    <description>The latest articles on DEV Community by buvn08 (@buvn08).</description>
    <link>https://dev.to/buvn08</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%2F3288362%2F3f2c9c58-6ff1-4f45-aabf-0dae446194c0.png</url>
      <title>DEV Community: buvn08</title>
      <link>https://dev.to/buvn08</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/buvn08"/>
    <language>en</language>
    <item>
      <title>I built a free, open-source Linktree alternative — here's why and how? Linkyaar.com</title>
      <dc:creator>buvn08</dc:creator>
      <pubDate>Wed, 19 Aug 2026 11:22:15 +0000</pubDate>
      <link>https://dev.to/buvn08/i-built-a-free-open-source-linktree-alternative-heres-why-and-how-linkyaarcom-2m48</link>
      <guid>https://dev.to/buvn08/i-built-a-free-open-source-linktree-alternative-heres-why-and-how-linkyaarcom-2m48</guid>
      <description>&lt;p&gt;The problem that annoyed me enough to build something&lt;/p&gt;

&lt;p&gt;Link-in-bio tools are one of the simplest product categories on the internet: one page, a list of links, some analytics. And yet somehow the popular ones have turned into subscription traps — watermarks you pay to remove, analytics locked behind a paywall, themes behind another paywall, and your audience data living on someone else's servers with no export button in sight.&lt;/p&gt;

&lt;p&gt;For a page that is literally your identity on the internet, that felt backwards.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="//linkyaar.com"&gt;LinkYaar&lt;/a&gt; — a free, open-source link-in-bio platform. Every feature that exists is free. No watermarks. No "upgrade to unlock." AGPL-licensed, so you can self-host it, fork it, or audit every line.&lt;/p&gt;

&lt;p&gt;⭐ GitHub: &lt;a href="https://github.com/bhuvan0808/linkyaar" rel="noopener noreferrer"&gt;https://github.com/bhuvan0808/linkyaar&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What it does&lt;br&gt;
One page for everything — unlimited links, socials, and work, live at linkyaar/yourname in under a minute&lt;br&gt;
Drag, drop, schedule, toggle — reorder links, feature what matters, schedule drops, and hide links without deleting them&lt;br&gt;
27 hand-tuned themes — or open the Studio and design your own with wallpapers, gradients, fonts, and button styles&lt;br&gt;
QR code built in — one short URL plus a crisp QR for posters, slides, and business cards&lt;br&gt;
Privacy-first analytics — views, clicks, CTR, 30-day trends, and top links. Collected without cookies or IP logging, visible only to you, never sold&lt;br&gt;
Your data is yours — full JSON export in one click, and account deletion that's actually permanent&lt;br&gt;
The design decisions I care most about&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Cookieless analytics&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I wanted creators to know what's working without turning their audience into tracking targets. So analytics are aggregated without cookies or IP logging. You get the numbers you actually need — views, clicks, trends, top links — and your visitors don't get followed around the internet. It turns out you don't need creepy tracking to answer "which link is working?"&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;AGPL, on purpose&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I picked AGPL-3.0 deliberately. It means anyone can self-host or fork LinkYaar, but improvements to hosted versions have to stay open too. For a product whose whole pitch is "your audience belongs to you," the license should back that up.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;No ransom model&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A lot of "free" tools are really a hostage negotiation: your page gets popular, then the watermark-removal fee shows up. LinkYaar's rule is simple — if a feature exists, it's free. The project sustains itself through community support, not by holding profiles hostage.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;SEO and social cards by default&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Every profile gets a clean URL, rich previews, and an auto-generated social card. Your page should look good when it's shared anywhere, not just inside the app.&lt;/p&gt;

&lt;p&gt;What I learned building it&lt;br&gt;
&amp;lt;!-- ✏️ CUSTOMIZE THIS SECTION — this is what makes the post &lt;em&gt;yours&lt;/em&gt; and what Dev.to readers actually love. 2–4 short lessons work best. Some prompts: --&amp;gt; &amp;lt;!-- - What was harder than expected? (theming system? analytics without cookies? scheduling?) --&amp;gt; &amp;lt;!-- - A specific bug or rewrite story --&amp;gt; &amp;lt;!-- - Your stack and why you chose it (e.g., Next.js, your DB, hosting) --&amp;gt; &amp;lt;!-- - What you'd do differently --&amp;gt;&lt;br&gt;
[Lesson one — e.g., "Building 27 themes taught me more about contrast and rhythm than any design course"]&lt;br&gt;
[Lesson two — e.g., "Cookieless analytics is a genuinely fun constraint — here's how I count uniques without fingerprinting"]&lt;br&gt;
[Lesson three — e.g., "Shipping the export button first kept me honest about the data model"]&lt;br&gt;
Try it, break it, fork it&lt;br&gt;
🚀 Claim your page: linkyaar.com — live in under a minute&lt;br&gt;
💻 Read the code: github.com/bhuvan0808/linkyaar&lt;br&gt;
🗺️ Public roadmap: linkyaar.com/roadmap&lt;/p&gt;

&lt;p&gt;It's early days and I'm building this in the open, so I'd genuinely love feedback — feature ideas, code review, theme requests, or just "this button feels wrong." Issues and discussions are open on GitHub.&lt;/p&gt;

&lt;p&gt;If you've ever paid to remove a watermark from your own bio page, this one's for you. 💛&lt;/p&gt;

&lt;p&gt;If you found this interesting, a ⭐ on GitHub helps more people discover the project — and tell me in the comments: what's the one feature every link-in-bio tool is missing?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
