<?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>Forem: kenansafi</title>
    <description>The latest articles on Forem by kenansafi (@kenansafi).</description>
    <link>https://forem.com/kenansafi</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3715212%2Fc3979344-6ddb-41fc-9b6e-2028fd353a6b.webp</url>
      <title>Forem: kenansafi</title>
      <link>https://forem.com/kenansafi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/kenansafi"/>
    <language>en</language>
    <item>
      <title>I Got Tired of Manual SSH. So I Built a Free Tool to Deploy GitHub Repos to Any VPS.</title>
      <dc:creator>kenansafi</dc:creator>
      <pubDate>Tue, 20 Jan 2026 16:59:58 +0000</pubDate>
      <link>https://forem.com/kenansafi/i-got-tired-of-manual-ssh-so-i-built-a-free-tool-to-deploy-github-repos-to-any-vps-15hn</link>
      <guid>https://forem.com/kenansafi/i-got-tired-of-manual-ssh-so-i-built-a-free-tool-to-deploy-github-repos-to-any-vps-15hn</guid>
      <description>&lt;p&gt;Stop running git pull and restarting Nginx manually. We are in the era of Vibe Coding, and our deployment workflow should be as fast as our Cursor prompts.&lt;br&gt;
I love Vercel’s DX, but I hate the "Serverless Tax" once my apps start scaling. I wanted the power of a dedicated VPS (DigitalOcean/Hostinger) with the ease of a "Push-to-Deploy" dashboard. Since I couldn't find a simple, free version—I built one.&lt;br&gt;
What is it?&lt;br&gt;
It’s a free deployment dashboard (DeployWise) where you can:&lt;br&gt;
🔗 Connect your GitHub account.&lt;br&gt;
🖥️ Link any VPS via SSH.&lt;br&gt;
🚀 Deploy any repo with one click.&lt;br&gt;
No more complex CI/CD pipelines or manual server setup. It handles the "boring" stuff so you can focus on the "vibe."&lt;br&gt;
How to start:&lt;br&gt;
Login with GitHub at &lt;a href="https://deploywise.dev/dashboard" rel="noopener noreferrer"&gt;Deploy Wise&lt;/a&gt;&lt;br&gt;
Connect your VPS.&lt;br&gt;
If you don't have a VPS yet, I recommend Hostinger (for budget) or Cloudways (for performance). You can find exclusive developer discounts on the dashboard.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>devops</category>
      <category>productivity</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Beyond the Vercel Tax: A Software Engineer's Guide to Managed Cloud Costs</title>
      <dc:creator>kenansafi</dc:creator>
      <pubDate>Fri, 16 Jan 2026 16:05:15 +0000</pubDate>
      <link>https://forem.com/kenansafi/beyond-the-vercel-tax-a-software-engineers-guide-to-managed-cloud-costs-po8</link>
      <guid>https://forem.com/kenansafi/beyond-the-vercel-tax-a-software-engineers-guide-to-managed-cloud-costs-po8</guid>
      <description>&lt;p&gt;We all love the Vercel/Netlify developer experience. git push and your app is live. It’s the "Vibe Coding" dream. But as a software engineer, I’ve noticed a recurring pattern in the SaaS community: The Scaling Wall.&lt;br&gt;
When your hobby project turns into a production app with real traffic, those "serverless" costs (especially bandwidth and function execution) can scale faster than your revenue.&lt;br&gt;
In this post, I want to share my research on finding the "break-even point" between Serverless PaaS and Managed Cloud (VPS).&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Invisible "Bandwidth Tax"
Most serverless platforms offer great free tiers, but their bandwidth markups are massive. We are talking about 
20
−
20−
40 per 100GB compared to 
1
−
1−
2 per 100GB on raw cloud providers like DigitalOcean, AWS, or GCP.
If you're building an AI wrapper that handles large prompts or an e-commerce site with high-res images, your infrastructure bill can become your biggest headache overnight.&lt;/li&gt;
&lt;li&gt;Cold Starts vs. Dedicated Resources
Serverless is great for sporadic traffic. But for a production SaaS, you want:
Zero Cold Starts: Your API should respond instantly, every time.
Predictable Billing: Knowing exactly what you’ll pay at the end of the month.
Control: Full access to Redis, Object Caching, and PHP/Node settings.&lt;/li&gt;
&lt;li&gt;The Middle Ground: Managed Cloud
Many developers avoid VPS (Virtual Private Servers) because they don't want to be "SysAdmins." They don't want to manage security patches, firewalls, or OS updates.
This is where Managed Cloud providers (like Cloudways) come in. You get the raw power of DigitalOcean or AWS but with a managed panel that handles the "boring" stuff.
Feature Serverless (PaaS)   Managed Cloud (VPS)
Setup Time  1 Minute    5 Minutes
Pricing Usage-based (Unpredictable) Fixed Monthly (Predictable)
Bandwidth   Expensive Markups   Massive limits included
Control Limited High (Managed)&lt;/li&gt;
&lt;li&gt;Why I Built a Tool to Solve This
During my research, I got tired of switching between price pages and spreadsheets. I wanted a way to calculate exactly when it makes sense to switch from a PaaS to a Managed Cloud based on specific RAM and traffic needs.
I built a simple, interactive Cloud Cost Calculator to visualize these numbers:
👉 DeployWise.dev
It compares tiers from DigitalOcean, AWS, and Google Cloud (managed via Cloudways) against standard serverless costs. It’s free, built with Next.js, and I've even shared the raw pricing data on GitHub for transparency.
Conclusion
Don't wait for a $500 surprise bill to think about your infrastructure. Use serverless for the "vibe" phase, but have a migration plan ready for the "growth" phase.
How are you managing your cloud costs in 2026? Are you sticking with serverless or moving back to managed VPS? Let's discuss in the comments.
#nextjs #cloud #devops #webdev #saas&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>nextjs</category>
      <category>cloud</category>
      <category>devops</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
