[{"data":1,"prerenderedAt":1110},["ShallowReactive",2],{"blog-en-supabase-email-rate-limit-exceeded":3,"blog-index-en":580},{"id":4,"title":5,"body":6,"category":535,"cover":536,"coverAlt":537,"description":538,"draft":539,"extension":540,"faq":541,"image":560,"keywords":561,"meta":569,"navigation":570,"ogTitle":5,"path":571,"published":572,"seo":573,"stem":574,"tldr":575,"updated":572,"__hash__":579},"blog_en\u002Fblog\u002Fsupabase-email-rate-limit-exceeded.md","Supabase \"Email Rate Limit Exceeded\": two limits, one error code",{"type":7,"value":8,"toc":522},"minimark",[9,18,28,31,43,48,51,54,73,91,110,116,124,128,131,188,200,207,212,216,219,234,237,241,249,252,258,265,287,291,294,318,321,346,353,357,364,370,373,384,389,393,396,402,412,416,419,428,446,455,475,479,516],[10,11,12,13,17],"p",{},"You are trying your sign-up form before you share the app. You sign up with\nyour own address, then with ",[14,15,16],"code",{},"you+2@gmail.com",", then once more to check the\nconfirmation email looks right. One of those attempts stops on this:",[19,20,25],"pre",{"className":21,"code":23,"language":24},[22],"language-text","AuthApiError: email rate limit exceeded\n","text",[14,26,23],{"__ignoreMap":27},"",[10,29,30],{},"Supabase \"Email Rate Limit Exceeded\" means your project has used up its\nallowance of emails for the hour, so Supabase Auth, the part of Supabase that\nsigns people in, refused to send another. On the email service every project\nstarts with, that allowance is two emails an hour for the whole project.",[10,32,33,34,38,39,42],{},"Here is the part that is easy to get wrong: ",[35,36,37],"strong",{},"the error code covers two\ndifferent limits."," Supabase's own list of Auth error codes describes\n",[14,40,41],{},"over_email_send_rate_limit"," as \"Too many emails have been sent to this email\naddress.\" That is true of one of them. The same code also comes back when the\nwhole project has run out, whoever the email was for, so trying a different\naddress changes nothing. And the usual advice, \"connect your own SMTP\", is half\nthe fix, because Supabase starts a newly connected email server at 30 emails an\nhour.",[44,45,47],"h2",{"id":46},"what-does-email-rate-limit-exceeded-mean-in-supabase","What does \"Email rate limit exceeded\" mean in Supabase?",[10,49,50],{},"It means your project has sent as many emails this hour as Supabase Auth\nallows, and the next one was refused.",[10,52,53],{},"Think of the allowance as a sheet of stamps. Supabase gives each project a\nfixed number of stamps an hour, and every email Supabase Auth sends uses one,\nwhatever kind of email it is and whoever it is for:",[55,56,57,61,64,67,70],"ul",{},[58,59,60],"li",{},"the confirmation link after somebody signs up",[58,62,63],{},"a magic link or a one-time code to sign in",[58,65,66],{},"a password reset",[58,68,69],{},"an invitation you send from the Users page",[58,71,72],{},"the confirmation when somebody changes their email address",[10,74,75,76,78,79,82,83,90],{},"When the sheet is empty, Supabase Auth answers with HTTP 429, which means \"too\nmany requests\", the code ",[14,77,41],{}," and the message ",[14,80,81],{},"email rate limit exceeded",". Those words come from\n",[84,85,89],"a",{"href":86,"rel":87},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fauth\u002Fblob\u002Fmaster\u002Finternal\u002Fapi\u002Fmail.go",[88],"nofollow","the Supabase Auth server's own code",".",[10,92,93,94,97,98,103,104,109],{},"On the built-in sender, the email service a new project starts with, the sheet\nholds ",[35,95,96],{},"two stamps an hour",". That is the figure on Supabase's\n",[84,99,102],{"href":100,"rel":101},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Frate-limits",[88],"rate limits page"," when we\nread it on 20 October 2026, and Supabase's\n",[84,105,108],{"href":106,"rel":107},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fauth-smtp",[88],"guide to custom SMTP"," says it\n\"can change without notice\". At two an hour, one sign-up and one password reset\nare the whole hour's allowance.",[111,112],"diagram",{"alt":113,"caption":114,"src":115},"Four kinds of email, for a new account, a sign-in link, a password reset and an invitation, all draw from one sheet that holds two stamps an hour. Two envelopes leave stamped. The other two are stopped at a barrier with no stamp on them.","Every email Supabase Auth sends uses a stamp from the same sheet. On the built-in sender the sheet holds two an hour.","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fone-sheet-every-email-1600x760.png",[10,117,118,119,123],{},"If nobody can sign in at all, or the whole app is blank, you are looking at\nsomething else, and\n",[84,120,122],{"href":121},"\u002Fblog\u002Fis-supabase-down-or-your-app","is Supabase down, or is it your app"," is\nwhere to start.",[44,125,127],{"id":126},"two-limits-share-one-error-code","Two limits share one error code",[10,129,130],{},"The message tells you which limit you hit. The code is the same for both:",[132,133,134,153],"table",{},[135,136,137],"thead",{},[138,139,140,144,147,150],"tr",{},[141,142,143],"th",{},"The message",[141,145,146],{},"What it limits",[141,148,149],{},"What it counts",[141,151,152],{},"The default",[154,155,156,172],"tbody",{},[138,157,158,163,166,169],{},[159,160,161],"td",{},[14,162,81],{},[159,164,165],{},"The whole project",[159,167,168],{},"Every email Supabase Auth sends, per hour",[159,170,171],{},"2 an hour on the built-in sender, 30 when you first connect your own",[138,173,174,179,182,185],{},[159,175,176],{},[14,177,178],{},"For security purposes, you can only request this after N seconds.",[159,180,181],{},"One address",[159,183,184],{},"The same kind of email, sent again to the same address",[159,186,187],{},"One every 60 seconds",[10,189,190,191,193,194,199],{},"Both answer HTTP 429 with ",[14,192,41],{},". Supabase's\n",[84,195,198],{"href":196,"rel":197},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fdebugging\u002Ferror-codes",[88],"list of Auth error codes","\nasks you to identify errors by their code and \"not string matching on error\nmessages\". That is right for your app's code, and it leaves one gap here: only\nthe message says which limit you hit. So read the message to find out what\nhappened, and let your app react to the code.",[10,201,202,203,206],{},"If your app only says \"something went wrong\", the exact message is in the\nresponse to the failed request, in the Network tab of your browser's developer\ntools. A code of ",[14,204,205],{},"over_request_rate_limit"," is a third limit, on requests from one\nIP address, and Supabase's list says it can point to a bug in your app that\nsends too many of them.",[111,208],{"alt":209,"caption":210,"src":211},"Two panels. In the left one, the project's sheet of stamps is empty and three envelopes for three different people are stopped. In the right one, one person has already been sent an envelope, and a second one to the same person waits beside a clock showing 60 seconds. Both panels lead to the same error code, over_email_send_rate_limit, with status 429.","An empty sheet and a 60-second wait are different refusals, and Supabase reports both with the same code.","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Ftwo-refusals-one-code-1600x720.png",[44,213,215],{"id":214},"why-does-it-say-you-can-only-request-this-after-0-seconds","Why does it say \"you can only request this after 0 seconds\"?",[10,217,218],{},"Because less than a second of the wait was left. The per-address limit allows\none email of each kind to the same address every 60 seconds: one sign-up\nconfirmation, one password reset, one magic link or code. Ask again sooner and\nSupabase Auth works out how long is left and puts that in the message.",[10,220,221,222,229,230,233],{},"It counts in whole seconds and drops the rest. The function in the Auth server\nthat writes this message\n(",[84,223,226],{"href":224,"rel":225},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fauth\u002Fblob\u002Fmaster\u002Finternal\u002Fapi\u002Ferrors.go",[88],[14,227,228],{},"errors.go",")\ndivides the time left by one second, so 0.8 of a second prints as ",[14,231,232],{},"0",". Ask\nagain a moment later and it goes through, as long as the project's hourly cap\nstill has a stamp.",[10,235,236],{},"This wait is working as intended. It is what stops a resend button, pressed\ntwenty times, from sending twenty emails. Leave it at 60 seconds and let your\nform explain it.",[44,238,240],{"id":239},"the-hourly-cap-and-who-it-is-for","The hourly cap, and who it is for",[10,242,243,244,248],{},"The built-in sender is for trying Supabase out, and Supabase says so in its\n",[84,245,247],{"href":106,"rel":246},[88],"SMTP guide",". It lists what the\nservice is intended for: \"Exploring and getting started with Supabase Auth\",\n\"Setting up and testing email templates with the members of the project's\nteam\", and \"Building toy projects, demos or any non-mission-critical\napplication\". It also comes with \"No SLA guarantee on message delivery or\nuptime\".",[10,250,251],{},"The same guide has a second rule, and it decides who sees which error. Until you\nconnect your own email server, Supabase Auth \"will refuse to deliver messages to\naddresses that are not part of the project's team\". A customer signing up with\ntheir own address is turned away before any stamp is counted, with a different\nmessage:",[19,253,256],{"className":254,"code":255,"language":24},[22],"Email address \"customer@example.com\" cannot be used as it is not authorized\n",[14,257,255],{"__ignoreMap":27},[10,259,260,261,264],{},"That is HTTP 400 with the code ",[14,262,263],{},"email_address_not_authorized",", and in the Auth\nserver's code this check runs before either limit. If sign-up works when you try\nit and fails for everybody else, this is why.",[10,266,267,268,270,271,274,275,278,279,282,283,286],{},"So on the built-in sender, ",[14,269,81],{}," mostly meets you and your\nteam, testing. When the Auth server checks whether an address is on your team,\nit ignores anything between a ",[14,272,273],{},"+"," and the ",[14,276,277],{},"@",". That makes ",[14,280,281],{},"you+test1@gmail.com","\nand ",[14,284,285],{},"you+test2@gmail.com"," both count as you, and every test sign-up uses one of\nthe same two stamps.",[44,288,290],{"id":289},"how-do-i-raise-the-supabase-email-rate-limit","How do I raise the Supabase email rate limit?",[10,292,293],{},"Connect your own email provider, then raise the limit Supabase puts on it. They\nare two separate steps, and the second is the one people miss.",[295,296,297,306,312],"ol",{},[58,298,299,302,303,90],{},[35,300,301],{},"Pick a sending service and get its SMTP settings."," Supabase's guide names\nResend, AWS SES, Postmark, Twilio SendGrid, ZeptoMail and Brevo, and says any\nservice that supports SMTP will work. You need the host, the port, a user\nname and a password, plus a From address such as ",[14,304,305],{},"no-reply@yourdomain.com",[58,307,308,311],{},[35,309,310],{},"Turn on custom SMTP"," in your project's Authentication settings and enter\nthose details. From then on Supabase sends to every address.",[58,313,314,317],{},[35,315,316],{},"Raise the email limit"," on the Rate Limits page, also under Authentication.\nThe guide says a newly connected server gets \"a low rate-limit of 30 messages\nper hour\" to protect its reputation, and that you change it there. Set it to\nwhat your provider allows and what your busiest hour needs.",[10,319,320],{},"Three more things from the same guide belong with this change:",[55,322,323,329,335],{},[58,324,325,328],{},[35,326,327],{},"Set up DKIM, DMARC and SPF"," for your sending domain with your provider.\nSupabase says this \"will significantly increase the deliverability of your\nmessages\".",[58,330,331,334],{},[35,332,333],{},"Turn on CAPTCHA for sign-ups."," The guide names bots signing up lists of\naddresses as \"a common source of abuse\", and every one of those sign-ups is an\nemail drawn from your hour. It calls CAPTCHA \"the most effective way\" to stop\nthem.",[58,336,337,340,341,345],{},[35,338,339],{},"Check that people are not being signed out."," The guide says short sessions\nforce \"active users to sign in frequently, increasing the number of messages\",\nand if your users sign in by email link, each unexpected logout costs a stamp.\n",[84,342,344],{"href":343},"\u002Fblog\u002Fsupabase-users-logged-out","Why Supabase users get logged out"," covers the\ncauses.",[10,347,348,349,90],{},"For the other limits a free project runs into, see\n",[84,350,352],{"href":351},"\u002Fblog\u002Fsupabase-free-plan-limits","what the Supabase free plan includes",[44,354,356],{"id":355},"handling-the-error-in-your-sign-up-form","Handling the error in your sign-up form",[10,358,359,360,363],{},"Catch it by its code and tell the person what to do in plain words. Supabase's\nJavaScript client puts the server's code on the error it returns, as\n",[14,361,362],{},"error.code",", so the check is one line:",[19,365,368],{"className":366,"code":367,"language":24},[22],"const { error } = await supabase.auth.signUp({ email, password })\n\nif (error?.code === 'over_email_send_rate_limit') {\n  \u002F\u002F show: \"We couldn't send your email just now. Please try again in a minute.\"\n}\n",[14,369,367],{"__ignoreMap":27},[10,371,372],{},"Ask your builder, whether that is Lovable, Bolt, v0, Cursor, Claude Code or\nReplit, for three things:",[55,374,375,378,381],{},[58,376,377],{},"the same check on every form that sends email: sign-up, \"forgot password\",\nsign-in by email link, and \"resend\"",[58,379,380],{},"a message that asks the person to try again shortly, in place of the raw\nerror or a form that silently does nothing",[58,382,383],{},"the resend button disabled for 60 seconds after each send, so nobody can\npress it into the per-address wait",[10,385,386,387,90],{},"Leave out automatic retries. While the sheet is empty each retry is refused, and\nsign-up requests are also limited per IP address, to 30 every 5 minutes by\ndefault. A retry loop can trip that limit too, and it answers with\n",[14,388,205],{},[44,390,392],{"id":391},"what-not-to-change-while-sign-ups-are-stuck","What not to change while sign-ups are stuck",[10,394,395],{},"Email confirmation, and where the emails are sent from. Two shortcuts make the\nerror disappear and leave you worse off.",[10,397,398,401],{},[35,399,400],{},"Leave email confirmation on."," Switching off \"Confirm email\" stops sign-ups\nsending anything, so the error goes away. Supabase's SMTP guide lists \"Do not\ndisable email confirmations under pressure\" among its defences, because without\nconfirmation somebody can create an account in another person's name.",[10,403,404,407,408,90],{},[35,405,406],{},"Keep the emails out of the browser."," Ask an assistant to \"just send the\nconfirmation with Resend\" and it can put the provider's API key into your app's\nfrontend code, where every visitor can read it and send mail as you. Send email\nthrough Supabase's SMTP settings or a server-side function, never with a key in\nthe page. If you are not sure one slipped in, our free scan reads the code your\nlive app sends to every visitor and flags the secret keys it finds there. It\ntakes about 20 seconds and needs no account: ",[84,409,411],{"href":410},"\u002Fsecurity-scanner","scan your app",[44,413,415],{"id":414},"keeping-watch-while-you-change-how-your-app-sends-email","Keeping watch while you change how your app sends email",[10,417,418],{},"Two things can go wrong while you rewire email: a key ends up in your app's\ncode, and a message saying \"nobody can sign up\" sends you hunting for an outage.",[10,420,421],{},[35,422,423,427],{},[84,424,426],{"href":425},"\u002Fwebsite-monitoring","Reeve Monitor"," keeps checking from outside:",[55,429,430,433,436,443],{},[58,431,432],{},"whether your app is up, checked every minute, so you know at once if a sign-up complaint is an outage or something narrower",[58,434,435],{},"the full security check every hour, on up to three apps, including secret keys in the code your app sends to visitors",[58,437,438,439,442],{},"a message when a result ",[35,440,441],{},"changes",", so a key that ships in a later deploy reaches you without you going to look",[58,444,445],{},"a monthly report, in plain language, of what it saw",[10,447,448],{},[35,449,450,454],{},[84,451,453],{"href":452},"\u002Fsupabase-backups","Reeve Care"," keeps a copy of your Supabase database:",[55,456,457,460,463,466,469,472],{},[58,458,459],{},"an encrypted copy on a schedule, on Reeve's own storage in the EU, outside your Supabase account",[58,461,462],{},"the auth schema, where every account that did sign up lives",[58,464,465],{},"each copy verified before it counts, by counting the rows in every table",[58,467,468],{},"your uploaded files as well, once you connect a Storage credential",[58,470,471],{},"a one-click restore, with a safety copy of the current state taken first",[58,473,474],{},"everything Monitor does",[44,476,478],{"id":477},"what-to-do-now","What to do now",[480,481,482],"key-takeaways",{},[55,483,484,494,501,504,507,513],{},[58,485,486,487,489,490,493],{},"Read the message as well as the code: ",[14,488,81],{}," is the project's hourly cap, and ",[14,491,492],{},"For security purposes…"," is the 60-second wait for one address.",[58,495,496,497,500],{},"If customers see ",[14,498,499],{},"Email address … cannot be used as it is not authorized",", your project is still on Supabase's built-in sender, which only mails your team.",[58,502,503],{},"Connect your own SMTP provider, then raise the email limit on the Rate Limits page, which starts at 30 an hour.",[58,505,506],{},"Set up DKIM, DMARC and SPF with your provider, and turn on CAPTCHA for sign-ups.",[58,508,509,510,512],{},"Make every form that sends email check for ",[14,511,41],{},", show a plain message, and hold the resend button for 60 seconds.",[58,514,515],{},"Keep email confirmation on, and never put an email provider's key in your frontend.",[10,517,518,519,521],{},"Start with the message in the failed response, because it tells you which of\nthe two limits you hit. Then, once email goes out through your own provider,\n",[84,520,411],{"href":410}," to check that no key came along with it.",{"title":27,"searchDepth":523,"depth":523,"links":524},3,[525,527,528,529,530,531,532,533,534],{"id":46,"depth":526,"text":47},2,{"id":126,"depth":526,"text":127},{"id":214,"depth":526,"text":215},{"id":239,"depth":526,"text":240},{"id":289,"depth":526,"text":290},{"id":355,"depth":526,"text":356},{"id":391,"depth":526,"text":392},{"id":414,"depth":526,"text":415},{"id":477,"depth":526,"text":478},"Security basics","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fcover-1200x630.png","A sheet of stamps with every stamp already torn out, beside a stack of sealed envelopes that have nothing on their corners.","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.",false,"md",[542,545,548,551,554,557],{"q":543,"a":544},"What does \"email rate limit exceeded\" mean in Supabase?","It means your project has sent as many emails this hour as Supabase Auth allows, so the next one was refused. The count covers every email Auth sends, to anyone: sign-up confirmations, magic links, password resets and invitations. On the built-in sender the allowance is 2 an hour. With your own SMTP provider you set it yourself.",{"q":546,"a":547},"Why does it say I can only request this after 0 seconds?","Because less than a second of the 60-second wait was left. Supabase Auth counts the time remaining in whole seconds and drops the rest, so the last second reads as 0. Ask again a moment later and the email goes out, as long as the hourly cap still has room.",{"q":549,"a":550},"How many emails can Supabase send for me?","On the built-in sender, 2 an hour for the whole project, and only to people on your Supabase team. Supabase says that figure can change without notice. With your own SMTP provider there is no fixed number: Supabase starts it at 30 an hour and you raise it on the Rate Limits page.",{"q":552,"a":553},"Do I need my own SMTP provider?","Yes, as soon as anybody outside your team signs up by email. The built-in sender refuses addresses that are not on your team, and Supabase describes it as being for trying things out, testing templates and demos. Resend, AWS SES, Postmark, SendGrid, ZeptoMail and Brevo are among the services Supabase lists as working with it.",{"q":555,"a":556},"How do I stop this crashing my sign-up form?","Check the code on the error before anything reaches the screen. When it is over_email_send_rate_limit, show a plain message asking the person to try again in a minute, and keep the resend button disabled for 60 seconds after each send so nobody can press it into the wait.",{"q":558,"a":559},"Why do my customers get \"Email address not authorized\"?","Because your project still sends through Supabase's built-in sender, which only delivers to members of your Supabase organization. Everybody else is refused with the code email_address_not_authorized. Connecting your own SMTP provider fixes it, and it is the same change that lifts the hourly cap.","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fcard-800x500.png",[562,563,41,564,565,566,567,568],"email rate limit exceeded supabase","supabase email rate limit exceeded","for security purposes you can only request this after","supabase smtp rate limit","supabase magic link not sending","supabase signup email limit","email address not authorized supabase",{},true,"\u002Fblog\u002Fsupabase-email-rate-limit-exceeded","2026-10-20",{"title":5,"description":538},"blog\u002Fsupabase-email-rate-limit-exceeded",[576,577,578],"Supabase \"Email Rate Limit Exceeded\" means your project has sent as many emails this hour as it is allowed. On the built-in sender that is 2 an hour, and every sign-up confirmation, magic link and password reset counts.","The same code, over_email_send_rate_limit, also comes back as \"For security purposes, you can only request this after N seconds\", a 60-second wait for one address. Only the message tells the two apart.","Your own SMTP provider lifts the hourly cap once you also raise the limit on the Rate Limits page, which starts it at 30 an hour. The 60-second wait stays, and your form should explain it.","rk4BUzxcPtxq-zM2Koa7lYMQJi3mPf1fSkDY9-2OYsY",[581,587,593,599,605,611,617,623,629,635,641,648,654,660,666,672,678,684,690,696,702,703,708,714,720,726,732,738,744,750,756,762,768,774,780,786,792,798,804,810,815,821,826,832,838,844,849,855,861,867,873,879,885,891,897,903,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,1076,1082,1088,1094,1099,1105],{"path":582,"title":583,"description":584,"published":585,"category":535,"image":586,"draft":539},"\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":588,"title":589,"description":590,"published":591,"category":535,"image":592,"draft":539},"\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":594,"title":595,"description":596,"published":597,"category":535,"image":598,"draft":539},"\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":600,"title":601,"description":602,"published":603,"category":535,"image":604,"draft":539},"\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":606,"title":607,"description":608,"published":609,"category":535,"image":610,"draft":539},"\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":612,"title":613,"description":614,"published":615,"category":535,"image":616,"draft":539},"\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":618,"title":619,"description":620,"published":621,"category":535,"image":622,"draft":539},"\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":624,"title":625,"description":626,"published":627,"category":535,"image":628,"draft":539},"\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":630,"title":631,"description":632,"published":633,"category":535,"image":634,"draft":539},"\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":636,"title":637,"description":638,"published":639,"category":535,"image":640,"draft":539},"\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":642,"title":643,"description":644,"published":645,"category":646,"image":647,"draft":539},"\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":649,"title":650,"description":651,"published":652,"category":535,"image":653,"draft":539},"\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":655,"title":656,"description":657,"published":658,"category":535,"image":659,"draft":539},"\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":661,"title":662,"description":663,"published":664,"category":535,"image":665,"draft":539},"\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":667,"title":668,"description":669,"published":670,"category":535,"image":671,"draft":539},"\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":673,"title":674,"description":675,"published":676,"category":535,"image":677,"draft":539},"\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":679,"title":680,"description":681,"published":682,"category":535,"image":683,"draft":539},"\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":685,"title":686,"description":687,"published":688,"category":535,"image":689,"draft":539},"\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":691,"title":692,"description":693,"published":694,"category":535,"image":695,"draft":539},"\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":697,"title":698,"description":699,"published":700,"category":535,"image":701,"draft":539},"\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":571,"title":5,"description":538,"published":572,"category":535,"image":560,"draft":539},{"path":343,"title":704,"description":705,"published":706,"category":535,"image":707,"draft":539},"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":709,"title":710,"description":711,"published":712,"category":535,"image":713,"draft":539},"\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":715,"title":716,"description":717,"published":718,"category":535,"image":719,"draft":539},"\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":721,"title":722,"description":723,"published":724,"category":535,"image":725,"draft":539},"\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":727,"title":728,"description":729,"published":730,"category":535,"image":731,"draft":539},"\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":733,"title":734,"description":735,"published":736,"category":535,"image":737,"draft":539},"\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":739,"title":740,"description":741,"published":742,"category":535,"image":743,"draft":539},"\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":745,"title":746,"description":747,"published":748,"category":535,"image":749,"draft":539},"\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":751,"title":752,"description":753,"published":754,"category":535,"image":755,"draft":539},"\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":757,"title":758,"description":759,"published":760,"category":535,"image":761,"draft":539},"\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":763,"title":764,"description":765,"published":766,"category":535,"image":767,"draft":539},"\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":769,"title":770,"description":771,"published":772,"category":535,"image":773,"draft":539},"\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":775,"title":776,"description":777,"published":778,"category":535,"image":779,"draft":539},"\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":781,"title":782,"description":783,"published":784,"category":535,"image":785,"draft":539},"\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":787,"title":788,"description":789,"published":790,"category":535,"image":791,"draft":539},"\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":793,"title":794,"description":795,"published":796,"category":535,"image":797,"draft":539},"\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":799,"title":800,"description":801,"published":802,"category":535,"image":803,"draft":539},"\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":805,"title":806,"description":807,"published":808,"category":535,"image":809,"draft":539},"\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":121,"title":811,"description":812,"published":813,"category":535,"image":814,"draft":539},"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":816,"title":817,"description":818,"published":819,"category":535,"image":820,"draft":539},"\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":351,"title":822,"description":823,"published":824,"category":535,"image":825,"draft":539},"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":827,"title":828,"description":829,"published":830,"category":646,"image":831,"draft":539},"\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":833,"title":834,"description":835,"published":836,"category":646,"image":837,"draft":539},"\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":839,"title":840,"description":841,"published":842,"category":646,"image":843,"draft":539},"\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":845,"title":846,"description":847,"published":842,"category":535,"image":848,"draft":539},"\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":850,"title":851,"description":852,"published":853,"category":535,"image":854,"draft":539},"\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":856,"title":857,"description":858,"published":859,"category":535,"image":860,"draft":539},"\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":862,"title":863,"description":864,"published":865,"category":646,"image":866,"draft":539},"\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":868,"title":869,"description":870,"published":871,"category":535,"image":872,"draft":539},"\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":874,"title":875,"description":876,"published":877,"category":535,"image":878,"draft":539},"\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":880,"title":881,"description":882,"published":883,"category":535,"image":884,"draft":539},"\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":886,"title":887,"description":888,"published":889,"category":535,"image":890,"draft":539},"\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":892,"title":893,"description":894,"published":895,"category":535,"image":896,"draft":539},"\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":898,"title":899,"description":900,"published":901,"category":535,"image":902,"draft":539},"\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":904,"title":905,"description":906,"published":907,"category":535,"image":908,"draft":539},"\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":910,"title":911,"description":912,"published":913,"category":535,"image":914,"draft":539},"\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":916,"title":917,"description":918,"published":919,"category":646,"image":920,"draft":539},"\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":922,"title":923,"description":924,"published":925,"category":646,"image":926,"draft":539},"\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":928,"title":929,"description":930,"published":931,"category":646,"image":932,"draft":539},"\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":934,"title":935,"description":936,"published":937,"category":535,"image":938,"draft":539},"\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":940,"title":941,"description":942,"published":943,"category":535,"image":944,"draft":539},"\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":946,"title":947,"description":948,"published":949,"category":535,"image":950,"draft":539},"\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":952,"title":953,"description":954,"published":955,"category":535,"image":956,"draft":539},"\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":958,"title":959,"description":960,"published":961,"category":535,"image":962,"draft":539},"\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":964,"title":965,"description":966,"published":967,"category":535,"image":968,"draft":539},"\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":970,"title":971,"description":972,"published":973,"category":535,"image":974,"draft":539},"\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":976,"title":977,"description":978,"published":979,"category":535,"image":980,"draft":539},"\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":982,"title":983,"description":984,"published":985,"category":535,"image":986,"draft":539},"\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":988,"title":989,"description":990,"published":991,"category":535,"image":992,"draft":539},"\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":994,"title":995,"description":996,"published":997,"category":646,"image":998,"draft":539},"\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":1000,"title":1001,"description":1002,"published":1003,"category":535,"image":1004,"draft":539},"\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":1006,"title":1007,"description":1008,"published":1009,"category":646,"image":1010,"draft":539},"\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":1012,"title":1013,"description":1014,"published":1015,"category":535,"image":1016,"draft":539},"\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":1018,"title":1019,"description":1020,"published":1021,"category":535,"image":1022,"draft":539},"\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":1024,"title":1025,"description":1026,"published":1027,"category":535,"image":1028,"draft":539},"\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":1030,"title":1031,"description":1032,"published":1033,"category":535,"image":1034,"draft":539},"\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":1036,"title":1037,"description":1038,"published":1039,"category":646,"image":1040,"draft":539},"\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":1042,"title":1043,"description":1044,"published":1045,"category":646,"image":1046,"draft":539},"\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":1048,"title":1049,"description":1050,"published":1051,"category":535,"image":1052,"draft":539},"\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":1054,"title":1055,"description":1056,"published":1057,"category":535,"image":1058,"draft":539},"\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":1060,"title":1061,"description":1062,"published":1063,"category":646,"image":1064,"draft":539},"\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":1066,"title":1067,"description":1068,"published":1069,"category":535,"image":1070,"draft":539},"\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":1072,"title":1073,"description":1074,"published":1069,"category":535,"image":1075,"draft":539},"\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":1077,"title":1078,"description":1079,"published":1080,"category":535,"image":1081,"draft":539},"\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":1083,"title":1084,"description":1085,"published":1086,"category":646,"image":1087,"draft":539},"\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":1089,"title":1090,"description":1091,"published":1092,"category":535,"image":1093,"draft":539},"\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":1095,"title":1096,"description":1097,"published":1092,"category":646,"image":1098,"draft":539},"\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":1100,"title":1101,"description":1102,"published":1103,"category":646,"image":1104,"draft":539},"\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":1106,"title":1107,"description":1108,"published":1103,"category":535,"image":1109,"draft":539},"\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]