<?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: Hayden</title>
    <description>The latest articles on DEV Community by Hayden (@selfhostcalc).</description>
    <link>https://dev.to/selfhostcalc</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%2F4201534%2Fdc1a30e7-e1c3-4e07-ba30-a719175dfe0f.png</url>
      <title>DEV Community: Hayden</title>
      <link>https://dev.to/selfhostcalc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/selfhostcalc"/>
    <language>en</language>
    <item>
      <title>StackCost weekly n8n hosting price check (Nov 16, 2026)</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Mon, 16 Nov 2026 15:20:26 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/stackcost-weekly-n8n-hosting-price-check-nov-16-2026-3ejg</link>
      <guid>https://dev.to/selfhostcalc/stackcost-weekly-n8n-hosting-price-check-nov-16-2026-3ejg</guid>
      <description>&lt;p&gt;My weekly check of what it really costs to run n8n on the hosts people ask about most. I re-checked every price against each host's own pricing page (or public API) on Nov 16, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short version: one change, at Hetzner. Everything else is the same.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hetzner&lt;/strong&gt;: its Regular Performance "from" prices dropped because Helsinki is now the cheapest EU location. CPX22 (2 vCPU / 4 GB) is from €16.99/mo excl. VAT in Helsinki (€19.99 in Nuremberg), CPX12 (2 GB) from €9.99, and CPX02 (1 GB) from €5.49. Catch: when I checked, Hetzner's page marked every CPX plan "currently unavailable", and the Cost-Optimized CX23 (€5.99) and CX33 (€8.99) are still "not available."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hostinger&lt;/strong&gt;: KVM 1 is still $6.49/mo intro and renews at $11.99/mo. KVM 2 (8 GB) is $8.79 intro and renews at $14.99. Budget for the renewal price, not the intro.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contabo&lt;/strong&gt;: Cloud VPS 10 (4 vCPU / 8 GB) is $5.28/mo for the first 24 months and $6.60/mo at the regular price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RackNerd&lt;/strong&gt;: the 2 GB KVM special is still $35.99/yr (about $3/mo), but only as a 12-month prepay on an unmanaged VPS.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vultr / Linode / DigitalOcean&lt;/strong&gt;: no change. 4 GB is $20 on Vultr and $24 on both Linode and DigitalOcean.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Cloud&lt;/strong&gt;: Starter is still $24/mo ($20/mo billed yearly) for 2,500 executions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two new comparisons this week:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://selfhostcalc.com/compare/n8n-cloud-vs-hostinger.html" rel="noopener noreferrer"&gt;n8n Cloud vs Hostinger&lt;/a&gt;: $240/yr for n8n Cloud Starter (billed yearly) vs $143.88/yr for Hostinger KVM 1 even at its renewal price.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/contabo-vs-racknerd-n8n.html" rel="noopener noreferrer"&gt;Contabo vs RackNerd for n8n&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To plug in your own workflow counts, the free &lt;a href="https://selfhostcalc.com/calculator.html" rel="noopener noreferrer"&gt;calculator&lt;/a&gt; compares n8n Cloud with a VPS.&lt;/p&gt;

&lt;p&gt;Disclosure: the RackNerd links on the site are affiliate links. Rankings are sorted by price either way.&lt;/p&gt;

&lt;p&gt;If you spot a price I got wrong, leave a comment and I'll fix it.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>automation</category>
    </item>
    <item>
      <title>StackCost weekly n8n hosting price check (Nov 2, 2026)</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Thu, 05 Nov 2026 23:05:32 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/stackcost-weekly-n8n-hosting-price-check-nov-2-2026-304i</link>
      <guid>https://dev.to/selfhostcalc/stackcost-weekly-n8n-hosting-price-check-nov-2-2026-304i</guid>
      <description>&lt;p&gt;My weekly check of what it really costs to run n8n on the hosts people ask about most. I re-checked every price against each host's own pricing page (or public API) on Nov 2, 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short version: no price changes this week.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hostinger&lt;/strong&gt;: KVM 1 is still $6.49/mo intro ($155.76 upfront for 24 months) and renews at $11.99/mo. KVM 2 (8 GB) is $8.79 intro and renews at $14.99. Budget for the renewal price, not the intro.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hetzner&lt;/strong&gt;: the Cost-Optimized CX23 (4 GB, €5.99) and CX33 (8 GB, €8.99) are still marked "not available." The 4 GB plan you can actually order, CPX22, is €19.99/mo excl. VAT in EU locations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contabo&lt;/strong&gt;: Cloud VPS 10 (4 vCPU / 8 GB) is $5.28/mo for the first 24 months and $6.60/mo at the regular price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RackNerd&lt;/strong&gt;: the 2 GB KVM special is still $35.99/yr (about $3/mo), but only as a 12-month prepay on an unmanaged VPS. Month-to-month plans cost much more.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vultr / Linode / DigitalOcean&lt;/strong&gt;: no change. 4 GB is $20 on Vultr and $24 on both Linode and DigitalOcean.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Cloud&lt;/strong&gt;: Starter is still $24/mo ($20/mo billed yearly) for 2,500 executions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two new comparisons this week, since Hetzner comes up in almost every "where should I host n8n" thread:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/hostinger-vs-hetzner-n8n.html" rel="noopener noreferrer"&gt;Hostinger vs Hetzner for n8n&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/contabo-vs-hetzner-n8n.html" rel="noopener noreferrer"&gt;Contabo vs Hetzner for n8n&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To plug in your own workflow counts, the free &lt;a href="https://selfhostcalc.com/calculator.html" rel="noopener noreferrer"&gt;calculator&lt;/a&gt; compares n8n Cloud with a VPS.&lt;/p&gt;

