[{"data":1,"prerenderedAt":1128},["ShallowReactive",2],{"blog-en-stripe-webhook-no-signatures-found":3,"blog-index-en":598},{"id":4,"title":5,"body":6,"category":555,"cover":556,"coverAlt":557,"description":558,"draft":559,"extension":560,"faq":561,"image":577,"keywords":578,"meta":586,"navigation":587,"ogTitle":588,"path":589,"published":590,"seo":591,"stem":592,"tldr":593,"updated":590,"__hash__":597},"blog_en\u002Fblog\u002Fstripe-webhook-no-signatures-found.md","\"No signatures found matching the expected signature\" in Supabase",{"type":7,"value":8,"toc":543},"minimark",[9,13,24,32,37,40,47,68,71,75,78,84,95,104,110,117,123,126,130,133,136,179,205,208,213,217,225,310,317,321,324,344,350,364,367,371,374,388,395,398,418,430,434,440,449,463,473,490,494,530],[10,11,12],"p",{},"You connected Stripe to your app, a test payment went through, and the webhook\nthat should mark the order as paid did nothing. Stripe's dashboard shows the\ndelivery failing, and your Supabase Edge Function's logs say this:",[14,15,20],"pre",{"className":16,"code":18,"language":19},[17],"language-text","No signatures found matching the expected signature for payload.\nAre you passing the raw request body you received from Stripe?\n","text",[21,22,18],"code",{"__ignoreMap":23},"",[10,25,26,27,31],{},"The good news is in where this error comes from. It is thrown by the part of\nyour function that checks the request really came from Stripe, which means that\ncheck exists and is doing its job. ",[28,29,30],"strong",{},"\"No signatures found matching the expected\nsignature for payload\" has two causes, and neither of them is fixed by checking\nless."," The fix that turns up first when people search it, wrapping the check so\nthe error is ignored, is the one that lets anyone mark an order as paid.",[33,34,36],"h2",{"id":35},"what-does-no-signatures-found-matching-the-expected-signature-mean","What does \"No signatures found matching the expected signature\" mean?",[10,38,39],{},"Your function checked Stripe's signature on the request, and it did not match.",[10,41,42,43,46],{},"Think of every webhook Stripe sends as a letter closed with a wax seal. Stripe\npresses the seal with a stamp only it and you hold: your endpoint's signing\nsecret, a value starting ",[21,44,45],{},"whsec_",". When the letter arrives, your function\npresses its own copy of the stamp against the wax. If the patterns line up, the\nletter is from Stripe and nobody has touched it on the way.",[10,48,49,50,53,54,61,62,67],{},"The seal covers the letter exactly as it was written. Stripe's library takes the\ntext of the request, the time from the ",[21,51,52],{},"Stripe-Signature"," header and your\nsecret, works out what the signature should be, and looks for it in that\nheader. The message above, written into\n",[55,56,60],"a",{"href":57,"rel":58},"https:\u002F\u002Fgithub.com\u002Fstripe\u002Fstripe-node\u002Fblob\u002Fmaster\u002Fsrc\u002FWebhooks.ts",[59],"nofollow","stripe-node itself",",\nis what it throws when nothing there matches. Stripe's\n",[55,63,66],{"href":64,"rel":65},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks\u002Fsignature",[59],"signature troubleshooting page","\nputs it plainly: at least one of the three things you passed in is wrong.",[10,69,70],{},"So there are two places to look. Either the letter was changed before your\nfunction checked the seal, or your function is holding the wrong stamp.",[33,72,74],{"id":73},"cause-1-the-body-was-changed-before-the-check","Cause 1: the body was changed before the check",[10,76,77],{},"The most common version in an Edge Function is a body that was read as JSON\nfirst and turned back into text for the check.",[14,79,82],{"className":80,"code":81,"language":19},[17],"const event = await req.json()\nawait stripe.webhooks.constructEventAsync(JSON.stringify(event), signature, secret, undefined, cryptoProvider)\n",[21,83,81],{"__ignoreMap":23},[10,85,86,87,90,91,94],{},"That reads naturally and fails every time. ",[21,88,89],{},"req.json()"," keeps the data and\nthrows away the text: the spacing, the line breaks, the order Stripe wrote\nthings in. ",[21,92,93],{},"JSON.stringify"," then writes new text with the same data in it. The\nseal was pressed over Stripe's text, and this is somebody else's copy of the\nletter in different handwriting, so it can never match.",[10,96,97,98,103],{},"What Supabase's own ",[55,99,102],{"href":100,"rel":101},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fsupabase\u002Fblob\u002Fmaster\u002Fexamples\u002Fedge-functions\u002Fsupabase\u002Ffunctions\u002Fstripe-webhooks\u002Findex.ts",[59],"Stripe webhook example","\ndoes instead is read the body once, as text, and hand that string over\nuntouched:",[14,105,108],{"className":106,"code":107,"language":19},[17],"const signature = req.headers.get('Stripe-Signature')\nconst body = await req.text()\nconst event = await stripe.webhooks.constructEventAsync(\n  body,\n  signature,\n  Deno.env.get('STRIPE_WEBHOOK_SIGNING_SECRET'),\n  undefined,\n  cryptoProvider,\n)\n",[21,109,107],{"__ignoreMap":23},[10,111,112,113,116],{},"The comment in that example says why: the verification relies on the raw\nrequest body rather than the parsed JSON. You do not need to parse anything\nyourself afterwards, because ",[21,114,115],{},"constructEventAsync"," returns the event, already\nparsed, once the seal checks out.",[118,119],"diagram",{"alt":120,"caption":121,"src":122},"Two copies of the same webhook body side by side. The left one is the text exactly as it arrived, and its seal lines up with the stamp, ticked. The right one holds the same values rewritten on different lines, and the same stamp no longer lines up with it, crossed in amber.","The signature covers the text Stripe sent, not the data in it. Rewritten text with identical data fails the check.","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fsame-data-other-text-1600x720.png",[10,124,125],{},"The same thing happens outside your code. Stripe's page names frameworks that\nparse or reformat a body before your code sees it, and stripe-node's message\nadds that a tool forwarding webhooks to you has to preserve the exact body,\n\"including JSON formatting and new line style\". If a proxy or a forwarding\nservice sits between Stripe and your function, check that it passes the body on\nexactly as it came.",[33,127,129],{"id":128},"cause-2-the-signing-secret-is-the-wrong-one","Cause 2: the signing secret is the wrong one",[10,131,132],{},"If the body is untouched, the stamp is wrong, and Stripe's page calls this the\nmost common cause of all.",[10,134,135],{},"Three different values can end up in the place where the signing secret goes,\nand they look alike:",[137,138,139,152,165],"ul",{},[140,141,142,145,146,151],"li",{},[28,143,144],{},"The secret of a different endpoint."," Stripe's\n",[55,147,150],{"href":148,"rel":149},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks",[59],"webhooks guide"," says every endpoint gets\nits own secret, and that the same address set up for both test and live mode\nhas a different secret in each. A live payment checked against the test\nendpoint's secret fails, and so does the reverse.",[140,153,154,161,162,164],{},[28,155,156,157,160],{},"The secret printed by ",[21,158,159],{},"stripe listen","."," When you forward events to your\nmachine with Stripe's command line tool, it prints a ",[21,163,45],{}," secret of its\nown. Stripe says it is different from the dashboard endpoint's secret and\nthat the two get mixed up. It works for events the tool forwards and for\nnothing else.",[140,166,167,170,171,174,175,178],{},[28,168,169],{},"Your Stripe API key."," ",[21,172,173],{},"sk_live_…"," or ",[21,176,177],{},"sk_test_…"," is the key your function\nuses to call Stripe. It is not a signing secret, and a check run with it\ncan never match.",[10,180,181,182,185,186,189,190,193,194,197,198,201,202,160],{},"To find the right one, open the endpoint in Stripe's dashboard under\n",[28,183,184],{},"Workbench",", then ",[28,187,188],{},"Webhooks",", and click ",[28,191,192],{},"Reveal secret",". Check the mode\nyou are in first. Then compare it with the one your function reads. In the\nexample above that is ",[21,195,196],{},"STRIPE_WEBHOOK_SIGNING_SECRET",", set on the ",[28,199,200],{},"Edge\nFunction Secrets"," page of your Supabase project or with\n",[21,203,204],{},"supabase secrets set",[10,206,207],{},"One more thing to look at while you are there. If the value was pasted with a\nspace or a line break at the end, stripe-node adds a note to the same error:\n\"The provided signing secret contains whitespace.\" Delete the value and paste it\nagain with nothing after it.",[118,209],{"alt":210,"caption":211,"src":212},"One sealed envelope on the left and three stamps on the right, each labelled whsec_, stripe listen or sk_live_. Only one of the three stamps has the same pattern as the seal and it is ticked. The other two, the secret printed by stripe listen and an sk_live_ API key, carry other patterns and are crossed in amber.","Every endpoint, every mode and the command line tool sign with their own secret. Only the one that signed this event can check it.","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fwhich-stamp-1600x720.png",[33,214,216],{"id":215},"the-messages-that-look-similar-and-mean-something-else","The messages that look similar and mean something else",[10,218,219,220,224],{},"stripe-node throws several errors from the same check, and each points at a\ndifferent problem. All of these are written in\n",[55,221,223],{"href":57,"rel":222},[59],"its webhook code",":",[226,227,228,241],"table",{},[229,230,231],"thead",{},[232,233,234,238],"tr",{},[235,236,237],"th",{},"What your logs say",[235,239,240],{},"What happened",[242,243,244,255,271,284,294],"tbody",{},[232,245,246,252],{},[247,248,249],"td",{},[21,250,251],{},"No signatures found matching the expected signature for payload",[247,253,254],{},"The body was changed, or the secret is the wrong one. This post.",[232,256,257,262],{},[247,258,259],{},[21,260,261],{},"Webhook payload must be provided as a string or a Buffer",[247,263,264,265,267,268,160],{},"You passed the parsed object from ",[21,266,89],{},". Pass the text from ",[21,269,270],{},"req.text()",[232,272,273,278],{},[247,274,275],{},[21,276,277],{},"No stripe-signature header value was provided.",[247,279,280,281,283],{},"The request had no ",[21,282,52],{}," header. It may not have come from Stripe at all.",[232,285,286,291],{},[247,287,288],{},[21,289,290],{},"Timestamp outside the tolerance zone",[247,292,293],{},"The seal matched, but the event is older than the limit. Stripe's libraries default to 5 minutes.",[232,295,296,301],{},[247,297,298],{},[21,299,300],{},"SubtleCryptoProvider cannot be used in a synchronous context.",[247,302,303,304,307,308,160],{},"You called ",[21,305,306],{},"constructEvent",". With the Web Crypto provider Deno needs, use ",[21,309,115],{},[10,311,312,313,316],{},"And one that never reaches your code. If Stripe's dashboard shows the delivery\nfailing with a ",[28,314,315],{},"401"," and your function's logs are empty, Supabase's platform\nturned the request away before your function ran, because of a check that has\nto be off for a webhook.",[33,318,320],{"id":319},"why-your-webhook-needs-verify_jwt-off","Why your webhook needs verify_jwt off",[10,322,323],{},"Because Stripe cannot prove who it is the way your app's users do, and with the\ncheck on, every delivery is refused.",[10,325,326,327,330,331,334,335,340,341,224],{},"Supabase puts a check called ",[21,328,329],{},"verify_jwt"," in front of every Edge Function, on by\ndefault. It wants a Supabase token in the request's ",[21,332,333],{},"Authorization"," header, and\nStripe has none to send. Supabase's\n",[55,336,339],{"href":337,"rel":338},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Ffunction-configuration",[59],"function configuration guide","\nuses exactly this as its example, saying Stripe webhooks \"need to be publicly\naccessible\", and turns the check off for that one function in\n",[21,342,343],{},"supabase\u002Fconfig.toml",[14,345,348],{"className":346,"code":347,"language":19},[17],"[functions.stripe-webhook]\nverify_jwt = false\n",[21,349,347],{"__ignoreMap":23},[10,351,352,353,356,357,360,361,160],{},"The ",[21,354,355],{},"supabase functions deploy"," command takes ",[21,358,359],{},"--no-verify-jwt"," for the same\nthing. Supabase's Stripe example carries the same instruction in a comment:\nStripe verifies the request via its signature, so deploy with\n",[21,362,363],{},"verify_jwt = false",[10,365,366],{},"With the platform check off, every request on the internet reaches your code,\nand the seal check inside your function is the only thing that tells Stripe's\nletters from anybody else's.",[33,368,370],{"id":369},"why-you-should-never-skip-the-signature-check","Why you should never skip the signature check",[10,372,373],{},"Because without it, anyone can tell your app that a payment went through.",[10,375,376,377,380,381,384,385,387],{},"A webhook function's address is your project's URL, which is in your frontend\nfor anyone to read, followed by ",[21,378,379],{},"\u002Ffunctions\u002Fv1\u002F"," and the function's name, which\nis usually the obvious one. The configuration guide's own example calls it\n",[21,382,383],{},"stripe-webhook",". With ",[21,386,329],{}," off, the platform lets every request\nthrough to your code. If your code no longer checks the seal, it believes every\nletter it gets.",[10,389,390,391,394],{},"So a stranger sends your function a request saying ",[21,392,393],{},"checkout.session.completed","\nwith an order or a customer of their choosing in it. Your function does what it\ndoes with a real one: marks the order paid, upgrades the account, unlocks the\ndownload. Nobody paid. Stripe has no record of it, because Stripe never sent it.",[10,396,397],{},"Three versions of skipping the check all end there:",[137,399,400,406,412],{},[140,401,402,405],{},[28,403,404],{},"Deleting it"," because it would not pass.",[140,407,408,411],{},[28,409,410],{},"Catching the error and carrying on",", logging the failure and processing\nthe event anyway. The example returns a 400 from its catch block, and that\nis the shape to keep: a request that fails the check stops there.",[140,413,414,417],{},[28,415,416],{},"Setting the timestamp tolerance to 0."," Stripe's webhooks guide says not\nto: 0 turns the age check off entirely, so a real event someone captured can\nbe sent again later.",[10,419,420,421,425,426,160],{},"A live Stripe secret key in your frontend is the other way payments go wrong,\nand it is the one we can see from outside: we found one in\n",[55,422,424],{"href":423},"\u002Fblog\u002Fstripe-secret-key-in-frontend","3 of 30,998 scanned apps",". Our free scan\nreads your live app's JavaScript the way a stranger would and names every key it\nfinds, including whether it is one that belongs there. It takes about 20 seconds\nand needs no account: ",[55,427,429],{"href":428},"\u002Fsecurity-scanner","scan your app",[33,431,433],{"id":432},"if-a-forged-payment-ever-gets-through","If a forged payment ever gets through",[10,435,436,439],{},[28,437,438],{},"A check removed by a prompt does not announce itself."," A builder asked to\nmake the webhook work again is free to take the shortcut above, and your app\nkeeps working while it does.",[10,441,442],{},[28,443,444,448],{},[55,445,447],{"href":446},"\u002Fwebsite-monitoring","Reeve Monitor"," watches what a stranger can see from outside:",[137,450,451,454,457,460],{},[140,452,453],{},"all nine checks every hour, on up to three apps",[140,455,456],{},"an email the day a re-scan grades your app lower than the one before; a secret key in your JavaScript caps the grade at D on its own",[140,458,459],{},"whether the app is up, every 60 seconds",[140,461,462],{},"a monthly report of what it saw",[10,464,465],{},[28,466,467,468,472],{},"A forged event writes to your database like a real one. ",[55,469,471],{"href":470},"\u002Fsupabase-backups","Reeve Care","\nkeeps a copy of your Supabase database from before it happened.",[137,474,475,478,481,484,487],{},[140,476,477],{},"an encrypted copy on a schedule, kept on Reeve's own storage in the EU, outside your Supabase account",[140,479,480],{},"each copy verified before it counts, by counting the rows in every table",[140,482,483],{},"a one-click restore that saves what is there now before it replaces anything",[140,485,486],{},"your uploaded files as well, once you connect a Storage credential",[140,488,489],{},"everything Monitor does",[33,491,493],{"id":492},"what-to-do-now","What to do now",[495,496,497],"key-takeaways",{},[137,498,499,502,515,521,527],{},[140,500,501],{},"Open the failed delivery in Stripe's dashboard and your function's Logs tab, and read the exact message before you change anything.",[140,503,504,505,508,509,511,512,514],{},"Read the body with ",[21,506,507],{},"await req.text()"," and pass that string to ",[21,510,115],{},", untouched. Never ",[21,513,93],{}," an event to check it.",[140,516,517,518,520],{},"Copy the ",[21,519,45],{}," secret from the endpoint Stripe is sending from, in the right mode, and paste it into Edge Function Secrets with nothing after it.",[140,522,523,524,526],{},"Keep ",[21,525,363],{}," on the webhook, and keep the signature check as the first thing the function does.",[140,528,529],{},"Return a 400 when the check fails. Never catch the error and process the event anyway.",[10,531,532,533,537,538,542],{},"The rest of what a function holding a secret needs is in\n",[55,534,536],{"href":535},"\u002Fblog\u002Fmove-a-secret-to-an-edge-function","moving a secret into an Edge Function",",\nand if the error you have is the generic one from supabase-js,\n",[55,539,541],{"href":540},"\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code","reading a non-2xx status code","\ncovers where the real message is.",{"title":23,"searchDepth":544,"depth":544,"links":545},3,[546,548,549,550,551,552,553,554],{"id":35,"depth":547,"text":36},2,{"id":73,"depth":547,"text":74},{"id":128,"depth":547,"text":129},{"id":215,"depth":547,"text":216},{"id":319,"depth":547,"text":320},{"id":369,"depth":547,"text":370},{"id":432,"depth":547,"text":433},{"id":492,"depth":547,"text":493},"Security basics","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fcover-1200x630.png","A sealed envelope with a teal wax seal, and beside it a seal stamp whose pattern does not match the impression, marked in amber.","A Stripe webhook in a Supabase Edge Function that says \"No signatures found matching the expected signature\" has one of two causes. Never stop checking.",false,"md",[562,565,568,571,574],{"q":563,"a":564},"What does \"No signatures found matching the expected signature for payload\" mean?","Your webhook function computed the signature it expected from the request body and your signing secret, and none of the signatures in the Stripe-Signature header matched it. Stripe's library throws this when the body it was given is not byte for byte what Stripe sent, or when the secret is not the one for the endpoint that sent the event.",{"q":566,"a":567},"Why does it fail when I pass JSON.stringify of the event?","Because the signature covers the exact text Stripe sent, spaces and line breaks included. Parsing the body with req.json() and turning it back into text with JSON.stringify gives you the same data in different text, and different text has a different signature. Read the body once with await req.text() and pass that string to constructEventAsync.",{"q":569,"a":570},"Which signing secret do I use?","The whsec_ secret of the exact endpoint Stripe is delivering to. Every endpoint has its own, the same address set up in test and in live mode has a different secret in each, and the stripe listen command prints a secret of its own that only works for events it forwards. Your sk_ API key is not a signing secret at all.",{"q":572,"a":573},"Should my Stripe webhook Edge Function have verify_jwt turned off?","Yes. Stripe has no Supabase token to send, so with the check on, every delivery is refused with a 401 before your code runs. Supabase's own Stripe example says to deploy it with verify_jwt = false. That makes the signature check inside your function the only check there is, so it must never be skipped or caught and ignored.",{"q":575,"a":576},"Can I remove the signature check to get payments working?","You can, and anyone who finds the function's address can then send it an event that says a payment succeeded. The address is your project URL, which is in your frontend, plus the function's name. Without the check, your function believes every request it gets and grants whatever the event says was paid for.","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fcard-800x500.png",[579,580,581,582,583,584,585],"no signatures found matching the expected signature for payload","stripe webhook supabase edge function","stripe signature verification failed","constructEventAsync deno","stripe webhook raw body","stripe webhook signing secret","supabase stripe webhook 401",{},true,"\"No signatures found matching the expected signature\"","\u002Fblog\u002Fstripe-webhook-no-signatures-found","2026-10-29",{"title":5,"description":558},"blog\u002Fstripe-webhook-no-signatures-found",[594,595,596],"\"No signatures found matching the expected signature for payload\" means your function checked Stripe's signature and it did not match. Either the body was changed before the check, or the signing secret is not the one Stripe signed with.","Read the body with await req.text() and pass that string, untouched, to constructEventAsync. Then compare the whsec_ secret your function holds with the one on the exact endpoint Stripe is sending from.","Do not make the error go away by skipping the check. The webhook has to run with verify_jwt = false, so the signature is the only thing stopping a stranger from telling your app a payment succeeded.","MtDXrYfD3KJw-YyM-7gjXSC6kNBhzHrxZAVhQYVs3uM",[599,605,611,617,623,629,635,641,647,653,659,666,667,673,678,684,690,696,702,708,714,720,726,732,738,744,750,756,762,768,774,780,786,792,798,804,809,815,821,827,833,839,845,851,857,863,868,874,880,886,892,898,904,909,915,921,927,933,939,945,951,957,963,969,975,981,987,993,999,1005,1011,1017,1023,1029,1035,1041,1047,1053,1059,1065,1071,1077,1083,1089,1094,1100,1106,1112,1117,1123],{"path":600,"title":601,"description":602,"published":603,"category":555,"image":604,"draft":559},"\u002Fblog\u002Fmax-client-connections-reached","Supabase \"max client connections reached\", explained","Supabase \"max client connections reached\" means the pooler has no room for one more client. The port in your connection string decides the limit.","2026-11-09","\u002Fblog\u002Fmax-client-connections-reached\u002Fcard-800x500.png",{"path":606,"title":607,"description":608,"published":609,"category":555,"image":610,"draft":559},"\u002Fblog\u002Funsupported-provider-provider-is-not-enabled","\"Unsupported provider: provider is not enabled\" in Supabase","\"Unsupported provider: provider is not enabled\" means Google sign-in is off in your Supabase project. How to turn it on, and fix redirect_uri_mismatch.","2026-11-08","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fcard-800x500.png",{"path":612,"title":613,"description":614,"published":615,"category":555,"image":616,"draft":559},"\u002Fblog\u002Fviolates-foreign-key-constraint","\"violates foreign key constraint\" on insert in Supabase","Supabase \"insert or update on table violates foreign key constraint\": your row points at a row that is not there. Which one, why, and the fix.","2026-11-07","\u002Fblog\u002Fviolates-foreign-key-constraint\u002Fcard-800x500.png",{"path":618,"title":619,"description":620,"published":621,"category":555,"image":622,"draft":559},"\u002Fblog\u002Fnull-value-violates-not-null-constraint","\"null value in column violates not-null constraint\" in Supabase","Supabase \"null value in column violates not-null constraint\": a required column arrived empty. Where the null came from, and the fix.","2026-11-06","\u002Fblog\u002Fnull-value-violates-not-null-constraint\u002Fcard-800x500.png",{"path":624,"title":625,"description":626,"published":627,"category":555,"image":628,"draft":559},"\u002Fblog\u002Fauth-session-missing","Supabase \"Auth session missing!\": where the session went","\"Auth session missing!\" is supabase-js finding no signed-in session and stopping before it asks Supabase. Where the session went, and the fix for each.","2026-11-05","\u002Fblog\u002Fauth-session-missing\u002Fcard-800x500.png",{"path":630,"title":631,"description":632,"published":633,"category":555,"image":634,"draft":559},"\u002Fblog\u002Finvalid-claim-missing-sub-claim","Supabase \"invalid claim: missing sub claim\": nobody is signed in","\"invalid claim: missing sub claim\" means Supabase Auth got a genuine token that names no user: your project key, sent where a session belongs.","2026-11-04","\u002Fblog\u002Finvalid-claim-missing-sub-claim\u002Fcard-800x500.png",{"path":636,"title":637,"description":638,"published":639,"category":555,"image":640,"draft":559},"\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function","\"Failed to send a request to the Edge Function\" in Supabase","\"Failed to send a request to the Edge Function\" means the browser got no reply it could read. Its console says why, and whether your function ran.","2026-11-03","\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function\u002Fcard-800x500.png",{"path":642,"title":643,"description":644,"published":645,"category":555,"image":646,"draft":559},"\u002Fblog\u002Fsupabase-auth-redirects-to-localhost","Why Supabase email links redirect to localhost:3000","A Supabase redirect to localhost:3000 means the Site URL was never changed, or your address is missing from Redirect URLs. The fix, and the wildcard to avoid.","2026-11-02","\u002Fblog\u002Fsupabase-auth-redirects-to-localhost\u002Fcard-800x500.png",{"path":648,"title":649,"description":650,"published":651,"category":555,"image":652,"draft":559},"\u002Fblog\u002Femail-link-is-invalid-or-has-expired","Supabase \"Email link is invalid or has expired\" on a fresh link","On a link sent a minute ago, Supabase's \"Email link is invalid or has expired\" usually means a mail filter used it first. How to check and fix it.","2026-11-01","\u002Fblog\u002Femail-link-is-invalid-or-has-expired\u002Fcard-800x500.png",{"path":654,"title":655,"description":656,"published":657,"category":555,"image":658,"draft":559},"\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout","Supabase \"canceling statement due to statement timeout\", explained","Supabase \"canceling statement due to statement timeout\" means a query outran its role's limit, 3 seconds for a visitor. Check the RLS policy first.","2026-10-31","\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout\u002Fcard-800x500.png",{"path":660,"title":661,"description":662,"published":663,"category":664,"image":665,"draft":559},"\u002Fblog\u002Fdatabase-error-deleting-user","\"Database error deleting user\" in Supabase, and what goes with it","\"Database error deleting user\" in Supabase means your database refused the delete. The reason is in your logs, and the fix decides what else is deleted.","2026-10-30","Backups","\u002Fblog\u002Fdatabase-error-deleting-user\u002Fcard-800x500.png",{"path":589,"title":5,"description":558,"published":590,"category":555,"image":577,"draft":559},{"path":668,"title":669,"description":670,"published":671,"category":555,"image":672,"draft":559},"\u002Fblog\u002Fsupabase-invalid-login","\"Invalid login credentials\" in Supabase: the three causes","Supabase says \"Invalid login credentials\" for a wrong password, an unknown email and a Google account. How to tell which, and why it is vague.","2026-10-28","\u002Fblog\u002Fsupabase-invalid-login\u002Fcard-800x500.png",{"path":540,"title":674,"description":675,"published":676,"category":555,"image":677,"draft":559},"\"Edge Function returned a non-2xx status code\" in Supabase","\"Edge Function returned a non-2xx status code\" means your Supabase function answered with an error. Here is where to read the real one.","2026-10-27","\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code\u002Fcard-800x500.png",{"path":679,"title":680,"description":681,"published":682,"category":555,"image":683,"draft":559},"\u002Fblog\u002Fcertificate-not-trusted","Certificate not trusted: the three causes besides expiry","Certificate not trusted, and the date is fine? It names another address, it signed itself, or its chain is missing a link. How to tell which.","2026-10-26","\u002Fblog\u002Fcertificate-not-trusted\u002Fcard-800x500.png",{"path":685,"title":686,"description":687,"published":688,"category":555,"image":689,"draft":559},"\u002Fblog\u002Finvalid-input-syntax-for-type-uuid","Supabase \"invalid input syntax for type uuid\": read the quotes","Supabase \"invalid input syntax for type uuid\" means your app sent something that is not an id. Read the quotes, hold the query, keep the column.","2026-10-25","\u002Fblog\u002Finvalid-input-syntax-for-type-uuid\u002Fcard-800x500.png",{"path":691,"title":692,"description":693,"published":694,"category":555,"image":695,"draft":559},"\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint","Supabase \"duplicate key value violates unique constraint\", explained","Supabase \"duplicate key value violates unique constraint\" means the value is already taken. Find the column, pick a fix, and keep the value off screen.","2026-10-24","\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint\u002Fcard-800x500.png",{"path":697,"title":698,"description":699,"published":700,"category":555,"image":701,"draft":559},"\u002Fblog\u002Fsupabase-relation-does-not-exist","Supabase \"relation does not exist\" when the table is right there","Supabase \"relation does not exist\" or PGRST205 means no table matches the name and schema your query used. Four checks, and what exposing a schema opens.","2026-10-23","\u002Fblog\u002Fsupabase-relation-does-not-exist\u002Fcard-800x500.png",{"path":703,"title":704,"description":705,"published":706,"category":555,"image":707,"draft":559},"\u002Fblog\u002Fsupabase-function-not-found","Supabase PGRST202: \"Could not find the function in the schema cache\"","Supabase \"Could not find the function in the schema cache\" lists the argument names your app sent. Compare them with the function first.","2026-10-22","\u002Fblog\u002Fsupabase-function-not-found\u002Fcard-800x500.png",{"path":709,"title":710,"description":711,"published":712,"category":555,"image":713,"draft":559},"\u002Fblog\u002Fsupabase-schema-cache-column-error","Supabase PGRST204: \"Could not find the column in the schema cache\"","Supabase \"Could not find the column in the schema cache\" usually means a name mismatch. Four checks in order, and the one-line reload.","2026-10-21","\u002Fblog\u002Fsupabase-schema-cache-column-error\u002Fcard-800x500.png",{"path":715,"title":716,"description":717,"published":718,"category":555,"image":719,"draft":559},"\u002Fblog\u002Fsupabase-email-rate-limit-exceeded","Supabase \"Email Rate Limit Exceeded\": two limits, one error code","Supabase \"Email Rate Limit Exceeded\" caps every email your project sends: 2 an hour on the built-in sender. What it counts and how to lift it.","2026-10-20","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fcard-800x500.png",{"path":721,"title":722,"description":723,"published":724,"category":555,"image":725,"draft":559},"\u002Fblog\u002Fsupabase-users-logged-out","Supabase \"Invalid Refresh Token: Refresh Token Not Found\": 3 causes","Supabase \"Invalid Refresh Token: Refresh Token Not Found\" logs your users out. Three causes, and how the auth log tells them apart.","2026-10-19","\u002Fblog\u002Fsupabase-users-logged-out\u002Fcard-800x500.png",{"path":727,"title":728,"description":729,"published":730,"category":555,"image":731,"draft":559},"\u002Fblog\u002Fpermission-denied-for-schema-public","Supabase \"permission denied for schema public\": three causes","Supabase \"permission denied for schema public\" means a missing schema grant. What removed it, and the line that puts it back.","2026-10-18","\u002Fblog\u002Fpermission-denied-for-schema-public\u002Fcard-800x500.png",{"path":733,"title":734,"description":735,"published":736,"category":555,"image":737,"draft":559},"\u002Fblog\u002Fsupabase-bucket-not-found","Supabase \"Bucket not found\": the three things it means","Supabase \"Bucket not found\" is one of three things: a public link to a private bucket, a name that is not an exact match, or the wrong project.","2026-10-17","\u002Fblog\u002Fsupabase-bucket-not-found\u002Fcard-800x500.png",{"path":739,"title":740,"description":741,"published":742,"category":555,"image":743,"draft":559},"\u002Fblog\u002Fsupabase-invalid-jwt","Supabase invalid JWT: which key stopped working?","A Supabase invalid JWT error is PGRST301, and it means a signed token failed verification. On a newer project that token is your user, not your API key.","2026-10-16","\u002Fblog\u002Fsupabase-invalid-jwt\u002Fcard-800x500.png",{"path":745,"title":746,"description":747,"published":748,"category":555,"image":749,"draft":559},"\u002Fblog\u002Fsupabase-single-row-error","Supabase \"multiple (or no) rows returned\" usually means no rows","Supabase returns PGRST116, \"JSON object requested, multiple (or no) rows returned\", when your query found none. A row your rules hide looks missing.","2026-10-15","\u002Fblog\u002Fsupabase-single-row-error\u002Fcard-800x500.png",{"path":751,"title":752,"description":753,"published":754,"category":555,"image":755,"draft":559},"\u002Fblog\u002Fdatabase-error-saving-new-user","\"Database error saving new user\" in Supabase, and where to look","\"Database error saving new user\" means something attached to your Supabase signup failed and it was all rolled back. The real error is in your logs.","2026-10-14","\u002Fblog\u002Fdatabase-error-saving-new-user\u002Fcard-800x500.png",{"path":757,"title":758,"description":759,"published":760,"category":555,"image":761,"draft":559},"\u002Fblog\u002Fwhat-is-supabase","What is Supabase? The database your builder picked for you","What is Supabase: the database, login and file storage behind your app. Supabase runs the servers; the rules about who reads your rows are yours.","2026-10-13","\u002Fblog\u002Fwhat-is-supabase\u002Fcard-800x500.png",{"path":763,"title":764,"description":765,"published":766,"category":555,"image":767,"draft":559},"\u002Fblog\u002Faws-access-key-exposed-in-frontend","An AWS access key exposed in your frontend is not like an OpenAI key","An AWS access key exposed in your frontend reads and writes your storage. The fix is usually a presigned URL rather than a new key.","2026-10-12","\u002Fblog\u002Faws-access-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":769,"title":770,"description":771,"published":772,"category":555,"image":773,"draft":559},"\u002Fblog\u002Fstorage-upload-violates-row-level-security","\"Row-level security policy for table objects\" on upload","\"New row violates row-level security policy for table objects\" means your upload has no insert rule. Making the bucket public does not add one.","2026-10-11","\u002Fblog\u002Fstorage-upload-violates-row-level-security\u002Fcard-800x500.png",{"path":775,"title":776,"description":777,"published":778,"category":555,"image":779,"draft":559},"\u002Fblog\u002Fbase44-security-scan","Base44 security scan: the one thing only it can see","The Base44 security scan checks seven kinds of problem from inside your app. Here is the half it reads that nothing outside can, and the half it never looks at.","2026-10-10","\u002Fblog\u002Fbase44-security-scan\u002Fcard-800x500.png",{"path":781,"title":782,"description":783,"published":784,"category":555,"image":785,"draft":559},"\u002Fblog\u002Fapi-key-leaked-what-to-do","Your API key leaked. Here is the order to do things in","An API key leaked and you want to know what to do first. Not every key in your frontend is one, and the order matters more than the speed.","2026-10-09","\u002Fblog\u002Fapi-key-leaked-what-to-do\u002Fcard-800x500.png",{"path":787,"title":788,"description":789,"published":790,"category":555,"image":791,"draft":559},"\u002Fblog\u002Finfinite-recursion-in-policy-for-relation","\"Infinite recursion detected in policy\" without disabling RLS","\"Infinite recursion detected in policy for relation\" means your Supabase policy asked the table it protects. Here is how to break the circle.","2026-10-08","\u002Fblog\u002Finfinite-recursion-in-policy-for-relation\u002Fcard-800x500.png",{"path":793,"title":794,"description":795,"published":796,"category":555,"image":797,"draft":559},"\u002Fblog\u002Fno-api-key-found-in-request","\"No API key found in request\" in Supabase, and the wrong fix","\"No API key found in request\" means your Supabase request arrived without a key. Most answers you find point at your database rules instead.","2026-10-07","\u002Fblog\u002Fno-api-key-found-in-request\u002Fcard-800x500.png",{"path":799,"title":800,"description":801,"published":802,"category":555,"image":803,"draft":559},"\u002Fblog\u002Fis-base44-safe","Is Base44 safe? What 5,442 live Base44 apps showed","Is Base44 safe? We ran nine checks on 5,442 live Base44 apps. Almost all scored B for reasons the owner never chose, and one question nobody can answer.","2026-10-06","\u002Fblog\u002Fis-base44-safe\u002Fcard-800x500.png",{"path":535,"title":805,"description":806,"published":807,"category":555,"image":808,"draft":559},"Hide an API key: move it to a Supabase Edge Function","Hiding an API key means moving it off the browser, and a Supabase Edge Function is the smallest place to put it. Two steps around the move matter more.","2026-10-05","\u002Fblog\u002Fmove-a-secret-to-an-edge-function\u002Fcard-800x500.png",{"path":810,"title":811,"description":812,"published":813,"category":555,"image":814,"draft":559},"\u002Fblog\u002Fenv-file-exposed-on-your-server","Is your .env file exposed? The twelve paths to check","Is your .env file exposed on your own web server? Twelve addresses tell you in a minute, and a hit means everything in the file is already public.","2026-10-04","\u002Fblog\u002Fenv-file-exposed-on-your-server\u002Fcard-800x500.png",{"path":816,"title":817,"description":818,"published":819,"category":555,"image":820,"draft":559},"\u002Fblog\u002Fis-v0-safe","v0 security: all 1,790 v0 apps we scanned got an A","v0 security, measured on 1,790 live v0 apps: every one graded A. Only 17 named a database, and that is most of what the A is measuring.","2026-10-03","\u002Fblog\u002Fis-v0-safe\u002Fcard-800x500.png",{"path":822,"title":823,"description":824,"published":825,"category":555,"image":826,"draft":559},"\u002Fblog\u002Fis-bolt-safe","Is Bolt safe? What 1,123 live Bolt apps showed","Is Bolt safe? We ran nine checks on 1,123 live Bolt apps. The hosting came back clean. The findings were API keys and open tables inside the apps.","2026-10-02","\u002Fblog\u002Fis-bolt-safe\u002Fcard-800x500.png",{"path":828,"title":829,"description":830,"published":831,"category":555,"image":832,"draft":559},"\u002Fblog\u002Fis-supabase-down-or-your-app","Is Supabase down, or is it your app? How to tell","Is Supabase down, or is it your app? A paused project, a full database and a bug of your own all look like an outage. Four checks tell them apart.","2026-10-01","\u002Fblog\u002Fis-supabase-down-or-your-app\u002Fcard-800x500.png",{"path":834,"title":835,"description":836,"published":837,"category":555,"image":838,"draft":559},"\u002Fblog\u002Fdoes-supabase-encrypt-my-data","Does Supabase encrypt my data? Yes. Here is what it stops","Does Supabase encrypt data? Yes: AES-256 at rest, TLS in transit, SOC 2 and ISO 27001 audited. What each one covers, and the leak none of them stops.","2026-09-30","\u002Fblog\u002Fdoes-supabase-encrypt-my-data\u002Fcard-800x500.png",{"path":840,"title":841,"description":842,"published":843,"category":555,"image":844,"draft":559},"\u002Fblog\u002Fsupabase-free-plan-limits","Supabase free plan limits, and what happens at each one","The Supabase free plan limits you to 500 MB of database and 5 GB of egress, with no backups. What happens as you cross each line, and what $25 changes.","2026-09-29","\u002Fblog\u002Fsupabase-free-plan-limits\u002Fcard-800x500.png",{"path":846,"title":847,"description":848,"published":849,"category":664,"image":850,"draft":559},"\u002Fblog\u002Ftest-your-supabase-backup","Test your Supabase backup before the day you need it","How to test your Supabase backup: restore it into a spare project, compare the row counts, sign in, and check for the line a cut-off file is missing.","2026-09-28","\u002Fblog\u002Ftest-your-supabase-backup\u002Fcard-800x500.png",{"path":852,"title":853,"description":854,"published":855,"category":664,"image":856,"draft":559},"\u002Fblog\u002Fsupabase-backup-github-action","Free Supabase backup with a GitHub Action, and the catch","A Supabase backup GitHub Action costs nothing and suits a lot of apps. The workflow, the connection string that works on GitHub, and the egress each run uses.","2026-09-27","\u002Fblog\u002Fsupabase-backup-github-action\u002Fcard-800x500.png",{"path":858,"title":859,"description":860,"published":861,"category":664,"image":862,"draft":559},"\u002Fblog\u002Fdownload-your-supabase-backup","Why you can't download your Supabase backup","You can't download your Supabase backup on a current project, because the daily copy is a physical snapshot. How to tell, and how to hold a copy of your own.","2026-09-26","\u002Fblog\u002Fdownload-your-supabase-backup\u002Fcard-800x500.png",{"path":864,"title":865,"description":866,"published":861,"category":555,"image":867,"draft":559},"\u002Fblog\u002Fsupabase-permission-denied-for-table","Supabase \"permission denied for table\": the missing grant","From October 30, a new Supabase table answers \"permission denied for table\" until you grant access. The grant the email shows is half the fix.","\u002Fblog\u002Fsupabase-permission-denied-for-table\u002Fcard-800x500.png",{"path":869,"title":870,"description":871,"published":872,"category":555,"image":873,"draft":559},"\u002Fblog\u002Fopen-api-endpoint-exposed","Is an open API endpoint a security problem? Look at the JSON","Your scan flagged an open API endpoint. Whether it matters depends on what came back, and most of the ones we found were the platform's own.","2026-09-25","\u002Fblog\u002Fopen-api-endpoint-exposed\u002Fcard-800x500.png",{"path":875,"title":876,"description":877,"published":878,"category":555,"image":879,"draft":559},"\u002Fblog\u002Flovable-security-scan","Lovable security scan: the one thing it cannot prove","Lovable security scan: what the Quick and Deep scans check, when each one runs, and the one thing no scan from inside your project can prove.","2026-09-24","\u002Fblog\u002Flovable-security-scan\u002Fcard-800x500.png",{"path":881,"title":882,"description":883,"published":884,"category":664,"image":885,"draft":559},"\u002Fblog\u002Fsupabase-backup-auth-users","Why your Supabase dump has no users in it","Run supabase db dump on its own and you get the shape of your database and none of its rows, with the auth schema your users live in left out entirely.","2026-09-23","\u002Fblog\u002Fsupabase-backup-auth-users\u002Fcard-800x500.png",{"path":887,"title":888,"description":889,"published":890,"category":555,"image":891,"draft":559},"\u002Fblog\u002Fdomain-and-certificate-expiry","Domain expired, website down: what actually happens next","Your domain expired and your website is down. Here is the clock you are on, why a lapsed certificate is the easier of the two, and how to check both.","2026-09-22","\u002Fblog\u002Fdomain-and-certificate-expiry\u002Fcard-800x500.png",{"path":893,"title":894,"description":895,"published":896,"category":555,"image":897,"draft":559},"\u002Fblog\u002Fis-lovable-safe","Is Lovable safe? What 18,554 live Lovable apps showed","Is Lovable safe? We ran nine checks on 18,554 live Lovable apps. The platform was the cleanest of five builders. Every finding was inside the app itself.","2026-09-21","\u002Fblog\u002Fis-lovable-safe\u002Fcard-800x500.png",{"path":899,"title":900,"description":901,"published":902,"category":555,"image":903,"draft":559},"\u002Fblog\u002Fvibe-coded-app-security-checklist","The vibe coding security checklist, in nine checks","A vibe coding security checklist with nine items, each one something anyone can verify about your live app from outside, and each with a one-line test.","2026-09-20","\u002Fblog\u002Fvibe-coded-app-security-checklist\u002Fcard-800x500.png",{"path":423,"title":905,"description":906,"published":907,"category":555,"image":908,"draft":559},"A Stripe secret key exposed in your frontend can move money","A Stripe secret key exposed in your frontend can refund, charge and read every customer record you hold. Your pk_live_ key is meant to be there.","2026-09-19","\u002Fblog\u002Fstripe-secret-key-in-frontend\u002Fcard-800x500.png",{"path":910,"title":911,"description":912,"published":913,"category":555,"image":914,"draft":559},"\u002Fblog\u002Fvite-and-next-public-env-vars","Vite env variables exposed: VITE_ and NEXT_PUBLIC_ mean publish this","Vite env variables exposed in your app did what the prefix asked. VITE_ and NEXT_PUBLIC_ mean publish this, and the AI that added one never knew the cost.","2026-09-18","\u002Fblog\u002Fvite-and-next-public-env-vars\u002Fcard-800x500.png",{"path":916,"title":917,"description":918,"published":919,"category":555,"image":920,"draft":559},"\u002Fblog\u002Fbase44-source-maps","Base44 security: what a scan flags, and what is yours to fix","Base44 security on 5,438 scanned apps: three findings on nearly every one are the platform's, the source map is Base44's badge, and what is yours is short.","2026-09-17","\u002Fblog\u002Fbase44-source-maps\u002Fcard-800x500.png",{"path":922,"title":923,"description":924,"published":925,"category":555,"image":926,"draft":559},"\u002Fblog\u002Fis-cursor-ai-safe","Is Cursor AI safe? The editor, the code, and the app you shipped","Is Cursor AI safe? Three questions in one search: what Cursor keeps, what the code it writes gets wrong, and whether the app you shipped is open.","2026-09-16","\u002Fblog\u002Fis-cursor-ai-safe\u002Fcard-800x500.png",{"path":928,"title":929,"description":930,"published":931,"category":555,"image":932,"draft":559},"\u002Fblog\u002Fis-replit-safe","Is Replit safe? What we found in 3,042 live Replit apps","Is Replit safe? We ran nine external checks on 3,042 live Replit apps. The host was not where the findings were. The app each owner published was.","2026-09-15","\u002Fblog\u002Fis-replit-safe\u002Fcard-800x500.png",{"path":934,"title":935,"description":936,"published":937,"category":664,"image":938,"draft":559},"\u002Fblog\u002Fsupabase-storage-backup","Supabase storage backup: why your database copy has no files","A Supabase storage backup is a separate job. Database backups keep the list of your files and none of the files, so a restore leaves every upload broken.","2026-09-14","\u002Fblog\u002Fsupabase-storage-backup\u002Fcard-800x500.png",{"path":940,"title":941,"description":942,"published":943,"category":664,"image":944,"draft":559},"\u002Fblog\u002Fsupabase-point-in-time-recovery","Supabase point-in-time recovery: what it costs, what it misses","Supabase point-in-time recovery rewinds your database to any second in the last week. It costs $100 a month on top of Pro, and it covers your database only.","2026-09-13","\u002Fblog\u002Fsupabase-point-in-time-recovery\u002Fcard-800x500.png",{"path":946,"title":947,"description":948,"published":949,"category":664,"image":950,"draft":559},"\u002Fblog\u002Fsupabase-project-paused-recover","Supabase project paused? Your data is still there","Supabase paused your project after a week of inactivity. Nothing is deleted, Restore sits beside the project name, and you have a year before that changes.","2026-09-12","\u002Fblog\u002Fsupabase-project-paused-recover\u002Fcard-800x500.png",{"path":952,"title":953,"description":954,"published":955,"category":555,"image":956,"draft":559},"\u002Fblog\u002Fsafest-ai-app-builder","Which AI app builder is safest? We scanned 30,998 apps","Which AI app builder is safest? We scanned 30,998 live apps from Lovable, Base44, Replit, v0 and Bolt. The builder is not what decides your grade.","2026-09-11","\u002Fblog\u002Fsafest-ai-app-builder\u002Fcard-800x500.png",{"path":958,"title":959,"description":960,"published":961,"category":555,"image":962,"draft":559},"\u002Fblog\u002Fenable-rls-on-every-supabase-table","Enable Row Level Security on every Supabase table, then prove it","Enabling Row Level Security in Supabase with no policy locks a table completely. A policy without the setting does nothing. Here is the SQL, and the test.","2026-09-10","\u002Fblog\u002Fenable-rls-on-every-supabase-table\u002Fcard-800x500.png",{"path":964,"title":965,"description":966,"published":967,"category":555,"image":968,"draft":559},"\u002Fblog\u002Fsupabase-rls-disabled-in-public","Supabase \"RLS disabled in public\": what the warning misses","Supabase reports \"RLS disabled in public\" as an error. It says nothing about the read policy that leaves your table just as open to strangers.","2026-09-09","\u002Fblog\u002Fsupabase-rls-disabled-in-public\u002Fcard-800x500.png",{"path":970,"title":971,"description":972,"published":973,"category":555,"image":974,"draft":559},"\u002Fblog\u002Frotate-supabase-service-role-key","How to rotate a leaked Supabase service_role key","Supabase says fix the leak first. Other guides say rotate now. Which is right depends on where your service_role key leaked.","2026-09-08","\u002Fblog\u002Frotate-supabase-service-role-key\u002Fcard-800x500.png",{"path":976,"title":977,"description":978,"published":979,"category":555,"image":980,"draft":559},"\u002Fblog\u002Fvibe-coding-security-scanners-compared","Vibe coding security scanners compared, including ours","The best vibe coding security scanner comes down to three questions no feature list answers. Eight tools compared, with prices, and the jobs Reeve does not do.","2026-09-07","\u002Fblog\u002Fvibe-coding-security-scanners-compared\u002Fcard-800x500.png",{"path":982,"title":983,"description":984,"published":985,"category":555,"image":986,"draft":559},"\u002Fblog\u002Fsupabase-security-checker","Supabase security checker: run the five checks yourself","A Supabase security checker reads your published app instead of your project settings. Here are the five checks it runs, and how to run each one yourself.","2026-09-06","\u002Fblog\u002Fsupabase-security-checker\u002Fcard-800x500.png",{"path":988,"title":989,"description":990,"published":991,"category":555,"image":992,"draft":559},"\u002Fblog\u002Fvibe-coding-security-scanner","Vibe coding security scanner: what a URL scan misses","A vibe coding security scanner reads your live app from outside. Here is what that covers, the four things it cannot see, and how to read the result.","2026-09-05","\u002Fblog\u002Fvibe-coding-security-scanner\u002Fcard-800x500.png",{"path":994,"title":995,"description":996,"published":997,"category":555,"image":998,"draft":559},"\u002Fblog\u002Fmissing-security-headers","Missing security headers: when it actually matters","Missing security headers is the finding our scanner prints most. Here is what it protects against, and when it is the least urgent line on your report.","2026-09-04","\u002Fblog\u002Fmissing-security-headers\u002Fcard-800x500.png",{"path":1000,"title":1001,"description":1002,"published":1003,"category":555,"image":1004,"draft":559},"\u002Fblog\u002Fopenai-api-key-exposed-in-frontend","Your OpenAI API key is exposed in your frontend. Rotate it.","An OpenAI API key exposed in your frontend cannot be locked to a domain. Rotate it today, move the call behind your own endpoint, and cap the spend.","2026-09-03","\u002Fblog\u002Fopenai-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1006,"title":1007,"description":1008,"published":1009,"category":555,"image":1010,"draft":559},"\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps","An API key exposed in your frontend: what 30,998 apps shipped","An API key exposed in your frontend is usually a Google Maps key. We scanned 30,998 live vibe-coded apps and counted which secrets actually leak.","2026-09-02","\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps\u002Fcard-800x500.png",{"path":1012,"title":1013,"description":1014,"published":1015,"category":664,"image":1016,"draft":559},"\u002Fblog\u002Fsupabase-backup-tools-compared","Supabase backup tools compared, including ours","Four kinds of Supabase backup tool, what each one actually copies, and the case where a free GitHub Action beats paying anyone, us included.","2026-09-01","\u002Fblog\u002Fsupabase-backup-tools-compared\u002Fcard-800x500.png",{"path":1018,"title":1019,"description":1020,"published":1021,"category":555,"image":1022,"draft":559},"\u002Fblog\u002Freplit-secrets-explained","How to use secrets in Replit, and what still gets published","How to use secrets in Replit: add one, read it back, and fix the two reasons it comes back undefined. Plus the keys the Secrets tool cannot keep private.","2026-08-31","\u002Fblog\u002Freplit-secrets-explained\u002Fcard-800x500.png",{"path":1024,"title":1025,"description":1026,"published":1027,"category":664,"image":1028,"draft":559},"\u002Fblog\u002Fback-up-supabase-free-tier","Supabase free tier backups: how to make one without a terminal","There are no Supabase free tier backups, so the copy has to come from you. How to make one from the dashboard, and what CSV leaves out.","2026-08-30","\u002Fblog\u002Fback-up-supabase-free-tier\u002Fcard-800x500.png",{"path":1030,"title":1031,"description":1032,"published":1033,"category":555,"image":1034,"draft":559},"\u002Fblog\u002Fis-supabase-secure","Is Supabase secure? Yes. Your project is a separate question","Is Supabase secure? The platform is audited, encrypted and pen-tested. Their own compliance documents say where that stops and your settings begin.","2026-08-29","\u002Fblog\u002Fis-supabase-secure\u002Fcard-800x500.png",{"path":1036,"title":1037,"description":1038,"published":1039,"category":555,"image":1040,"draft":559},"\u002Fblog\u002Fwhere-to-find-supabase-api-keys","Where to find your Supabase API keys: anon, service_role and the URL","Your Supabase project URL, anon key and service_role key are on one dashboard page. Here is where that page is, and which of the four belongs in your app.","2026-08-28","\u002Fblog\u002Fwhere-to-find-supabase-api-keys\u002Fcard-800x500.png",{"path":1042,"title":1043,"description":1044,"published":1045,"category":555,"image":1046,"draft":559},"\u002Fblog\u002Fnew-row-violates-row-level-security-policy","New row violates row-level security policy in Supabase. Now what?","\"New row violates row-level security policy\" means Supabase refused a write. The fix that clears it in ten seconds also reopens the table to everyone.","2026-08-27","\u002Fblog\u002Fnew-row-violates-row-level-security-policy\u002Fcard-800x500.png",{"path":1048,"title":1049,"description":1050,"published":1051,"category":555,"image":1052,"draft":559},"\u002Fblog\u002Fcors-wildcard-security-risk","Is a CORS wildcard a security risk? Usually not.","Is a CORS wildcard a security risk? Usually it is your builder default, and it gives away nothing your server was not already handing to anyone who asked.","2026-08-26","\u002Fblog\u002Fcors-wildcard-security-risk\u002Fcard-800x500.png",{"path":1054,"title":1055,"description":1056,"published":1057,"category":664,"image":1058,"draft":559},"\u002Fblog\u002Fsupabase-branching-is-not-a-backup","Supabase branching is not a backup. It only goes forwards.","Supabase branching is not a backup: a branch starts with none of your data, and merging only moves schema. What it is for, and what to use instead.","2026-08-25","\u002Fblog\u002Fsupabase-branching-is-not-a-backup\u002Fcard-800x500.png",{"path":1060,"title":1061,"description":1062,"published":1063,"category":664,"image":1064,"draft":559},"\u002Fblog\u002Fhow-to-restore-a-supabase-backup","How to restore a Supabase backup, and what breaks after","How to restore a Supabase backup from the dashboard or from a dump file, what the restore replaces, and why your app can still be broken when it finishes.","2026-08-24","\u002Fblog\u002Fhow-to-restore-a-supabase-backup\u002Fcard-800x500.png",{"path":1066,"title":1067,"description":1068,"published":1069,"category":555,"image":1070,"draft":559},"\u002Fblog\u002Fsupabase-storage-bucket-public","Your Supabase storage bucket is public. Is that a problem?","A public Supabase storage bucket means anyone with a file URL can open it. It does not mean anyone can list what is in there. Two different settings.","2026-08-23","\u002Fblog\u002Fsupabase-storage-bucket-public\u002Fcard-800x500.png",{"path":1072,"title":1073,"description":1074,"published":1075,"category":555,"image":1076,"draft":559},"\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend","Is a Google API key exposed in your frontend a problem?","A Google API key exposed in your frontend is the key our scanner finds most often, and usually it is fine. One free setting decides which it is.","2026-08-22","\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1078,"title":1079,"description":1080,"published":1081,"category":664,"image":1082,"draft":559},"\u002Fblog\u002Fai-agent-deleted-my-database","An AI agent deleted my Supabase data. What can I recover?","An AI agent deleted your database data. What you can recover was decided before it ran, and the next few minutes decide how much of it survives.","2026-08-21","\u002Fblog\u002Fai-agent-deleted-my-database\u002Fcard-800x500.png",{"path":1084,"title":1085,"description":1086,"published":1087,"category":555,"image":1088,"draft":559},"\u002Fblog\u002Fcan-anyone-read-your-supabase-database","Can anyone read your Supabase database? We checked 3,680 apps","Can anyone read your Supabase database without logging in? We scanned 30,998 live apps built with AI builders and measured how often the answer is yes.","2026-08-18","\u002Fblog\u002Fcan-anyone-read-your-supabase-database\u002Fcard-800x500.png",{"path":1090,"title":1091,"description":1092,"published":1087,"category":555,"image":1093,"draft":559},"\u002Fblog\u002Fsource-maps-exposed-in-production","Source maps exposed: your app is publishing its original code","An exposed source map lets anyone read your app's original code, comments included. The 30-second check, and what actually matters if yours are public.","\u002Fblog\u002Fsource-maps-exposed-in-production\u002Fcard-800x500.png",{"path":1095,"title":1096,"description":1097,"published":1098,"category":555,"image":1099,"draft":559},"\u002Fblog\u002Fsupabase-new-api-keys","Supabase publishable key: is it the same as the anon key?","Supabase replaced anon and service_role with publishable and secret keys. Which one belongs in your app, and which never does?","2026-08-12","\u002Fblog\u002Fsupabase-new-api-keys\u002Fcard-800x500.png",{"path":1101,"title":1102,"description":1103,"published":1104,"category":664,"image":1105,"draft":559},"\u002Fblog\u002Fdoes-supabase-back-up-my-database","Does Supabase back up my database? It depends on your plan.","Does Supabase back up your database? Daily on paid plans, and not at all on the free one. How to check which you have, and what that copy cannot survive.","2026-08-11","\u002Fblog\u002Fdoes-supabase-back-up-my-database\u002Fcard-800x500.png",{"path":1107,"title":1108,"description":1109,"published":1110,"category":555,"image":1111,"draft":559},"\u002Fblog\u002Fsupabase-rls-on-but-table-still-public","Supabase Row Level Security is on. Your table is still public.","Turning on Supabase Row Level Security does not protect a table. Your policies do, and the policy that fixed your broken app may let everyone in.","2026-08-10","\u002Fblog\u002Fsupabase-rls-on-but-table-still-public\u002Fcard-800x500.png",{"path":1113,"title":1114,"description":1115,"published":1110,"category":664,"image":1116,"draft":559},"\u002Fblog\u002Fversion-history-is-not-a-backup","Version history is not a backup. It cannot undo a deleted table.","Lovable and Bolt keep version history for your code. Your database is a separate service, so rolling back to this morning does not bring your data back.","\u002Fblog\u002Fversion-history-is-not-a-backup\u002Fcard-800x500.png",{"path":1118,"title":1119,"description":1120,"published":1121,"category":664,"image":1122,"draft":559},"\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database","Three ways to back up a Supabase database, and what each misses","The dashboard, pg_dump, and a managed service. What each one actually saves, what it quietly leaves out, and which one survives losing the account.","2026-08-09","\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database\u002Fcard-800x500.png",{"path":1124,"title":1125,"description":1126,"published":1121,"category":555,"image":1127,"draft":559},"\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend","Which API keys are safe in your frontend, and which aren't","Your Supabase anon key is supposed to be public. Your service_role key is not, and it ignores every rule you set. Here is how to tell them apart.","\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend\u002Fcard-800x500.png",1794213635058]