<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AuthServer on</title><link>https://eunus.dev/tags/authserver/</link><description>Recent content in AuthServer on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/authserver/index.xml" rel="self" type="application/rss+xml"/><item><title>When Does Your Login System Need Its Own AuthServer?</title><link>https://eunus.dev/blog/when-does-your-login-system-need-its-own-authserver/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/when-does-your-login-system-need-its-own-authserver/</guid><description>A client asked me something recently that I think a lot of founders wonder but rarely ask out loud: &amp;ldquo;Why does the quote include a separate AuthServer? Isn&amp;rsquo;t that just&amp;hellip; more stuff to pay for?&amp;rdquo;
It&amp;rsquo;s a fair question. And the honest answer is: sometimes yes, it&amp;rsquo;s overkill. Sometimes it&amp;rsquo;s exactly the thing that saves your product later. The difference comes down to a few concrete signals, not a blanket rule.</description></item></channel></rss>