&lt;p&gt;Disclosure: the RackNerd links on the site are affiliate links. Rankings are sorted by price either way.&lt;/p&gt;

&lt;p&gt;If you spot a price I got wrong, leave a comment and I'll fix it.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>automation</category>
    </item>
    <item>
      <title>Stripe in a Lovable or Bolt app: the success page isn't proof of payment</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Thu, 29 Oct 2026 23:36:31 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/stripe-in-a-lovable-or-bolt-app-the-success-page-isnt-proof-of-payment-103b</link>
      <guid>https://dev.to/selfhostcalc/stripe-in-a-lovable-or-bolt-app-the-success-page-isnt-proof-of-payment-103b</guid>
      <description>&lt;p&gt;You asked your AI builder to "add Stripe." It worked. You paid with a test card, landed on &lt;code&gt;/success&lt;/code&gt;, and your app unlocked the Pro stuff.&lt;/p&gt;

&lt;p&gt;Here's the problem. &lt;strong&gt;Many AI-built apps unlock paid features just because someone opened the success page.&lt;/strong&gt; Anyone can type &lt;code&gt;/success&lt;/code&gt; into the address bar. No card needed. That's not a checkout. That's an honor system.&lt;/p&gt;

&lt;p&gt;Stripe says this plainly in its own docs: you can't rely on the landing page alone, because a customer might pay and then lose their connection before the page loads. &lt;strong&gt;Webhooks are required&lt;/strong&gt; (&lt;a href="https://docs.stripe.com/checkout/fulfillment" rel="noopener noreferrer"&gt;Stripe's fulfillment docs&lt;/a&gt;). So the success page is wrong both ways. It can unlock things for people who didn't pay, and it can miss people who did.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 30-second test
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Log in as a free user (or open a private window).&lt;/li&gt;
&lt;li&gt;Type your success URL by hand, like &lt;code&gt;yourapp.com/success&lt;/code&gt; or &lt;code&gt;yourapp.com/success?session_id=anything&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Did anything unlock? A Pro badge, credits, a download, an "order paid" status?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If yes, your app is giving things away. Fix it before you launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it should work
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Customer pays on Stripe Checkout
        ↓
Stripe sends a signed webhook (checkout.session.completed) to YOUR server
        ↓
Your server checks the signature, then checks payment_status
        ↓
Your server marks the order paid in the database
        ↓
The success page just READS that status ("Thanks! You're all set.")
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The browser never decides who paid. Your server does, based on a message that only Stripe can sign.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix, step by step
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Move "mark as paid" to a webhook
&lt;/h3&gt;

&lt;p&gt;In Supabase, that's an Edge Function (for example &lt;code&gt;stripe-webhook&lt;/code&gt;). Have it listen for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;checkout.session.completed&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;checkout.session.async_payment_succeeded&lt;/code&gt; (for bank payments that clear later)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Check the signature, every time
&lt;/h3&gt;

&lt;p&gt;Use Stripe's library to verify the &lt;code&gt;Stripe-Signature&lt;/code&gt; header with your webhook secret (&lt;code&gt;whsec_...&lt;/code&gt;). In a Supabase Edge Function (Deno), use &lt;code&gt;constructEventAsync&lt;/code&gt; with the &lt;strong&gt;raw&lt;/strong&gt; request body:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;body&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;text&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt; &lt;span class="c1"&gt;// raw body, not req.json()&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;sig&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Stripe-Signature&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;event&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;stripe&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;webhooks&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;constructEventAsync&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="nx"&gt;body&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;sig&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Deno&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;STRIPE_WEBHOOK_SECRET&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Stripe&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createSubtleCryptoProvider&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the check fails, return 400 and do nothing. Without this, anyone can send your webhook a fake "they paid" message.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Heads up: Stripe can't send a Supabase login token, so this one function usually runs with JWT checks off (&lt;code&gt;--no-verify-jwt&lt;/code&gt;). That's fine &lt;strong&gt;only because&lt;/strong&gt; the signature check is doing the security work. Never turn off JWT checks on your other functions to "fix" a 401.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  3. Check &lt;code&gt;payment_status&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;A completed session isn't always a paid one. Stripe's own sample only fulfills when &lt;code&gt;payment_status&lt;/code&gt; is not &lt;code&gt;unpaid&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Make it safe to run twice
&lt;/h3&gt;

