[{"data":1,"prerenderedAt":1091},["ShallowReactive",2],{"blog-en-unsupported-provider-provider-is-not-enabled":3,"blog-index-en":560},{"id":4,"title":5,"body":6,"category":518,"cover":519,"coverAlt":520,"description":521,"draft":522,"extension":523,"faq":524,"image":540,"keywords":541,"meta":548,"navigation":549,"ogTitle":550,"path":551,"published":552,"seo":553,"stem":554,"tldr":555,"updated":552,"__hash__":559},"blog_en\u002Fblog\u002Funsupported-provider-provider-is-not-enabled.md","\"Unsupported provider: provider is not enabled\" in Supabase",{"type":7,"value":8,"toc":507},"minimark",[9,13,24,31,38,41,46,49,52,85,88,97,103,107,110,121,125,134,156,171,204,222,225,310,314,317,333,348,362,365,370,374,377,383,405,412,416,419,428,442,451,471,475,495],[10,11,12],"p",{},"You add a \"Sign in with Google\" button to your app and press it. Instead of\nGoogle's account picker, your browser shows this:",[14,15,20],"pre",{"className":16,"code":18,"language":19},[17],"language-text","{\"code\":400,\"error_code\":\"validation_failed\",\"msg\":\"Unsupported provider: provider is not enabled\"}\n","text",[21,22,18],"code",{"__ignoreMap":23},"",[10,25,26,27,30],{},"The address bar shows your Supabase project, something like\n",[21,28,29],{},"https:\u002F\u002Fabcdefghij.supabase.co\u002Fauth\u002Fv1\u002Fauthorize?provider=google&redirect_to=…",".\nYou built the app with Lovable, Bolt, v0, Cursor, Claude Code or Replit, the\nbutton came with the code, and nothing in that code looks wrong.",[10,32,33,34,37],{},"\"Unsupported provider: provider is not enabled\" means Supabase Auth, the part of\nSupabase that signs people in, has Google switched off in the project your app\ntalks to. The fix is one switch and two values you get from Google. After that,\nGoogle checks a list of its own, and that list is where the next error,\n",[21,35,36],{},"redirect_uri_mismatch",", comes from.",[10,39,40],{},"The trap is in that second list. The address that feels right for it is your\nown app's, and Google never uses it, because Google never sends anyone to your\napp.",[42,43,45],"h2",{"id":44},"what-does-unsupported-provider-provider-is-not-enabled-mean","What does \"Unsupported provider: provider is not enabled\" mean?",[10,47,48],{},"It means Supabase refused to start a Google sign-in, because Google is switched\noff in the project that received the request.",[10,50,51],{},"Signing in with Google is a round trip through two front desks. Your app sends\nthe person to Supabase's desk. Supabase sends them on to Google's desk to prove\nwho they are, Google sends them back to Supabase, and Supabase sends them home\nto your app, signed in. Each desk sends people only where its own settings\nallow. This message is Supabase's desk saying its Google counter is closed.",[10,53,54,55,62,63,66,67,70,71,74,75,78,79,84],{},"In Supabase Auth's\n",[56,57,61],"a",{"href":58,"rel":59},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fauth\u002Fblob\u002Fmaster\u002Finternal\u002Fapi\u002Fexternal.go",[60],"nofollow","source",",\na request to ",[21,64,65],{},"\u002Fauth\u002Fv1\u002Fauthorize"," first looks the provider up, and any problem\nwith it comes back as a 400 with the code ",[21,68,69],{},"validation_failed"," and\n",[21,72,73],{},"Unsupported provider:"," in front of the reason. ",[21,76,77],{},"provider is not enabled"," is\n",[56,80,83],{"href":81,"rel":82},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fauth\u002Fblob\u002Fmaster\u002Finternal\u002Fconf\u002Fconfiguration.go",[60],"the first thing that lookup checks",".",[10,86,87],{},"So Google never saw the request, and nothing in Google's console will explain\nit. Your app never sees the error either: Supabase's JavaScript library sends\nthe whole browser to that address, so the page that fails belongs to Supabase,\nand your app's console stays empty.",[10,89,90,91,96],{},"The same message appears for GitHub, Apple or any other provider that is\nswitched off, and the switch is in the same place. Apps on Lovable's built-in\nbackend are set up differently: Lovable's\n",[56,92,95],{"href":93,"rel":94},"https:\u002F\u002Fdocs.lovable.dev\u002Ffeatures\u002Fauthentication",[60],"authentication docs"," list\nGoogle as \"managed by Lovable with no setup, or your own Google Cloud OAuth\ncredentials.\" This post is for apps on your own Supabase project, whichever tool\nbuilt them.",[98,99],"diagram",{"alt":100,"caption":101,"src":102},"A browser leaves an app and reaches Supabase, where the Google switch is off. The route on to Google is dashed and crossed out, and a 400 goes back to the browser.","Supabase answers before Google is asked, so the error is Supabase's and the fix is in Supabase.","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fwhere-it-stops-1600x760.png",[42,104,106],{"id":105},"is-it-the-right-supabase-project","Is it the right Supabase project?",[10,108,109],{},"Check that before you change anything, because the error page names the project\nthat answered.",[10,111,112,113,116,117,120],{},"The address on the error page starts with your project's reference, the string\nof letters before ",[21,114,115],{},".supabase.co",". Open your Supabase dashboard and look at its\nown address bar: the same reference follows ",[21,118,119],{},"\u002Fproject\u002F",". If the two differ, your\napp talks to another project, such as one a builder created for you or a copy\nyou made for testing. That is the project where Google has to be switched on.",[42,122,124],{"id":123},"how-to-fix-unsupported-provider-provider-is-not-enabled","How to fix \"Unsupported provider: provider is not enabled\"",[10,126,127,128,133],{},"Create an OAuth client in Google, then switch Google on in Supabase with the two\nvalues it gives you. Supabase's\n",[56,129,132],{"href":130,"rel":131},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fsocial-login\u002Fauth-google",[60],"Google sign-in guide","\nhas the steps; here they are in the order the two consoles ask for them.",[10,135,136,140,141,144,145,148,149,152,153,84],{},[137,138,139],"strong",{},"In Supabase, copy the callback URL first."," Go to ",[137,142,143],{},"Authentication",", then\n",[137,146,147],{},"Sign In \u002F Providers",", and open ",[137,150,151],{},"Google",". The panel shows a Callback URL with\na Copy button. It looks like ",[21,154,155],{},"https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Fauth\u002Fv1\u002Fcallback",[10,157,158,161,162,167,168,84],{},[137,159,160],{},"In Google Cloud, create the client."," On the\n",[56,163,166],{"href":164,"rel":165},"https:\u002F\u002Fconsole.cloud.google.com\u002Fauth\u002Fclients",[60],"Clients"," page of the Google Auth\nPlatform, create an OAuth client ID of the type ",[137,169,170],{},"Web application",[172,173,174,185,191],"ul",{},[175,176,177,178,181,182,84],"li",{},"Under ",[137,179,180],{},"Authorized JavaScript origins",", add your app's address, such as ",[21,183,184],{},"https:\u002F\u002Fyourapp.com",[175,186,177,187,190],{},[137,188,189],{},"Authorized redirect URIs",", paste the callback URL you copied from Supabase.",[175,192,193,194,197,198,203],{},"Press ",[137,195,196],{},"Create",", and copy the Client ID and the Client Secret straight away. Google's ",[56,199,202],{"href":200,"rel":201},"https:\u002F\u002Fsupport.google.com\u002Fcloud\u002Fanswer\u002F15549257",[60],"help page on OAuth clients"," says you \"will only be able to view and download the full client secret once, at the time of its creation.\"",[10,205,206,209,210,213,214,217,218,221],{},[137,207,208],{},"Back in Supabase, switch it on."," Turn on ",[137,211,212],{},"Enable Sign in with Google",", paste\nthe Client ID into ",[137,215,216],{},"Client IDs"," and the secret into ",[137,219,220],{},"Client Secret (for\nOAuth)",", and save. The dashboard will not save Google switched on without a\nClient ID, but it does save with the secret field empty. That field's own\ndescription says the secret is for \"the OAuth flow on the web\", and a button in\na web app is exactly that flow.",[10,223,224],{},"Then press your button again. If the message still starts with \"Unsupported\nprovider\", its ending says what is left:",[226,227,228,244],"table",{},[229,230,231],"thead",{},[232,233,234,238,241],"tr",{},[235,236,237],"th",{},"The message ends in",[235,239,240],{},"What it means",[235,242,243],{},"What to change",[245,246,247,260,273,290],"tbody",{},[232,248,249,254,257],{},[250,251,252],"td",{},[21,253,77],{},[250,255,256],{},"Google is off in the project that answered",[250,258,259],{},"Switch it on in that project",[232,261,262,267,270],{},[250,263,264],{},[21,265,266],{},"missing OAuth client ID",[250,268,269],{},"Google is on with no Client ID saved",[250,271,272],{},"Paste the Client ID",[232,274,275,280,283],{},[250,276,277],{},[21,278,279],{},"missing OAuth secret",[250,281,282],{},"Google is on and the secret field is empty",[250,284,285,286,289],{},"Paste the secret, or press ",[137,287,288],{},"Add Secret"," on the client in Google if you no longer have it",[232,291,292,297,300],{},[250,293,294],{},[21,295,296],{},"Provider … could not be found",[250,298,299],{},"Your code asks for a provider Supabase does not have",[250,301,302,303,306,307],{},"Use ",[21,304,305],{},"google"," as the provider in ",[21,308,309],{},"signInWithOAuth",[42,311,313],{"id":312},"why-google-then-says-redirect_uri_mismatch","Why Google then says redirect_uri_mismatch",[10,315,316],{},"Because your callback URL is not on the client's list, written exactly as\nSupabase sends it.",[10,318,319,320,322,323,328,329,332],{},"This is the second desk. When Supabase starts the sign-in, it hands the person to\nGoogle with a note saying where to send them back: your project's callback URL.\nGoogle checks that note against ",[137,321,189],{}," on the client you\ncreated. Its\n",[56,324,327],{"href":325,"rel":326},"https:\u002F\u002Fdevelopers.google.com\u002Fidentity\u002Fprotocols\u002Foauth2\u002Fweb-server",[60],"OAuth documentation","\ndescribes the failure in one line: \"The ",[21,330,331],{},"redirect_uri"," passed in the\nauthorization request does not match an authorized redirect URI for the OAuth\nclient ID.\"",[10,334,335,336,339,340,343,344,347],{},"The match is exact. The same page says \"the ",[21,337,338],{},"http"," or ",[21,341,342],{},"https"," scheme, case, and\ntrailing slash ('\u002F') must all match.\" So an entry ending in ",[21,345,346],{},"\u002Fauth\u002Fv1\u002Fcallback\u002F",",\nwith a slash at the end, will not match the address Supabase sends.",[10,349,350,353,354,357,358,84],{},[137,351,352],{},"Your own app's address does nothing on this list."," Google sends people back to\nSupabase, so the only address it ever checks is Supabase's callback. Your app's\naddress belongs on the other desk's list, Supabase's Redirect URLs, which decides\nwhere Supabase sends people at the very end. When that list is wrong, people\ncome back signed in on ",[21,355,356],{},"localhost:3000"," instead, and\n",[56,359,361],{"href":360},"\u002Fblog\u002Fsupabase-auth-redirects-to-localhost","that has a page of its own",[10,363,364],{},"After you save, give Google a little time. Its help page on OAuth clients says\n\"It may take 5 minutes to a few hours for changes made to these settings to take\neffect.\"",[98,366],{"alt":367,"caption":368,"src":369},"Google's list holds the Supabase callback address and sends the person back to Supabase. An entry with the app's own address is crossed out. Supabase's list holds the app's address and sends them home.","Each desk checks its own list. Google's needs the Supabase callback, and Supabase's needs your app.","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Ftwo-lists-1600x760.png",[42,371,373],{"id":372},"where-the-client-secret-belongs","Where the Client Secret belongs",[10,375,376],{},"In the Supabase dashboard, and nowhere else. Your app's code never needs it.",[10,378,379,380,382],{},"The Client ID is public: it travels in the address of Google's sign-in page,\nwhere anyone can read it. The Client Secret is what proves to Google that a\nrequest comes from your side, and in this setup only Supabase holds it. When your\napp calls ",[21,381,309],{},", the library sends the browser to Supabase, and\nSupabase Auth is the one that talks to Google with the secret.",[10,384,385,386,339,389,392,393,397,398,400,401,404],{},"So if your builder put the secret into your app's code, or into a variable whose\nname starts with ",[21,387,388],{},"VITE_",[21,390,391],{},"NEXT_PUBLIC_",", it is in every visitor's browser.\n",[56,394,396],{"href":395},"\u002Fblog\u002Fvite-and-next-public-env-vars","Those variables are public by design",".\nGoogle's help page is plain about it: \"Never add client secrets directly in your\ncode or check them into version control systems such as Git or Subversion.\"\nReplace it on the client's page in Google's console: press ",[137,399,288],{},", paste\nthe new secret into Supabase, then ",[137,402,403],{},"Disable"," the old one and delete it. Take\nthe old value out of your code as well.",[10,406,407,408,84],{},"Checking what your live app hands to visitors does not need the builder open.\nOur free scan reads your live app the way a visitor's browser does and reports\nthe secret keys it recognises, along with tables that answer anyone and missing\nheaders. It takes about 20 seconds and\nneeds no account: ",[56,409,411],{"href":410},"\u002Fsecurity-scanner","scan your app",[42,413,415],{"id":414},"looking-after-the-app-people-now-sign-in-to","Looking after the app people now sign in to",[10,417,418],{},"Once people sign in with Google, their accounts live in your Supabase project,\nand the app they sign in to changes with every deploy.",[10,420,421],{},[137,422,423,427],{},[56,424,426],{"href":425},"\u002Fwebsite-monitoring","Reeve Monitor"," keeps checking your live app:",[172,429,430,433,436,439],{},[175,431,432],{},"whether it is up, every 60 seconds",[175,434,435],{},"all nine checks every hour, on up to three apps, including secret keys in the code your app sends to visitors",[175,437,438],{},"a message when a result changes, so a key that ships in a later deploy reaches you without you going to look",[175,440,441],{},"a monthly report, in plain language, of what it saw",[10,443,444],{},[137,445,446,450],{},[56,447,449],{"href":448},"\u002Fsupabase-backups","Reeve Care"," keeps a copy of your Supabase database,\naccounts included:",[172,452,453,456,459,462,465,468],{},[175,454,455],{},"an encrypted copy on a schedule, on Reeve's own storage in the EU, outside your Supabase account",[175,457,458],{},"the auth schema, where Supabase keeps each user and the Google identity they signed in with, so they come back with everything else",[175,460,461],{},"each copy verified before it counts, by counting the rows in every table",[175,463,464],{},"your uploaded files as well, once you connect a Storage credential",[175,466,467],{},"a one-click restore, with a safety copy of the current state taken first",[175,469,470],{},"everything Monitor does",[42,472,474],{"id":473},"what-to-do-now","What to do now",[476,477,478],"key-takeaways",{},[172,479,480,483,486,489,492],{},[175,481,482],{},"Read the project reference on the error page, and switch Google on in that project under Authentication, Sign In \u002F Providers.",[175,484,485],{},"Create a Web application client in Google, with your Supabase callback URL under Authorized redirect URIs, exactly as Supabase shows it.",[175,487,488],{},"Paste the Client ID and the Client Secret into the Google panel in Supabase, and save.",[175,490,491],{},"If Google answers redirect_uri_mismatch, compare the two addresses letter for letter, then allow a few minutes for Google's change to apply.",[175,493,494],{},"Keep the Client Secret in Supabase only. If it ever went into your app's code, add a new one in Google and disable the old.",[10,496,497,498,501,502,506],{},"If people get through Google and then land on the wrong page,\n",[56,499,500],{"href":360},"the redirect settings post"," picks up\nfrom there. The ",[56,503,505],{"href":504},"\u002Fchecklist","10-minute security checklist"," covers what else to\nlook at before launch.",{"title":23,"searchDepth":508,"depth":508,"links":509},3,[510,512,513,514,515,516,517],{"id":44,"depth":511,"text":45},2,{"id":105,"depth":511,"text":106},{"id":123,"depth":511,"text":124},{"id":312,"depth":511,"text":313},{"id":372,"depth":511,"text":373},{"id":414,"depth":511,"text":415},{"id":473,"depth":511,"text":474},"Security basics","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fcover-1200x630.png","A settings panel with one provider pulled forward. Its switch is off and outlined in amber, and its two key slots are empty.","\"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.",false,"md",[525,528,531,534,537],{"q":526,"a":527},"Why does Google sign-in open a page of JSON with validation_failed?","Your app sent the browser to your Supabase project's \u002Fauth\u002Fv1\u002Fauthorize address, and Supabase answered there instead of passing the person on to Google. The page reads {\"code\":400,\"error_code\":\"validation_failed\",\"msg\":\"Unsupported provider: provider is not enabled\"}. Your app never receives that answer, which is why its console shows nothing. Switch Google on under Authentication, Sign In \u002F Providers.",{"q":529,"a":530},"I switched Google on and still get the error. Why?","Usually your app talks to a different Supabase project from the one you changed. The address on the error page starts with the project's reference, the letters before .supabase.co; compare it with the reference in your dashboard's address bar. If they match, read the end of the message: \"missing OAuth secret\" means the Client Secret field is still empty.",{"q":532,"a":533},"What goes in Authorized redirect URIs for Supabase?","Your project's callback URL, https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Fauth\u002Fv1\u002Fcallback, copied from the Google entry on the Sign In \u002F Providers page. Google sends people back to Supabase, and Supabase sends them on to your app, so your app's own address belongs on Supabase's Redirect URLs list instead.",{"q":535,"a":536},"Do I have to publish my Google app or add test users?","Not for a sign-in that asks only for name, email address and profile, which is all Supabase asks Google for unless your code adds scopes. Google's page on app audiences says the users of such an app do not need to be on the test user list. Ask for more, such as access to Drive, and the testing limits apply.",{"q":538,"a":539},"I use a custom domain for Supabase. Which callback URL does Google need?","Both. Supabase's custom domain guide says to add the custom domain's callback, such as https:\u002F\u002Fapi.example.com\u002Fauth\u002Fv1\u002Fcallback, in the provider's own console, in addition to the project's supabase.co callback.","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fcard-800x500.png",[542,543,544,545,546,547],"unsupported provider provider is not enabled","supabase google login not working","redirect_uri_mismatch supabase","supabase google oauth callback url","validation_failed unsupported provider","supabase sign in with google",{},true,"Unsupported provider: provider is not enabled in Supabase","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled","2026-11-08",{"title":5,"description":521},"blog\u002Funsupported-provider-provider-is-not-enabled",[556,557,558],"\"Unsupported provider: provider is not enabled\" means the Supabase project your app sent the person to has Google sign-in switched off. Turn it on under Authentication, Sign In \u002F Providers, in that same project.","Google then checks a list of its own. Your Supabase callback URL has to be on your OAuth client's Authorized redirect URIs, letter for letter, or Google answers redirect_uri_mismatch.","The Client Secret goes into the Supabase dashboard and nowhere else. Your app's code never needs it.","na-TvAqIpuN1H9MBb_YqhHl8FfhTWQXwButNM4qcsWQ",[561,567,568,574,580,586,592,598,603,609,615,622,628,634,640,646,652,658,664,670,676,682,688,694,700,706,712,718,724,730,736,742,748,754,760,766,772,778,784,790,796,802,808,814,820,826,831,837,843,849,855,861,867,873,878,884,890,896,902,908,914,920,926,932,938,944,950,956,962,968,974,980,986,992,998,1004,1010,1016,1022,1028,1034,1040,1046,1052,1057,1063,1069,1075,1080,1086],{"path":562,"title":563,"description":564,"published":565,"category":518,"image":566,"draft":522},"\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":551,"title":5,"description":521,"published":552,"category":518,"image":540,"draft":522},{"path":569,"title":570,"description":571,"published":572,"category":518,"image":573,"draft":522},"\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":575,"title":576,"description":577,"published":578,"category":518,"image":579,"draft":522},"\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":581,"title":582,"description":583,"published":584,"category":518,"image":585,"draft":522},"\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":587,"title":588,"description":589,"published":590,"category":518,"image":591,"draft":522},"\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":593,"title":594,"description":595,"published":596,"category":518,"image":597,"draft":522},"\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":360,"title":599,"description":600,"published":601,"category":518,"image":602,"draft":522},"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":604,"title":605,"description":606,"published":607,"category":518,"image":608,"draft":522},"\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":610,"title":611,"description":612,"published":613,"category":518,"image":614,"draft":522},"\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":616,"title":617,"description":618,"published":619,"category":620,"image":621,"draft":522},"\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":623,"title":624,"description":625,"published":626,"category":518,"image":627,"draft":522},"\u002Fblog\u002Fstripe-webhook-no-signatures-found","\"No signatures found matching the expected signature\" in Supabase","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.","2026-10-29","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fcard-800x500.png",{"path":629,"title":630,"description":631,"published":632,"category":518,"image":633,"draft":522},"\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":635,"title":636,"description":637,"published":638,"category":518,"image":639,"draft":522},"\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code","\"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":641,"title":642,"description":643,"published":644,"category":518,"image":645,"draft":522},"\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":647,"title":648,"description":649,"published":650,"category":518,"image":651,"draft":522},"\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":653,"title":654,"description":655,"published":656,"category":518,"image":657,"draft":522},"\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":659,"title":660,"description":661,"published":662,"category":518,"image":663,"draft":522},"\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":665,"title":666,"description":667,"published":668,"category":518,"image":669,"draft":522},"\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":671,"title":672,"description":673,"published":674,"category":518,"image":675,"draft":522},"\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":677,"title":678,"description":679,"published":680,"category":518,"image":681,"draft":522},"\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":683,"title":684,"description":685,"published":686,"category":518,"image":687,"draft":522},"\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":689,"title":690,"description":691,"published":692,"category":518,"image":693,"draft":522},"\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":695,"title":696,"description":697,"published":698,"category":518,"image":699,"draft":522},"\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":701,"title":702,"description":703,"published":704,"category":518,"image":705,"draft":522},"\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":707,"title":708,"description":709,"published":710,"category":518,"image":711,"draft":522},"\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":713,"title":714,"description":715,"published":716,"category":518,"image":717,"draft":522},"\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":719,"title":720,"description":721,"published":722,"category":518,"image":723,"draft":522},"\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":725,"title":726,"description":727,"published":728,"category":518,"image":729,"draft":522},"\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":731,"title":732,"description":733,"published":734,"category":518,"image":735,"draft":522},"\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":737,"title":738,"description":739,"published":740,"category":518,"image":741,"draft":522},"\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":743,"title":744,"description":745,"published":746,"category":518,"image":747,"draft":522},"\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":749,"title":750,"description":751,"published":752,"category":518,"image":753,"draft":522},"\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":755,"title":756,"description":757,"published":758,"category":518,"image":759,"draft":522},"\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":761,"title":762,"description":763,"published":764,"category":518,"image":765,"draft":522},"\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":767,"title":768,"description":769,"published":770,"category":518,"image":771,"draft":522},"\u002Fblog\u002Fmove-a-secret-to-an-edge-function","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":773,"title":774,"description":775,"published":776,"category":518,"image":777,"draft":522},"\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":779,"title":780,"description":781,"published":782,"category":518,"image":783,"draft":522},"\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":785,"title":786,"description":787,"published":788,"category":518,"image":789,"draft":522},"\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":791,"title":792,"description":793,"published":794,"category":518,"image":795,"draft":522},"\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":797,"title":798,"description":799,"published":800,"category":518,"image":801,"draft":522},"\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":803,"title":804,"description":805,"published":806,"category":518,"image":807,"draft":522},"\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":809,"title":810,"description":811,"published":812,"category":620,"image":813,"draft":522},"\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":815,"title":816,"description":817,"published":818,"category":620,"image":819,"draft":522},"\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":821,"title":822,"description":823,"published":824,"category":620,"image":825,"draft":522},"\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":827,"title":828,"description":829,"published":824,"category":518,"image":830,"draft":522},"\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":832,"title":833,"description":834,"published":835,"category":518,"image":836,"draft":522},"\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":838,"title":839,"description":840,"published":841,"category":518,"image":842,"draft":522},"\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":844,"title":845,"description":846,"published":847,"category":620,"image":848,"draft":522},"\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":850,"title":851,"description":852,"published":853,"category":518,"image":854,"draft":522},"\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":856,"title":857,"description":858,"published":859,"category":518,"image":860,"draft":522},"\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":862,"title":863,"description":864,"published":865,"category":518,"image":866,"draft":522},"\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":868,"title":869,"description":870,"published":871,"category":518,"image":872,"draft":522},"\u002Fblog\u002Fstripe-secret-key-in-frontend","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":395,"title":874,"description":875,"published":876,"category":518,"image":877,"draft":522},"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":879,"title":880,"description":881,"published":882,"category":518,"image":883,"draft":522},"\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":885,"title":886,"description":887,"published":888,"category":518,"image":889,"draft":522},"\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":891,"title":892,"description":893,"published":894,"category":518,"image":895,"draft":522},"\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":897,"title":898,"description":899,"published":900,"category":620,"image":901,"draft":522},"\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":903,"title":904,"description":905,"published":906,"category":620,"image":907,"draft":522},"\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":909,"title":910,"description":911,"published":912,"category":620,"image":913,"draft":522},"\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":915,"title":916,"description":917,"published":918,"category":518,"image":919,"draft":522},"\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":921,"title":922,"description":923,"published":924,"category":518,"image":925,"draft":522},"\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":927,"title":928,"description":929,"published":930,"category":518,"image":931,"draft":522},"\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":933,"title":934,"description":935,"published":936,"category":518,"image":937,"draft":522},"\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":939,"title":940,"description":941,"published":942,"category":518,"image":943,"draft":522},"\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":945,"title":946,"description":947,"published":948,"category":518,"image":949,"draft":522},"\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":951,"title":952,"description":953,"published":954,"category":518,"image":955,"draft":522},"\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":957,"title":958,"description":959,"published":960,"category":518,"image":961,"draft":522},"\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":963,"title":964,"description":965,"published":966,"category":518,"image":967,"draft":522},"\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":969,"title":970,"description":971,"published":972,"category":518,"image":973,"draft":522},"\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":975,"title":976,"description":977,"published":978,"category":620,"image":979,"draft":522},"\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":981,"title":982,"description":983,"published":984,"category":518,"image":985,"draft":522},"\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":987,"title":988,"description":989,"published":990,"category":620,"image":991,"draft":522},"\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":993,"title":994,"description":995,"published":996,"category":518,"image":997,"draft":522},"\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":999,"title":1000,"description":1001,"published":1002,"category":518,"image":1003,"draft":522},"\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":1005,"title":1006,"description":1007,"published":1008,"category":518,"image":1009,"draft":522},"\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":1011,"title":1012,"description":1013,"published":1014,"category":518,"image":1015,"draft":522},"\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":1017,"title":1018,"description":1019,"published":1020,"category":620,"image":1021,"draft":522},"\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":1023,"title":1024,"description":1025,"published":1026,"category":620,"image":1027,"draft":522},"\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":1029,"title":1030,"description":1031,"published":1032,"category":518,"image":1033,"draft":522},"\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":1035,"title":1036,"description":1037,"published":1038,"category":518,"image":1039,"draft":522},"\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":1041,"title":1042,"description":1043,"published":1044,"category":620,"image":1045,"draft":522},"\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":1047,"title":1048,"description":1049,"published":1050,"category":518,"image":1051,"draft":522},"\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":1053,"title":1054,"description":1055,"published":1050,"category":518,"image":1056,"draft":522},"\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":1058,"title":1059,"description":1060,"published":1061,"category":518,"image":1062,"draft":522},"\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":1064,"title":1065,"description":1066,"published":1067,"category":620,"image":1068,"draft":522},"\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":1070,"title":1071,"description":1072,"published":1073,"category":518,"image":1074,"draft":522},"\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":1076,"title":1077,"description":1078,"published":1073,"category":620,"image":1079,"draft":522},"\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":1081,"title":1082,"description":1083,"published":1084,"category":620,"image":1085,"draft":522},"\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":1087,"title":1088,"description":1089,"published":1084,"category":518,"image":1090,"draft":522},"\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]