<?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: Olamilekan Olakunle</title>
    <description>The latest articles on DEV Community by Olamilekan Olakunle (@leksitech).</description>
    <link>https://dev.to/leksitech</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%2F223283%2F007d3fd4-3e33-4188-8cf4-19d26d644e86.jpg</url>
      <title>DEV Community: Olamilekan Olakunle</title>
      <link>https://dev.to/leksitech</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/leksitech"/>
    <language>en</language>
    <item>
      <title>cPanel vs Render vs AWS: the hosting costs nobody puts on the pricing page</title>
      <dc:creator>Olamilekan Olakunle</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:01:16 +0000</pubDate>
      <link>https://dev.to/leksitech/cpanel-vs-render-vs-aws-the-hosting-costs-nobody-puts-on-the-pricing-page-2pa6</link>
      <guid>https://dev.to/leksitech/cpanel-vs-render-vs-aws-the-hosting-costs-nobody-puts-on-the-pricing-page-2pa6</guid>
      <description>&lt;p&gt;Everyone asks which hosting is cheapest and gets a number back. Two dollars. Seven dollars. Twenty dollars.&lt;/p&gt;

&lt;p&gt;That number is the least useful thing about hosting.&lt;/p&gt;

&lt;p&gt;The real cost shows up on the day something breaks, and you find out what you can't do. No shell. No logs. No way to roll back.&lt;/p&gt;

&lt;p&gt;I've seen a site stay down for &lt;strong&gt;fourteen months&lt;/strong&gt; on hosting that cost about $4/month. It was, technically, very cheap.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three tiers, with the useless numbers first
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Monthly&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Shared cPanel&lt;/td&gt;
&lt;td&gt;$2-10&lt;/td&gt;
&lt;td&gt;Disk, MySQL, PHP, a control panel&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Render&lt;/td&gt;
&lt;td&gt;Free, or ~$7&lt;/td&gt;
&lt;td&gt;Managed deploys, logs, rollback&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AWS (App Runner + RDS)&lt;/td&gt;
&lt;td&gt;~$20-40&lt;/td&gt;
&lt;td&gt;Real infrastructure, real complexity&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Those numbers are correct and they explain almost nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shared cPanel: genuinely the right answer, sometimes
&lt;/h2&gt;

&lt;p&gt;For a WordPress install, a static site or a brochure site, shared hosting at a few dollars a month is the correct choice. Don't let anyone shame you out of it.&lt;/p&gt;

&lt;p&gt;What you're giving up is &lt;strong&gt;access&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Shell access is often disabled entirely - no SSH, no running a command&lt;/li&gt;
&lt;li&gt;No real application logs, just a generic error page&lt;/li&gt;
&lt;li&gt;No deploy pipeline. You upload files.&lt;/li&gt;
&lt;li&gt;No rollback&lt;/li&gt;
&lt;li&gt;Some panels block you from uploading a zip containing JavaScript&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last one sounds trivial until it's 11pm and you're trying to deploy a build.&lt;/p&gt;

&lt;h2&gt;
  
  
  What that actually costs when it goes wrong
&lt;/h2&gt;

&lt;p&gt;A legacy PHP app on shared hosting starts returning a truncated response. Fast first byte, so the uptime monitor reports everything fine - then the connection just stops partway through the page. Every page that loads one particular include dies at the same byte count.&lt;/p&gt;

&lt;p&gt;On a server with shell access that's a twenty-minute job: tail the error log, find the fatal, fix it.&lt;/p&gt;

&lt;p&gt;With shell disabled and no log access, you're guessing. And because the monitor said "up", nobody escalated it.&lt;/p&gt;

&lt;p&gt;Fourteen months.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The hosting didn't fail. The access failed.&lt;/strong&gt; That's the cost nobody puts on the pricing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Render: the $7 that buys the most
&lt;/h2&gt;