&lt;p&gt;Stripe can send the same event more than once. Save the Checkout Session ID with the order and skip it if you've already fulfilled it.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Lock the "paid" column
&lt;/h3&gt;

&lt;p&gt;If your &lt;code&gt;orders&lt;/code&gt; or &lt;code&gt;profiles&lt;/code&gt; table has &lt;code&gt;is_paid&lt;/code&gt;, &lt;code&gt;plan&lt;/code&gt;, or &lt;code&gt;credits&lt;/code&gt;, make sure users can't update it themselves. With Supabase RLS, don't give users an UPDATE policy on those columns. Only the webhook (using the secret key on the server) should change them.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Keep secret keys off the front end
&lt;/h3&gt;

&lt;p&gt;Your Stripe &lt;strong&gt;secret&lt;/strong&gt; key (&lt;code&gt;sk_live_...&lt;/code&gt;) and webhook secret belong in server env vars, never in &lt;code&gt;VITE_&lt;/code&gt; or &lt;code&gt;NEXT_PUBLIC_&lt;/code&gt; variables. The publishable key (&lt;code&gt;pk_...&lt;/code&gt;) is the only Stripe key the browser should see.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Turn the success page into a "thank you" page
&lt;/h3&gt;

&lt;p&gt;It can show a spinner and check the order status from your database. It should never write "paid" anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  A prompt you can paste into Lovable, Bolt or Cursor
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;"Don't mark orders or plans as paid from the success page. Create a Supabase Edge Function that receives Stripe webhooks, verifies the Stripe-Signature header with constructEventAsync on the raw body, handles checkout.session.completed and checkout.session.async_payment_succeeded, checks payment_status, and updates the order using the server-side key. Skip sessions already fulfilled. Make sure users can't update is_paid, plan or credits through RLS. Show me the changes before applying them."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Read what it changes before you accept it. AI tools love to "fix" errors by turning checks off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Typing &lt;code&gt;/success&lt;/code&gt; by hand unlocks nothing&lt;/li&gt;
&lt;li&gt;[ ] Webhook verifies the Stripe signature with the raw body&lt;/li&gt;
&lt;li&gt;[ ] Webhook checks &lt;code&gt;payment_status&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Same event twice doesn't double-credit&lt;/li&gt;
&lt;li&gt;[ ] Users can't edit &lt;code&gt;is_paid&lt;/code&gt; / &lt;code&gt;plan&lt;/code&gt; / &lt;code&gt;credits&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] No &lt;code&gt;sk_&lt;/code&gt; key or &lt;code&gt;whsec_&lt;/code&gt; secret in front-end code&lt;/li&gt;
&lt;li&gt;[ ] Live mode has its own webhook endpoint and secret (test ones don't carry over)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is the Stripe publishable key safe to show?&lt;/strong&gt;&lt;br&gt;
Yes. &lt;code&gt;pk_&lt;/code&gt; keys are meant for the browser. The &lt;code&gt;sk_&lt;/code&gt; secret key is not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can't I just check &lt;code&gt;session_id&lt;/code&gt; on the success page?&lt;/strong&gt;&lt;br&gt;
Only if your server looks that session up with Stripe and checks it. Even then, you still need the webhook, because some customers never reach the page.&lt;/p&gt;




&lt;p&gt;I build DeployVet, an outside-in security check for AI-built sites. If you want a free outside check of your own site: &lt;a href="https://deployvet.com/?utm_source=devto" rel="noopener noreferrer"&gt;https://deployvet.com/?utm_source=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>stripe</category>
      <category>security</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What about 630 website checks showed me in the first week, and what they cannot show</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Thu, 29 Oct 2026 00:34:05 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/what-about-630-website-checks-showed-me-in-the-first-week-and-what-they-cannot-show-3dl6</link>
      <guid>https://dev.to/selfhostcalc/what-about-630-website-checks-showed-me-in-the-first-week-and-what-they-cannot-show-3dl6</guid>
      <description>&lt;p&gt;I build DeployVet, a free tool that does a website security and bug check from the outside and grades the site A to F. I wanted to share what the numbers look like after the first week, and be clear about what they do not prove.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Oct 20 to 26, 2026: 645 checks on 633 unique domains (our own test domains excluded).&lt;/li&gt;
&lt;li&gt;Using each domain's latest grade: 260 domains (about 41%) scored A or B, and 372 (about 59%) scored C, D or F. One had no grade.&lt;/li&gt;
&lt;li&gt;The public counter read 650 total checks as of Mon Oct 26, 2026, about 11:55 AM Central.&lt;/li&gt;
&lt;li&gt;On the public board, the 20 lowest results were 4 F, 9 D and 7 C. The 20 highest were all A (19 scored 100, one scored 95).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These sites are ones people chose to type in, not a random sample. Read the method notes before you quote any of this.&lt;/p&gt;

&lt;h2&gt;
  
  
  Grade tables
&lt;/h2&gt;

&lt;p&gt;All domains checked, Oct 20 to 26, 2026 (latest grade per domain, 633 domains):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Grade group&lt;/th&gt;
&lt;th&gt;Domains&lt;/th&gt;
&lt;th&gt;Share of 633&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A or B&lt;/td&gt;
&lt;td&gt;260&lt;/td&gt;
&lt;td&gt;about 41%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;C, D or F&lt;/td&gt;
&lt;td&gt;372&lt;/td&gt;
&lt;td&gt;about 59%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No grade&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;under 1%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The query reports A/B and C/D/F as groups, so I am not giving a count for each single letter.&lt;/p&gt;

&lt;p&gt;Newest 10 on the public board:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Grade&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;B&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;C&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;D&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;F&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Scores in this slice run from 46 to 100.&lt;/p&gt;

&lt;p&gt;20 lowest on the board:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Grade&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;th&gt;Score range&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;F&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;11 to 39&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;D&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;46 to 56&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;C&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;61 to 71&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;20 highest on the board:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Grade&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;th&gt;Score range&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;td&gt;95 to 100&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The board tables are a small, opt-in slice. Do not read them as the overall picture; the first table is the overall one.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;A is 90 and up, B is 75 and up, C is 60 and up, D is 40 and up, and F is below 40.&lt;/li&gt;
&lt;li&gt;Each problem takes points off based on how serious it is. A serious problem also caps the grade. One critical finding keeps a site at F. One high-severity finding keeps it at D or below.&lt;/li&gt;
&lt;li&gt;The free check shows only the worst problem it found, with a plain-English fix. It does not list everything.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the checker looks at
&lt;/h2&gt;

&lt;p&gt;It only reads what any visitor can already see. It does not log in, guess passwords or try to break anything, and it follows robots.txt.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does the padlock (HTTPS) work, and does http redirect to https?&lt;/li&gt;
&lt;li&gt;Are the usual browser safety settings (security headers) set?&lt;/li&gt;
&lt;li&gt;Are private files like /.env or other sensitive paths reachable from the outside?&lt;/li&gt;
&lt;li&gt;Do the pages load?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is not a penetration test. It cannot see behind a login and it cannot judge your business logic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method notes and limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Source: a read-only query of the free check results table in our database.&lt;/li&gt;
&lt;li&gt;Window: Oct 20 to 26, 2026.&lt;/li&gt;
&lt;li&gt;Latest grade per domain: if a domain was checked more than once, only its most recent grade is counted in the A/B vs C/D/F split. The 645 figure counts every check, including repeats.&lt;/li&gt;
&lt;li&gt;Exclusions: our own test domains, deployvet.com and example.com. Some other test-looking domains may remain in the data, so treat the counts as approximate.&lt;/li&gt;
&lt;li&gt;Not a random sample. These are sites people typed in themselves. Sites whose owners care about security, or who suspect a problem, may be more likely to run it, and I cannot tell which way that pushes the numbers.&lt;/li&gt;
&lt;li&gt;The 650 total on the public counter and the 645 in the query are different counts (different filters and time of day). I am using the query for the split and the counter only as a running total.&lt;/li&gt;
&lt;li&gt;The public board shows only 50 rows at a time (20 highest, 20 lowest, 10 newest), opt-in, with masked domains. I cannot tell you what kinds of sites they were, and I will not name anyone.&lt;/li&gt;
&lt;li&gt;Not every site checked was made with an AI or no-code tool. I do not have a clean way to tell, so I will not make claims about "AI-built sites" as a group.&lt;/li&gt;
&lt;li&gt;Scores can change as the scanner changes. A grade is a snapshot from the day it was run.&lt;/li&gt;
&lt;li&gt;Automated checks make mistakes, both missing things and flagging things that are fine.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I do not know yet
&lt;/h2&gt;

&lt;p&gt;I do not have a verified breakdown of which problems come up most often, so I am not going to guess at one. If I get that checked properly, I will post it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;If you have shipped something built with an AI tool, what is the last thing you check before you share the link?&lt;/p&gt;

&lt;p&gt;I build DeployVet. If you want to try the free check: &lt;a href="https://deployvet.com/?utm_source=devto&amp;amp;utm_campaign=datapost" rel="noopener noreferrer"&gt;https://deployvet.com/?utm_source=devto&amp;amp;utm_campaign=datapost&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>ai</category>
    </item>
    <item>
      <title>Before you send someone your website link, what do you actually check first?</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Mon, 26 Oct 2026 17:00:43 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/before-you-send-someone-your-website-link-what-do-you-actually-check-first-pl8</link>
      <guid>https://dev.to/selfhostcalc/before-you-send-someone-your-website-link-what-do-you-actually-check-first-pl8</guid>
      <description>&lt;p&gt;Monday question for the group.&lt;/p&gt;

&lt;p&gt;Before you send someone your website link (a customer, your mom, a group like this one), what do you actually check first?&lt;/p&gt;

&lt;p&gt;Me, I used to check exactly one thing: does the homepage load on my phone. That's it. That was the whole security plan.&lt;/p&gt;

&lt;p&gt;Then I learned a site can look perfectly fine on the homepage and still have a broken contact form, a footer from three years ago, or files sitting out in public that should not be.&lt;/p&gt;

&lt;p&gt;So now I'm curious what real people do. Do you click every page? Look for the padlock? Ask your nephew who "does computers"? Just hit send and pray?&lt;/p&gt;

&lt;p&gt;No wrong answers. Well, "pray" is a little wrong.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>security</category>
    </item>
    <item>
      <title>n8n self-hosting prices this week (Oct 26, 2026)</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Mon, 26 Oct 2026 14:27:33 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/n8n-self-hosting-prices-this-week-oct-26-2026-1cgo</link>
      <guid>https://dev.to/selfhostcalc/n8n-self-hosting-prices-this-week-oct-26-2026-1cgo</guid>
      <description>&lt;p&gt;A quick weekly check of what it actually costs to run n8n on the hosts people ask about most. All prices were checked against each host's own pricing page on Oct 26, 2026.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hostinger&lt;/strong&gt; hasn't changed. KVM 1 is $6.49/mo intro and renews at $11.99/mo, and the 24-month plan is $155.76 upfront. Budget for the renewal price, not the intro.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hetzner&lt;/strong&gt;: the cheapest 4 GB plan (CX23, €5.99/mo) shows as not available right now. The 4 GB plan you can actually order, CPX22, is €19.99/mo excl. VAT in EU locations, which is still under DigitalOcean's $24 for 4 GB. The €6.49 CPX02 has only 1 GB RAM, which is too small for most n8n setups.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vultr vs Linode&lt;/strong&gt;: Vultr is cheaper at every size we compared ($10 / $20 / $40 vs $12 / $24 / $48 for 2 / 4 / 8 GB). Linode includes more monthly data transfer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contabo&lt;/strong&gt; Cloud VPS 10 (8 GB RAM) is still the cheapest renewal we track, at $6.60/mo.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Cloud&lt;/strong&gt; Starter is $24/mo ($20/mo billed yearly) for 2,500 executions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two new write-ups this week, for anyone sizing a box:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/how-much-ram-does-n8n-need.html" rel="noopener noreferrer"&gt;How much RAM does n8n need?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/vultr-vs-linode-n8n.html" rel="noopener noreferrer"&gt;Vultr vs Linode for n8n&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want to plug in your own workflow counts, the free &lt;a href="https://selfhostcalc.com/calculator.html" rel="noopener noreferrer"&gt;calculator&lt;/a&gt; compares n8n Cloud with a VPS. Disclosure: some host links on the site are affiliate links, and prices are listed the same either way.&lt;/p&gt;

&lt;p&gt;If you spot a price I got wrong, drop a comment and I'll fix it.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>automation</category>
    </item>
    <item>
      <title>How to check your website's security headers in 5 minutes (and turn on the 4 that matter)</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Mon, 26 Oct 2026 13:18:34 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/how-to-check-your-websites-security-headers-in-5-minutes-and-turn-on-the-4-that-matter-1hk3</link>
      <guid>https://dev.to/selfhostcalc/how-to-check-your-websites-security-headers-in-5-minutes-and-turn-on-the-4-that-matter-1hk3</guid>
      <description>&lt;p&gt;Every time someone visits your website, your server sends a few lines of instructions along with the page. They're called response headers. Some of them tell the browser how careful to be: always use the secure connection, don't let other sites wrap your page in a frame, don't guess file types.&lt;/p&gt;

&lt;p&gt;They cost nothing. They take minutes to add. And a lot of sites, from hand-built WordPress sites to apps made with Lovable or Bolt, ship without them.&lt;/p&gt;

&lt;p&gt;Here's how to check yours and fix the gaps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Look at your headers (2 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Option A: your browser.&lt;/strong&gt; Open your site in Chrome or Firefox. Press F12 (or right-click and choose Inspect). Click the &lt;strong&gt;Network&lt;/strong&gt; tab, then reload the page. Click the first row, which is your page itself. Scroll to &lt;strong&gt;Response Headers&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Option B: one command.&lt;/strong&gt; If you have a terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sI&lt;/span&gt; https://yoursite.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;-I&lt;/code&gt; asks for headers only. You'll get a short list back.&lt;/p&gt;

&lt;p&gt;Now look for these four names:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;code&gt;strict-transport-security&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;x-content-type-options&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;x-frame-options&lt;/code&gt; (or &lt;code&gt;frame-ancestors&lt;/code&gt; inside &lt;code&gt;content-security-policy&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;referrer-policy&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Write down which ones are missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Know what each one does (1 minute)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Strict-Transport-Security (HSTS).&lt;/strong&gt; Tells the browser: "Only ever talk to me over https." Without it, a visitor who types your address without https can land on the plain, unprotected version first. A common value:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;Strict-Transport-Security: max-age=31536000
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Only add this once https works everywhere on your site, including subdomains you plan to cover. Browsers will remember it for the full max-age.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;X-Content-Type-Options.&lt;/strong&gt; Stops the browser from guessing what a file is. One value, always the same:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;X-Content-Type-Options: nosniff
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;X-Frame-Options.&lt;/strong&gt; Stops other sites from loading your page inside a hidden frame and tricking people into clicking things (this is called clickjacking):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;X-Frame-Options: DENY
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you embed your own pages in frames, use &lt;code&gt;SAMEORIGIN&lt;/code&gt; instead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Referrer-Policy.&lt;/strong&gt; Controls how much of your page address gets passed along when someone clicks a link off your site. Useful if your URLs ever hold things like reset tokens or order numbers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;Referrer-Policy: strict-origin-when-cross-origin
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 3: Turn them on (2 minutes, depends on your host)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Vercel.&lt;/strong&gt; Add a &lt;code&gt;vercel.json&lt;/code&gt; in your project root:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"headers"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/(.*)"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"headers"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Strict-Transport-Security"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"max-age=31536000"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"X-Content-Type-Options"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"nosniff"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"X-Frame-Options"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"DENY"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Referrer-Policy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"strict-origin-when-cross-origin"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Netlify.&lt;/strong&gt; Add a file named &lt;code&gt;_headers&lt;/code&gt; to your publish folder:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/*
  Strict-Transport-Security: max-age=31536000
  X-Content-Type-Options: nosniff
  X-Frame-Options: DENY
  Referrer-Policy: strict-origin-when-cross-origin
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Cloudflare in front of your site.&lt;/strong&gt; Use Rules, then Transform Rules, then "Modify Response Header," and add each one. HSTS has its own switch under SSL/TLS, then Edge Certificates.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WordPress.&lt;/strong&gt; Many hosts have a security headers setting in their control panel. If yours doesn't, a well-known security plugin can add them. Pick one plugin, not three.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Wix, Squarespace, Shopify.&lt;/strong&gt; You usually can't edit headers yourself. The platform sets them. Check what you have with Step 1. If something important is missing, ask their support.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Check again
&lt;/h2&gt;

&lt;p&gt;Reload with F12 open, or run the &lt;code&gt;curl&lt;/code&gt; command again. All four should show up. Then click around your site for a minute. If something broke (usually an embedded video or a payment widget inside a frame), that's almost always X-Frame-Options. Switch it to &lt;code&gt;SAMEORIGIN&lt;/code&gt; or allow that one page.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about Content-Security-Policy?
&lt;/h2&gt;

&lt;p&gt;CSP is the strongest header and the easiest to break your site with. It lists exactly where scripts, images and styles may load from. Start with &lt;code&gt;Content-Security-Policy-Report-Only&lt;/code&gt; so the browser reports problems without blocking anything. Fix what it reports, then switch to the real header. Give it its own afternoon.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest part
&lt;/h2&gt;

&lt;p&gt;Headers are seatbelts, not a lock. They won't fix a database that anyone can read or a secret key sitting in your front-end code. But they're the cheapest fix on this list, and the first thing a stranger can see.&lt;/p&gt;

&lt;p&gt;If you'd rather not do Step 1 by hand, DeployVet runs a free outside check of your site. It looks at headers, the padlock, exposed files and broken pages, and explains what it finds in plain English: &lt;a href="https://deployvet.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=howto" rel="noopener noreferrer"&gt;https://deployvet.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=howto&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It reads what's public, the same way a stranger would. It isn't a penetration test.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>A pre-launch security checklist for apps built with Lovable, Bolt and Cursor</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Sun, 25 Oct 2026 12:26:39 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/a-pre-launch-security-checklist-for-apps-built-with-lovable-bolt-and-cursor-29c4</link>
      <guid>https://dev.to/selfhostcalc/a-pre-launch-security-checklist-for-apps-built-with-lovable-bolt-and-cursor-29c4</guid>
      <description>&lt;p&gt;You built an app over a weekend with Lovable, Bolt, Replit or Cursor. It works, the demo looks great, and you are about to share the link. Before you do, spend an hour on the boring stuff. AI tools are good at making things work. They are much less good at making things safe, because "safe" never shows up in a demo.&lt;/p&gt;

&lt;p&gt;This is the checklist I run before any AI-built app gets real users. It is ordered by how often the problem bites, and none of it needs a security background.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Look for secrets in your front end
&lt;/h2&gt;

&lt;p&gt;Anything your browser downloads is public. In Vite projects, every variable starting with &lt;code&gt;VITE_&lt;/code&gt; ends up in the JavaScript bundle. In Next.js it is &lt;code&gt;NEXT_PUBLIC_&lt;/code&gt;. If a Stripe secret key, an OpenAI key or a Supabase &lt;code&gt;service_role&lt;/code&gt; key sits behind one of those prefixes, anyone can copy it.&lt;/p&gt;

&lt;p&gt;Open your deployed site, view the source, and search the JavaScript files for &lt;code&gt;sk_&lt;/code&gt;, &lt;code&gt;service_role&lt;/code&gt; and &lt;code&gt;api_key&lt;/code&gt;. If you find a real secret, rotate it first and then move the call to a server function.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Check your database from the outside
&lt;/h2&gt;

&lt;p&gt;If you use Supabase, the &lt;code&gt;anon&lt;/code&gt; key is meant to be public. That is fine only when Row Level Security (RLS) is switched on for every table in the &lt;code&gt;public&lt;/code&gt; schema and the policies are strict. Run this in the SQL editor:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;tablename&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;pg_tables&lt;/span&gt;
&lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;schemaname&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'public'&lt;/span&gt; &lt;span class="k"&gt;and&lt;/span&gt; &lt;span class="k"&gt;not&lt;/span&gt; &lt;span class="n"&gt;rowsecurity&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Every table it returns can be read by anyone holding your public key. Turn RLS on, then write policies such as &lt;code&gt;using (auth.uid() = user_id)&lt;/code&gt;. Policies that say &lt;code&gt;using (true)&lt;/code&gt; are RLS in name only.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Test as a second user
&lt;/h2&gt;

&lt;p&gt;Create two accounts. Log in as user A, copy the id of one of A's rows, then log in as user B and try to fetch it. If B can read it, your policies only check "is logged in" and not "is the owner". This is the single most common leak in AI-generated apps, and the anon test above will not catch it.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Don't leave files lying around
&lt;/h2&gt;

&lt;p&gt;Visit &lt;code&gt;/.env&lt;/code&gt;, &lt;code&gt;/.git/config&lt;/code&gt;, and any backup file names your project might have produced. Each should return 404 or be blocked. Also check that the build output does not ship source maps you did not intend to publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Payments: trust the webhook, not the redirect
&lt;/h2&gt;

&lt;p&gt;If you take payments, do not mark an order as paid because the user landed on a "thank you" page. Anyone can type that URL. Confirm payment from the provider's webhook, verify the signature on every event, and make the handler idempotent so a retry does not grant access twice.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Auth settings
&lt;/h2&gt;

&lt;p&gt;Set the Site URL and allowed redirect URLs in your auth provider to your real domain, not a wildcard. Make sure password reset and email confirmation actually work in production, with a real inbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Add limits
&lt;/h2&gt;

&lt;p&gt;Signup, login, password reset and any endpoint that sends email or calls a paid API need rate limits. Without them, one script can burn your monthly API budget in an afternoon. Set a spending cap or alert on every paid service.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Headers and HTTPS
&lt;/h2&gt;

&lt;p&gt;Force HTTPS and add the basic security headers: &lt;code&gt;Strict-Transport-Security&lt;/code&gt;, &lt;code&gt;Content-Security-Policy&lt;/code&gt; (even a loose one), &lt;code&gt;X-Content-Type-Options&lt;/code&gt; and a frame policy. Hosts like Vercel and Netlify let you set these in a config file.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Click through your own app
&lt;/h2&gt;

&lt;p&gt;Sign up, log in, reset a password, pay, delete your account, and open every page. Broken links and 500 errors are not security holes, but they are the first thing a stranger sees.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Have a way back
&lt;/h2&gt;

&lt;p&gt;Turn on backups for your database and test one restore. Keep your code in Git and commit before each big AI change, so a bad edit is a one-command undo.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a checklist cannot do
&lt;/h2&gt;

&lt;p&gt;None of this is a penetration test, and I would not call any automated check one. A checker looking at your site from the outside cannot see behind your login, and it cannot judge your business logic. Steps 3, 5 and 6 above need you to try things by hand.&lt;/p&gt;

&lt;p&gt;Full disclosure: I built &lt;a href="https://deployvet.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=firstcustomer" rel="noopener noreferrer"&gt;DeployVet&lt;/a&gt;, a free check that does steps 1, 2, 4, 8 and 9 for you from the outside, because those steps are easy to skip. Use it, use another tool, or just use this list. The point is to look before your users do.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>beginners</category>
    </item>
    <item>
      <title>What self-hosting n8n actually costs in 2026: VPS vs n8n Cloud</title>
      <dc:creator>Hayden</dc:creator>
      <pubDate>Fri, 23 Oct 2026 12:47:26 +0000</pubDate>
      <link>https://dev.to/selfhostcalc/what-self-hosting-n8n-actually-costs-in-2026-vps-vs-n8n-cloud-om6</link>
      <guid>https://dev.to/selfhostcalc/what-self-hosting-n8n-actually-costs-in-2026-vps-vs-n8n-cloud-om6</guid>
      <description>&lt;p&gt;Self-hosting n8n looks cheap until you read the fine print. A $5 VPS headline usually means a 24-month prepay, and the renewal price is what you actually pay long term. Here is what I found when I checked providers' public pricing pages on 2026-10-22.&lt;/p&gt;

&lt;h2&gt;
  
  
  What n8n needs
&lt;/h2&gt;

&lt;p&gt;n8n plus Postgres in Docker idles at roughly 0.5-1 GB of RAM and spikes with large payloads or many concurrent runs. My rule of thumb: 2 GB for light use, 4 GB as a comfortable minimum, 8 GB for heavy workflows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cheapest workable VPS plans (USD/month)
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Specs&lt;/th&gt;
&lt;th&gt;Intro&lt;/th&gt;
&lt;th&gt;Renewal&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Contabo Cloud VPS 10&lt;/td&gt;
&lt;td&gt;4 vCPU, 8 GB, 100 GB&lt;/td&gt;
&lt;td&gt;$5.28&lt;/td&gt;
&lt;td&gt;$6.60&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hostinger KVM 1&lt;/td&gt;
&lt;td&gt;1 vCPU, 4 GB, 50 GB&lt;/td&gt;
&lt;td&gt;$6.49&lt;/td&gt;
&lt;td&gt;$11.99&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;OVHcloud VPS-1&lt;/td&gt;
&lt;td&gt;2 vCPU, 4 GB, 40 GB&lt;/td&gt;
&lt;td&gt;$4.54&lt;/td&gt;
&lt;td&gt;not verified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DigitalOcean Basic 4 GB&lt;/td&gt;
&lt;td&gt;2 vCPU, 4 GB, 80 GB&lt;/td&gt;
&lt;td&gt;$24&lt;/td&gt;
&lt;td&gt;$24&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vultr 4 GB&lt;/td&gt;
&lt;td&gt;2 vCPU, 4 GB, 80 GB&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Contabo and Hostinger need a 24-month term for the intro price. DigitalOcean and Vultr bill hourly with no lock-in, which is worth something if you are not sure yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  n8n Cloud vs self-hosting
&lt;/h2&gt;

&lt;p&gt;n8n Cloud Starter is $24/mo ($20 billed annually) for 2,500 executions; Pro is $60/mo ($50 annually) for 10,000. If you run a few workflows and don't want to maintain a server, Cloud is reasonable. If you run many scheduled workflows, the execution cap is the thing to watch, and a VPS has no cap beyond its hardware. Details: &lt;a href="https://selfhostcalc.com/compare/n8n-cloud-vs-self-hosted.html" rel="noopener noreferrer"&gt;n8n Cloud vs self-hosted&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Costs people forget
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Backups&lt;/strong&gt;: snapshots usually add 10-20%, or run a nightly pg_dump to object storage. Back up your N8N_ENCRYPTION_KEY too, without it your credentials are gone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Domain&lt;/strong&gt;: about $10-15/year. TLS via Let's Encrypt is free.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your time&lt;/strong&gt;: a couple of hours to set up, then about an hour a month for updates and checks.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The tools
&lt;/h2&gt;

&lt;p&gt;I built StackCost to put these numbers side by side, with renewal prices shown first and unverified numbers left blank:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://selfhostcalc.com" rel="noopener noreferrer"&gt;selfhostcalc.com&lt;/a&gt; - price tracker&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://selfhostcalc.com/calculator.html" rel="noopener noreferrer"&gt;Calculator&lt;/a&gt; - estimate your monthly cost&lt;/li&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/compare/cheapest-vps-for-n8n.html" rel="noopener noreferrer"&gt;Cheapest VPS for n8n&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://selfhostcalc.com/data/hosts.json" rel="noopener noreferrer"&gt;Raw data&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Disclosure: I run the site. Some "View deal" links may become affiliate links in the future; see the &lt;a href="https://selfhostcalc.com/affiliate-disclosure.html" rel="noopener noreferrer"&gt;affiliate disclosure&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>selfhosted</category>
      <category>automation</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