&lt;p&gt;The free tier spins down after 15 minutes of no traffic, with roughly a 50-second cold start. You get 750 instance hours a month - enough for exactly one always-on service. The free Postgres deletes itself after 30 days.&lt;/p&gt;

&lt;p&gt;Starter is about $7/month and the sleeping stops.&lt;/p&gt;

&lt;p&gt;What that $7 buys is precisely what cPanel won't give you: logs, a deploy pipeline, rollback, environment variables, a health check. For a small API that's the best value on this list, and it isn't close.&lt;/p&gt;

&lt;h2&gt;
  
  
  AWS: and the free tier change nobody updated
&lt;/h2&gt;

&lt;p&gt;A realistic small deployment is App Runner for the service and RDS Postgres for the data:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RDS &lt;code&gt;db.t4g.micro&lt;/code&gt; - about &lt;strong&gt;$12-15/month&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;App Runner - &lt;strong&gt;$5-25/month&lt;/strong&gt; depending on traffic&lt;/li&gt;
&lt;li&gt;Realistically &lt;strong&gt;$20-40/month&lt;/strong&gt; at low traffic&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But the number everyone quotes is out of date:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Accounts created &lt;strong&gt;before 15 July 2025&lt;/strong&gt; keep the legacy 12-month free tier.&lt;br&gt;
Accounts created &lt;strong&gt;after&lt;/strong&gt; that get &lt;strong&gt;6 months plus up to $200 in credits&lt;/strong&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Almost every AWS tutorial still says "free for twelve months". For a new account it isn't. Plan for six.&lt;br&gt;
&lt;a href="https://aws.amazon.com/free" rel="noopener noreferrer"&gt;https://aws.amazon.com/free&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And the honest point: &lt;strong&gt;AWS isn't expensive at this size - it's complicated.&lt;/strong&gt; IAM users, security groups, a region choice, ECR, a deploy role, DNS validation. The cost is measured in hours, not dollars, and those hours are all front-loaded.&lt;/p&gt;

&lt;h2&gt;
  
  
  The costs that never appear on a pricing page
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;cPanel&lt;/th&gt;
&lt;th&gt;Render&lt;/th&gt;
&lt;th&gt;AWS&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Time to first deploy&lt;/td&gt;
&lt;td&gt;Minutes&lt;/td&gt;
&lt;td&gt;Minutes&lt;/td&gt;
&lt;td&gt;A day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time to debug at 2am&lt;/td&gt;
&lt;td&gt;Hours, or never&lt;/td&gt;
&lt;td&gt;Minutes&lt;/td&gt;
&lt;td&gt;Minutes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rollback&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;One click&lt;/td&gt;
&lt;td&gt;Redeploy previous image&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scaling&lt;/td&gt;
&lt;td&gt;Buy a bigger plan&lt;/td&gt;
&lt;td&gt;Change a dropdown&lt;/td&gt;
&lt;td&gt;Automatic&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lock-in&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;td&gt;High&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What I'd actually pick
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;WordPress, static sites, brochure sites&lt;/strong&gt; -&amp;gt; shared cPanel. Correct answer, don't overthink it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A side project or prototype&lt;/strong&gt; -&amp;gt; Render free, with Neon for the database.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A real app with real users&lt;/strong&gt; -&amp;gt; Render Starter at $7. Best money-per-problem-solved on this list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Compliance, scale, or a team&lt;/strong&gt; -&amp;gt; AWS, and budget the hours rather than the dollars.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one rule
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Choose the cheapest tier that still lets you see what went wrong.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That single rule would have saved fourteen months.&lt;/p&gt;




&lt;p&gt;Figures checked November 2026 against the vendors' own pages - they change often, so check the date before planning around any of it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>devops</category>
      <category>hosting</category>
      <category>aws</category>
    </item>
    <item>
      <title>Neon vs Supabase free tiers: the difference that kills side projects</title>
      <dc:creator>Olamilekan Olakunle</dc:creator>
      <pubDate>Thu, 19 Nov 2026 13:25:21 +0000</pubDate>
      <link>https://dev.to/leksitech/neon-vs-supabase-free-tiers-the-difference-that-kills-side-projects-2a34</link>
      <guid>https://dev.to/leksitech/neon-vs-supabase-free-tiers-the-difference-that-kills-side-projects-2a34</guid>
      <description>&lt;p&gt;Every Neon vs Supabase comparison I could find is a feature checklist. Storage, bandwidth, row limits, a table of green ticks.&lt;/p&gt;

&lt;p&gt;None of them mention the difference that actually decides it.&lt;/p&gt;

&lt;p&gt;It isn't how much storage you get on day one. It's &lt;strong&gt;what happens to your project on the week nobody touches it&lt;/strong&gt; — because that's the week it breaks, and these two behave nothing alike.&lt;/p&gt;

&lt;p&gt;Everything below is from the vendors' own documentation, checked November 2026, with links so you can verify it rather than trust me.&lt;/p&gt;

&lt;h2&gt;
  
  
  First: "Neon is just a database" is out of date
&lt;/h2&gt;

&lt;p&gt;The standard take is that comparing them is a category error — Neon is a Postgres database, Supabase is a backend platform, so they aren't really competitors.&lt;/p&gt;

&lt;p&gt;That was true. It isn't any more.&lt;/p&gt;

&lt;p&gt;Neon's &lt;strong&gt;free&lt;/strong&gt; plan now includes managed auth (up to 60k MAU per project), 5 GB of object storage, functions, an AI gateway and realtime. That's a backend.&lt;/p&gt;

&lt;p&gt;So for the first time this is an honest comparison rather than two product categories shouting past each other. Which means it comes down to behaviour and arithmetic, not feature lists.&lt;/p&gt;

&lt;h2&gt;
  
  
  The headline numbers
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Neon free&lt;/th&gt;
&lt;th&gt;Supabase free&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Database storage&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1 GB&lt;/strong&gt; per project&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;500 MB&lt;/strong&gt; per project&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Projects&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;100&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;2 active&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;100 CU-hours/project/month&lt;/td&gt;
&lt;td&gt;shared CPU, 500 MB RAM&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Egress&lt;/td&gt;
&lt;td&gt;5 GB per project&lt;/td&gt;
&lt;td&gt;5 GB + 5 GB cached&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;File storage&lt;/td&gt;
&lt;td&gt;5 GB object storage&lt;/td&gt;
&lt;td&gt;1 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Auth&lt;/td&gt;
&lt;td&gt;up to 60k MAU&lt;/td&gt;
&lt;td&gt;50k MAU&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;First paid tier&lt;/td&gt;
&lt;td&gt;usage-based, &lt;strong&gt;no monthly minimum&lt;/strong&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;$25/month&lt;/strong&gt; floor&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Of those, one number barely matters and one matters a lot.&lt;/p&gt;

&lt;p&gt;A gigabyte against 500 MB: almost no side project hits either ceiling.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;100 projects against 2&lt;/strong&gt; is the difference between parking every experiment you start and deleting one to begin the next.&lt;/p&gt;

&lt;h2&gt;
  
  
  The difference nobody leads with
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Neon: compute suspends after 5 minutes
&lt;/h3&gt;

&lt;p&gt;From &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Neon's plan documentation&lt;/a&gt;, under Scale to zero:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Free:&lt;/strong&gt; 5 min inactivity; cannot disable&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Your compute suspends. The next query wakes it. Your data, schema and connection string are exactly where you left them. Neon does not pause or delete free projects for inactivity.&lt;/p&gt;

&lt;h3&gt;
  
  
  Supabase: the project pauses after 7 days
&lt;/h3&gt;

&lt;p&gt;From &lt;a href="https://supabase.com/docs/guides/platform/free-project-pausing" rel="noopener noreferrer"&gt;Supabase's project pausing guide&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Supabase pauses Free Plan projects that show low activity over a 7-day period to save server resources.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Not the compute. &lt;strong&gt;The project.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;To be fair to Supabase, paused is not deleted — you get a &lt;em&gt;Resume project&lt;/em&gt; button in the dashboard and roughly a year to press it. But in the meantime your API is down, and if anyone was actually using that side project, it's down for them too.&lt;/p&gt;

&lt;p&gt;Their guidance is that "a few user requests to the database each day over the previous week is enough to keep the project from being paused."&lt;/p&gt;

&lt;h2&gt;
  
  
  The keep-alive trap
&lt;/h2&gt;

&lt;p&gt;This is the same shape of problem as Render's free web services sleeping after 15 minutes — the one people solve by bolting on a cron job that pings their own service.&lt;/p&gt;

&lt;p&gt;On Supabase, that pattern is arguably necessary: a few requests a day keeps the project alive.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On Neon it's actively harmful&lt;/strong&gt;, and here's the arithmetic nobody does.&lt;/p&gt;

&lt;p&gt;Neon free gives you &lt;strong&gt;100 CU-hours per project per month&lt;/strong&gt;. The smallest compute size is &lt;strong&gt;0.25 CU&lt;/strong&gt;. So:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;100 CU-hours ÷ 0.25 CU = 400 hours of running compute
a 31-day month         = 744 hours
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You cannot keep a Neon free project awake around the clock. Read that as a trap and you'd be wrong — you don't need to. A suspended compute burns nothing, and the whole design assumes it's asleep most of the time.&lt;/p&gt;

&lt;p&gt;The thing that &lt;em&gt;would&lt;/em&gt; break it is exactly the keep-alive ping people reach for out of habit. Ping a database designed to scale to zero and you spend your month's allowance keeping an idle thing awake.&lt;/p&gt;

&lt;h2&gt;
  
  
  The money, when free stops being enough
&lt;/h2&gt;

&lt;p&gt;Supabase Pro starts at &lt;strong&gt;$25/month&lt;/strong&gt;. That's a floor, not an estimate — you pay it whether anyone shows up or not.&lt;/p&gt;

&lt;p&gt;Neon's first paid plan is usage-based with no monthly minimum: roughly &lt;strong&gt;$0.106 per CU-hour&lt;/strong&gt; and &lt;strong&gt;$0.35 per GB-month&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;That's a difference in kind, not just in price. Predictable billing usually wins if you're running one serious app. If you're running six half-finished ones, it very much doesn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd actually pick
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Lots of small projects you come back to every few weeks → Neon.&lt;/strong&gt; A hundred projects, and the week you ignore one costs you nothing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One real app that needs auth, file storage and realtime today, and that you're in most weeks → Supabase.&lt;/strong&gt; The backend is more mature, and you'll keep it awake just by working on it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Already on Prisma or Drizzle and you only need Postgres → Neon&lt;/strong&gt;, without much thinking about it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don't take my word for it — the 10-minute test
&lt;/h2&gt;

&lt;p&gt;Create a free project on each. Run one query. Walk away for ten minutes. Run the same query and time it.&lt;/p&gt;

&lt;p&gt;That one number will tell you more about living with a free tier than any comparison table, including this one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;All checked November 2026. These pages change often, so check the date before trusting any of it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;neon.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;neon.com/docs/introduction/plans&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/pricing" rel="noopener noreferrer"&gt;supabase.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/platform/free-project-pausing" rel="noopener noreferrer"&gt;supabase.com/docs/guides/platform/free-project-pausing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I made a video version of this with the documentation on screen, if you'd rather watch it: &lt;a href="https://youtu.be/4T6uHlN8xQs" rel="noopener noreferrer"&gt;https://youtu.be/4T6uHlN8xQs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've hit either of these limits in anger, I'd genuinely like to hear how it went — especially the Supabase pause, which I suspect catches more people than anyone admits.&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>database</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
