[{"data":1,"prerenderedAt":1201},["ShallowReactive",2],{"blog-en-lovable-cloud-backup":3,"blog-index-en":593},{"id":4,"title":5,"body":6,"category":85,"cover":550,"coverAlt":551,"description":552,"draft":553,"extension":554,"faq":555,"image":571,"keywords":572,"meta":580,"navigation":581,"ogTitle":582,"path":583,"published":584,"seo":585,"stem":586,"tldr":587,"updated":584,"__hash__":592},"blog_en\u002Fblog\u002Flovable-cloud-backup.md","Lovable Cloud backup: does Lovable back up your database?",{"type":7,"value":8,"toc":536},"minimark",[9,13,16,24,29,32,35,54,68,72,87,90,94,97,187,190,194,197,203,206,209,225,229,232,235,255,260,263,266,270,278,293,312,320,324,327,367,370,373,387,398,404,407,411,414,422,436,445,459,467,481,485,524],[10,11,12],"p",{},"You built your app in Lovable, people sign up and use it, and somebody has just\nasked you a question you could not answer: if the data went, could you get it\nback? You remember Lovable saying something about backups. You have never looked\nat one.",[10,14,15],{},"The short answer is yes. If your app runs on Lovable Cloud, Lovable's built-in\nbackend, a Lovable Cloud backup of your database is taken every day, and Lovable\nkeeps up to roughly 14 days of them. You can see the list and restore from it\nyourself.",[10,17,18,19,23],{},"What changes what you should do is where those copies are kept. ",[20,21,22],"strong",{},"They live\ninside the same backend as the database they protect."," Picture Lovable Cloud as\none filing cabinet. Your database is the top drawer. Once a day Lovable\nphotocopies that drawer and files the copy further down the same cabinet. That\ncovers a bad edit. It does nothing on the day the cabinet itself goes, and the\nphotocopier never opens the drawer where your users' uploaded files are kept.",[25,26,28],"h2",{"id":27},"does-lovable-back-up-your-database","Does Lovable back up your database?",[10,30,31],{},"Yes, if your project uses Lovable Cloud. Lovable's documentation says it \"backs\nup your project's database every day\", takes one backup a day and \"keeps up to\nroughly 14 days of them\".",[10,33,34],{},"Lovable projects come in two kinds, and that answer belongs to one of them. The\nbuilt-in backend is on by default, Lovable calls it Cloud in parts of the\nproduct, and in Lovable's words it \"utilizes Supabase's open-source foundation\".\nThe other kind is connected to a Supabase project the owner holds on their own\nSupabase account.",[10,36,37,38,41,42,45,46,49,50,53],{},"You can tell which you have from the editor. On Lovable Cloud, your data is in\nthe ",[20,39,40],{},"Database",", ",[20,43,44],{},"Users"," and ",[20,47,48],{},"Storage"," views inside Lovable. On your own\nSupabase project, ",[20,51,52],{},"More → Supabase"," shows that project's name, with links into\nthe Supabase dashboard.",[10,55,56,57,62,63,67],{},"For the second kind, Lovable's own comparison table lists backups under \"Managed\nby you in Supabase\". What you have then depends on your Supabase plan, and the\n",[58,59,61],"a",{"href":60},"\u002Fsupabase-backups","Supabase backups page"," sets the plans side by side. Your\nuploaded files need ",[58,64,66],{"href":65},"\u002Fblog\u002Fsupabase-storage-backup","a backup of their own"," there\nas well. The rest of this article is about Lovable Cloud.",[25,69,71],{"id":70},"where-to-find-your-lovable-cloud-backups","Where to find your Lovable Cloud backups",[10,73,74,75,78,79,82,83,86],{},"In the editor, go to ",[20,76,77],{},"More → Database",", select ",[20,80,81],{},"Manage",", then ",[20,84,85],{},"Backups",".\nEach row is one daily copy, with the time it was taken shown in UTC.",[10,88,89],{},"That list is all there is. You can restore to any row on it and to nothing in\nbetween, so the nearest you can get to a mistake is the last copy taken before\nit happened. Lovable's FAQ answers \"Can I restore my database to any point in\ntime?\" with a plain no. If you deleted something at four in the afternoon and\nthe last copy is from the early morning, the hours between are not in any of\nthem.",[25,91,93],{"id":92},"what-a-lovable-cloud-backup-holds","What a Lovable Cloud backup holds",[10,95,96],{},"Your database, its structure and its data. Lovable states it in one line:\n\"Backups and exports cover the database only, both structure and data.\" Files\nin storage are a separate thing.",[98,99,100,119],"table",{},[101,102,103],"thead",{},[104,105,106,110,113,116],"tr",{},[107,108,109],"th",{},"Part of your app",[107,111,112],{},"Daily backup",[107,114,115],{},"Export",[107,117,118],{},"Where it is otherwise",[120,121,122,135,147,163,175],"tbody",{},[104,123,124,128,131,133],{},[125,126,127],"td",{},"Your tables, structure and data",[125,129,130],{},"Yes",[125,132,130],{},[125,134],{},[104,136,137,140,143,145],{},[125,138,139],{},"Your users' accounts and password hashes",[125,141,142],{},"Lovable does not say",[125,144,130],{},[125,146],{},[104,148,149,152,155,157],{},[125,150,151],{},"Files your users uploaded",[125,153,154],{},"No",[125,156,154],{},[125,158,159,160],{},"Download them from ",[20,161,162],{},"More → Storage",[104,164,165,168,170,172],{},[125,166,167],{},"Edge function code",[125,169,154],{},[125,171,154],{},[125,173,174],{},"Your version history, which redeploys it on revert",[104,176,177,180,182,184],{},[125,178,179],{},"Secrets, API keys, sign-in provider settings",[125,181,154],{},[125,183,154],{},[125,185,186],{},"Set up again by hand if you move",[10,188,189],{},"The files row matters most. A restore \"does not change the files in storage\",\nin Lovable's words, so it cannot bring back a photo that was deleted. If a\ncustomer's profile row and their photo were both removed after the copy was\ntaken, the restore puts the row back and the photo stays gone.",[25,191,193],{"id":192},"where-lovable-keeps-the-copies","Where Lovable keeps the copies",[10,195,196],{},"In the same backend as the database, which makes them the bottom drawer of the\nsame cabinet. Lovable's warning on removing a database says so directly:\n\"Removing the database deletes the database, its backups, your app's user\naccounts, and the files in storage, and cannot be undone.\" Exports saved in your\nproject's storage are deleted too.",[198,199],"diagram",{"alt":200,"caption":201,"src":202},"Left, a cabinet holding a database, a row of daily copies and a stack of uploaded files. Right, the same cabinet after the database is removed, drawn as a dashed red outline with everything in it crossed out, while one copy on a laptop outside it is ticked.","Removing the database takes the daily copies and the uploaded files with it. The copy on your own laptop is the one still there afterwards.","\u002Fblog\u002Flovable-cloud-backup\u002Fremoving-the-database-1600x700.png",[10,204,205],{},"Anyone with permission to manage the project's settings can remove the\ndatabase, after ticking two warnings and typing the project's exact name.",[10,207,208],{},"Two other events sound similar and are gentler:",[210,211,212,219],"ul",{},[213,214,215,218],"li",{},[20,216,217],{},"A pause keeps the data."," Lovable pauses the backend of a project after\nabout 7 days without activity. While it is paused, your published app cannot\nread or write data, sign anyone in or serve files, and you cannot export until\nyou wake it up. Opening the project in the editor wakes one paused for\ninactivity, and that takes a few minutes.",[213,220,221,224],{},[20,222,223],{},"Deleting the project is reversible for 60 days."," Lovable pauses the backend\nand the data in it stays. After 60 days Lovable deletes the project\npermanently, and nobody can bring it back, including Lovable support.",[25,226,228],{"id":227},"what-restoring-a-lovable-cloud-backup-does","What restoring a Lovable Cloud backup does",[10,230,231],{},"The whole database goes back to the day you pick, structure and data together,\nin one step that cannot be undone. Lovable says it plainly: \"Any data created or\nchanged after the chosen backup is lost.\" The database is unavailable for a few\nminutes while the restore runs.",[10,233,234],{},"In the cabinet, a restore swaps the entire top drawer for one of the\nphotocopies. You cannot pull out the one page you lost and keep today's drawer\naround it. Three details follow from that:",[210,236,237,243,249],{},[213,238,239,242],{},[20,240,241],{},"Everything since that copy goes."," A customer who signed up yesterday and an\norder placed this morning are both missing from a copy taken two days ago.",[213,244,245,248],{},[20,246,247],{},"The code may no longer match."," The structure goes back too, so a column\nLovable added since then disappears while the code that reads it stays.\nLovable's advice is to ask it in the project chat to test the app and fix any\nmismatch afterwards.",[213,250,251,254],{},[20,252,253],{},"It always replaces the same project's database."," There is no restoring a\ncopy to the side to fetch a single table out of it.",[198,256],{"alt":257,"caption":258,"src":259},"A row of seven daily copies with rows of data stacking up above each day. A restore arrow runs back from today's copy to the one three days earlier, and the rows added in the three days since are drawn as dashed red outlines. A separate stack of uploaded files sits to the side, untouched.","A restore puts the whole database back to one daily copy. Whatever was written after it is gone, and the uploaded files are not part of it at all.","\u002Fblog\u002Flovable-cloud-backup\u002Fa-restore-takes-the-whole-drawer-1600x640.png",[10,261,262],{},"So export first. Lovable gives the same advice: \"To keep the current state,\nexport your database first.\" Then whatever the restore removes still exists in\na file you hold.",[10,264,265],{},"Anyone with edit access to the project can restore a backup. On Enterprise\nplans every restore is recorded in the workspace audit log.",[25,267,269],{"id":268},"version-history-does-not-touch-your-data","Version history does not touch your data",[10,271,272,273,277],{},"Lovable's version history rolls back code and nothing else. Its documentation\nsays reverting \"restores your project's code only\" and \"does not restore or roll\nback your database data\". The\nFAQ entry \"What happens to my database when I revert?\" is answered with one\nword, \"Nothing.\" The longer account of why the two are separate is in\n",[58,274,276],{"href":275},"\u002Fblog\u002Fversion-history-is-not-a-backup","version history is not a backup",".",[10,279,280,281,284,285,288,289,292],{},"That matters because Lovable edits your data as well as your code. In its\nbackend permissions, the setting called ",[20,282,283],{},"Change data",", which lets Lovable \"add,\nupdate, or delete data in your database tables\", is set to ",[20,286,287],{},"Always allow"," out\nof the box. So is ",[20,290,291],{},"Modify database",", which covers \"schema and policy changes\nvia SQL migrations\". Ask Lovable to clear out some test bookings and it can\ndelete rows without asking first, and a revert will not bring a single one back.",[10,294,295,296,299,300,302,303,306,307,311],{},"You can change that under ",[20,297,298],{},"Account settings → Preferences → Agent\npermissions",". Set ",[20,301,283],{}," to ",[20,304,305],{},"Ask each time"," and Lovable asks for your\napproval whenever it is about to touch rows. If an agent has already deleted\nsomething, ",[58,308,310],{"href":309},"\u002Fblog\u002Fai-agent-deleted-my-database","what you can still recover","\ndepends on how long ago it happened.",[10,313,314,315,319],{},"A policy change is easy to miss in a long chat, and a loosened one can leave a\ntable readable by anybody who opens your site. If you want to know how your\nlive app looks from outside, ",[58,316,318],{"href":317},"\u002Fsecurity-scanner","the free scan"," reads it the way\na stranger's browser would and tells you what it found open.",[25,321,323],{"id":322},"how-to-keep-a-copy-of-your-own","How to keep a copy of your own",[10,325,326],{},"Export the database, then keep the file outside Lovable. The export is the one\ncopy that does not live in the cabinet, and Lovable describes what it holds in\nfull: \"your full database, both structure and data\", plus \"your users' accounts\nand their password hashes, the scrambled form in which passwords are stored\".",[328,329,330,341,351,362],"ol",{},[213,331,332,333,78,335,337,338,277],{},"In your project, go to ",[20,334,77],{},[20,336,81],{},", then\n",[20,339,340],{},"Settings",[213,342,343,344,347,348,277],{},"In ",[20,345,346],{},"Export project data",", click ",[20,349,350],{},"Export data",[213,352,353,354,356,357,82,359,277],{},"In the ",[20,355,40],{}," card, click ",[20,358,115],{},[20,360,361],{},"Start export",[213,363,364,365,277],{},"Lovable emails you when it is ready and saves it to your project's storage.\nDownload it from ",[20,366,162],{},[10,368,369],{},"Then move it off Lovable, to your own computer or a drive you control. Left in\nstorage it sits inside the cabinet with everything else, and removing the\ndatabase deletes it.",[10,371,372],{},"The limits, all from Lovable's page:",[210,374,375,378,381,384],{},[213,376,377],{},"Databases using up to 15 GB of storage, and an export file of at most 5 GB.\nLarger ones go through Lovable's support.",[213,379,380],{},"One export every 24 hours.",[213,382,383],{},"Only while the database is running. A paused project, including one paused\nbecause your workspace ran out of credits, has to be woken first.",[213,385,386],{},"Anyone who can manage the project's settings can export.",[10,388,389,390,394,395,397],{},"The file is a compressed PostgreSQL archive, which a developer, or the import\ntool of whatever backend you move to, loads with ",[391,392,393],"code",{},"pg_restore",". For a copy you\ncan open yourself, Lovable points you to CSV instead: download a single table\nfrom the ",[20,396,40],{}," view.",[10,399,400,401,403],{},"Download your files from ",[20,402,162],{}," at the same time, because the export\nleaves them out. And take a fresh export before any restore, so the rows written\nsince the last copy stay in a file you hold.",[10,405,406],{},"If you ever move the app to your own Supabase project, this export is how the\ndata travels. Lovable says your users keep their passwords when the export is\nrestored into Supabase, and people signed in at the time of the switch have to\nsign in again.",[25,408,410],{"id":409},"keeping-an-eye-on-the-app-between-exports","Keeping an eye on the app between exports",[10,412,413],{},"Reeve watches the live app from outside on the days between your exports. When\nthe app runs on your own Supabase project, it keeps the copies for you too.",[10,415,416],{},[20,417,418,421],{},[58,419,420],{"href":317},"The free scan"," reads your Lovable app as a stranger would.",[210,423,424,427,430],{},[213,425,426],{},"It looks at your live site from outside, with nothing to install.",[213,428,429],{},"It reports the keys in your code, the tables a visitor can read and the files\nanyone can list.",[213,431,432,433,277],{},"No account needed. ",[58,434,435],{"href":317},"Scan your app free in 20 seconds",[10,437,438],{},[20,439,440,444],{},[58,441,443],{"href":442},"\u002Fwebsite-monitoring","Monitor"," keeps looking after you stop.",[210,446,447,450,453],{},[213,448,449],{},"It checks your site every 60 seconds and tells you by email, Telegram or Slack\nwhen it stops answering.",[213,451,452],{},"It reads the pages you name for the words that must be there and for error\nmessages that must not.",[213,454,455,456,277],{},"It runs the security checks again every hour, so a rule an edit loosened shows\nup the same day. ",[58,457,458],{"href":442},"See how Monitor works",[10,460,461],{},[20,462,463,466],{},[58,464,465],{"href":60},"Care"," keeps the copies, for a Lovable app on your own\nSupabase project.",[210,468,469,472,475],{},[213,470,471],{},"It copies your Supabase database on a schedule, encrypted, on Reeve's own\nstorage in the EU, outside your Supabase account.",[213,473,474],{},"Each copy is verified before it counts.",[213,476,477,478,277],{},"Connect a Storage credential and your uploaded files come too.\n",[58,479,480],{"href":60},"See what a Care backup holds",[25,482,484],{"id":483},"what-to-do-this-week","What to do this week",[486,487,488],"key-takeaways",{},[210,489,490,503,510,513,516],{},[213,491,492,493,41,495,45,497,499,500,502],{},"Find out which backend your project uses. ",[20,494,40],{},[20,496,44],{},[20,498,48],{}," views inside Lovable mean Lovable Cloud; ",[20,501,52],{}," showing a project name means your own Supabase.",[213,504,505,506,509],{},"On Lovable Cloud, open ",[20,507,508],{},"More → Database → Manage → Backups"," once, so you know where the list is before you need it.",[213,511,512],{},"Export the database and download your storage files, then keep both on a computer or drive outside Lovable.",[213,514,515],{},"Take a fresh export before any restore, so the restore cannot cost you the rows written since the last copy.",[213,517,518,519,302,521,523],{},"Set ",[20,520,283],{},[20,522,305],{}," if you want Lovable to ask before it edits rows.",[10,525,526,527,530,531,535],{},"The first export is today's job, and it starts under ",[20,528,529],{},"More → Database →\nManage → Settings",". While it runs, the\n",[58,532,534],{"href":533},"\u002Fchecklist","10-minute security checklist"," covers the other things worth\nconfirming on a Lovable app that real people use.",{"title":537,"searchDepth":538,"depth":538,"links":539},"",3,[540,542,543,544,545,546,547,548,549],{"id":27,"depth":541,"text":28},2,{"id":70,"depth":541,"text":71},{"id":92,"depth":541,"text":93},{"id":192,"depth":541,"text":193},{"id":227,"depth":541,"text":228},{"id":268,"depth":541,"text":269},{"id":322,"depth":541,"text":323},{"id":409,"depth":541,"text":410},{"id":483,"depth":541,"text":484},"\u002Fblog\u002Flovable-cloud-backup\u002Fcover-1200x630.png","A filing cabinet holding a database in its top drawer and a row of daily copies below it, with one copy carried out to a laptop.","A Lovable Cloud backup is taken daily and kept about 14 days, in the same backend as your data. What it holds, who can restore it, how to keep a copy.",false,"md",[556,559,562,565,568],{"q":557,"a":558},"Does Lovable back up my database automatically?","If your project uses Lovable Cloud, the built-in backend, yes. Lovable takes one backup a day, keeps up to roughly 14 days of them, and lists them under More → Database → Manage → Backups. If your project is connected to a Supabase project of your own, Lovable lists backups under \"Managed by you in Supabase\", so what you have depends on your Supabase plan.",{"q":560,"a":561},"Does reverting in Lovable bring my data back?","No. Lovable says reverting restores your project's code only and does not roll back your database data. Rows that were added, changed or deleted after that version stay exactly as they are. A database backup is the copy that can put data back.",{"q":563,"a":564},"Are uploaded files included in a Lovable Cloud backup?","No. Lovable's backups and exports cover the database only, and files in storage are separate. You download them from More → Storage. A restore leaves them alone too, so a file deleted after the backup was taken stays deleted.",{"q":566,"a":567},"What happens to my backups if I remove the database or delete the project?","Removing the database deletes it together with its backups, your users' accounts, the files in storage and any export saved there, and it cannot be undone. Deleting the whole project pauses the backend and keeps the data for the time being: Lovable holds the project for 60 days and then deletes it permanently.",{"q":569,"a":570},"Can I download a Lovable Cloud backup?","The copy Lovable hands you is the export: a compressed PostgreSQL archive of the whole database, including user accounts and password hashes. You can request one every 24 hours, only while the database is running. Lovable saves it to your project's storage, so download it from More → Storage and keep it on a computer or drive outside Lovable.","\u002Fblog\u002Flovable-cloud-backup\u002Fcard-800x500.png",[573,574,575,576,577,578,579],"lovable cloud backup","lovable database backup","does lovable back up my database","how to back up lovable database","lovable cloud export database","lovable restore backup","lovable cloud supabase",{},true,"Lovable Cloud backup: what Lovable keeps for you","\u002Fblog\u002Flovable-cloud-backup","2026-11-11",{"title":5,"description":552},"blog\u002Flovable-cloud-backup",[588,589,590,591],"Yes. A Lovable Cloud backup of your database is taken once a day, and Lovable keeps up to roughly 14 days of them under More → Database → Manage → Backups.","The copies sit in the same backend as the database. Removing the database deletes them in the same step, and none of them holds the files your users uploaded.","A restore rolls the whole database back to one of those days and cannot be undone, and anyone with edit access to the project can run one.","The copy that outlives the project is the export: a PostgreSQL archive you download and keep yourself, with your storage files downloaded beside it.","EZZro9RGqk2n8j4VDuVGQSM4uIbEEqTj54E9iOtGYZ8",[594,601,607,613,619,625,631,637,643,649,655,661,662,668,674,680,686,692,698,704,710,716,722,728,734,740,746,752,758,764,770,776,782,788,794,800,806,812,818,824,830,836,842,848,854,860,866,872,878,884,890,896,902,908,914,920,926,932,938,943,949,955,961,967,973,979,985,991,997,1003,1009,1014,1020,1026,1032,1038,1044,1050,1056,1062,1068,1074,1080,1086,1092,1098,1104,1110,1116,1122,1128,1134,1140,1146,1152,1157,1163,1168,1174,1180,1186,1190,1196],{"path":595,"title":596,"description":597,"published":598,"category":599,"image":600,"draft":553},"\u002Fblog\u002Fsupabase-only-returns-1000-rows","Supabase only returns 1000 rows: how to get the rest","Supabase only returns 1000 rows per request because of its Max rows setting. How to page through the rest, count them, and what the cap is there for.","2026-11-22","Security basics","\u002Fblog\u002Fsupabase-only-returns-1000-rows\u002Fcard-800x500.png",{"path":602,"title":603,"description":604,"published":605,"category":599,"image":606,"draft":553},"\u002Fblog\u002Ferror-running-hook-uri","\"Error running hook URI\" in Supabase: why nobody can sign in","\"Error running hook URI\" means a Supabase Auth hook failed, so sign-in or sign-up fails for everyone. Where the real error is, and the safe fix.","2026-11-21","\u002Fblog\u002Ferror-running-hook-uri\u002Fcard-800x500.png",{"path":608,"title":609,"description":610,"published":611,"category":599,"image":612,"draft":553},"\u002Fblog\u002Fsupabase-realtime-channel-error","Supabase Realtime CHANNEL_ERROR: why a subscription gets nothing","Supabase Realtime CHANNEL_ERROR, or no events at all: usually a rule doing its job. How to read the reason and fix it without opening your data.","2026-11-20","\u002Fblog\u002Fsupabase-realtime-channel-error\u002Fcard-800x500.png",{"path":614,"title":615,"description":616,"published":617,"category":599,"image":618,"draft":553},"\u002Fblog\u002Ferr-ssl-version-or-cipher-mismatch","ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a new custom domain","ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a domain you just connected: why the name has no certificate yet, and when to wait, go DNS only or shorten the name.","2026-11-19","\u002Fblog\u002Ferr-ssl-version-or-cipher-mismatch\u002Fcard-800x500.png",{"path":620,"title":621,"description":622,"published":623,"category":599,"image":624,"draft":553},"\u002Fblog\u002Fapplication-error-a-client-side-exception-has-occurred","\"Application error: a client-side exception has occurred\" in Next.js","Application error: a client-side exception has occurred on your v0 or Next.js app: where the real error is and how to fix it.","2026-11-18","\u002Fblog\u002Fapplication-error-a-client-side-exception-has-occurred\u002Fcard-800x500.png",{"path":626,"title":627,"description":628,"published":629,"category":85,"image":630,"draft":553},"\u002Fblog\u002Freplit-database-rollback","Replit database rollback: does a checkpoint bring your data back?","A Replit database rollback restores the development database only when you ask. Your live data has a restore of its own. Which one you need, and how.","2026-11-17","\u002Fblog\u002Freplit-database-rollback\u002Fcard-800x500.png",{"path":632,"title":633,"description":634,"published":635,"category":599,"image":636,"draft":553},"\u002Fblog\u002Fthe-object-exceeded-the-maximum-allowed-size","\"The object exceeded the maximum allowed size\" in Supabase Storage","\"The object exceeded the maximum allowed size\" means a Supabase Storage limit refused the file. Which of two limits did it, and how to raise it.","2026-11-16","\u002Fblog\u002Fthe-object-exceeded-the-maximum-allowed-size\u002Fcard-800x500.png",{"path":638,"title":639,"description":640,"published":641,"category":599,"image":642,"draft":553},"\u002Fblog\u002Fsignups-not-allowed-for-this-instance","\"Signups not allowed for this instance\" in Supabase","\"Signups not allowed for this instance\" is Supabase refusing new accounts. Which switch does it, and why hiding your sign-up form is not the same thing.","2026-11-15","\u002Fblog\u002Fsignups-not-allowed-for-this-instance\u002Fcard-800x500.png",{"path":644,"title":645,"description":646,"published":647,"category":599,"image":648,"draft":553},"\u002Fblog\u002Fis-lovable-down-or-your-app","Is Lovable down, or is it your app? How to tell","Is Lovable down, or is it your app? Its editor, hosting and backend fail separately, and a paused backend looks like an outage. Here is how to tell.","2026-11-14","\u002Fblog\u002Fis-lovable-down-or-your-app\u002Fcard-800x500.png",{"path":650,"title":651,"description":652,"published":653,"category":599,"image":654,"draft":553},"\u002Fblog\u002Ffailed-to-load-module-script","\"Failed to load module script\": the blank page after a deploy","Failed to load module script and a blank page after a deploy: how to tell if one visitor or every visitor sees it, and the fix for each case.","2026-11-13","\u002Fblog\u002Ffailed-to-load-module-script\u002Fcard-800x500.png",{"path":656,"title":657,"description":658,"published":659,"category":599,"image":660,"draft":553},"\u002Fblog\u002Ferr-too-many-redirects","ERR_TOO_MANY_REDIRECTS on a custom domain behind Cloudflare","ERR_TOO_MANY_REDIRECTS after you put Cloudflare in front of your site: why the loop happens, and the fix that keeps your sign-ins encrypted.","2026-11-12","\u002Fblog\u002Ferr-too-many-redirects\u002Fcard-800x500.png",{"path":583,"title":5,"description":552,"published":584,"category":85,"image":571,"draft":553},{"path":663,"title":664,"description":665,"published":666,"category":599,"image":667,"draft":553},"\u002Fblog\u002Fthis-site-cant-be-reached","\"This site can't be reached\" on your own domain: read the code","Your own site says \"This site can't be reached\". The code under the headline tells you whether the name, the host or the network failed, and what to fix.","2026-11-10","\u002Fblog\u002Fthis-site-cant-be-reached\u002Fcard-800x500.png",{"path":669,"title":670,"description":671,"published":672,"category":599,"image":673,"draft":553},"\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":675,"title":676,"description":677,"published":678,"category":599,"image":679,"draft":553},"\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":681,"title":682,"description":683,"published":684,"category":599,"image":685,"draft":553},"\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":687,"title":688,"description":689,"published":690,"category":599,"image":691,"draft":553},"\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":693,"title":694,"description":695,"published":696,"category":599,"image":697,"draft":553},"\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":699,"title":700,"description":701,"published":702,"category":599,"image":703,"draft":553},"\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":705,"title":706,"description":707,"published":708,"category":599,"image":709,"draft":553},"\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":711,"title":712,"description":713,"published":714,"category":599,"image":715,"draft":553},"\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":717,"title":718,"description":719,"published":720,"category":599,"image":721,"draft":553},"\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":723,"title":724,"description":725,"published":726,"category":599,"image":727,"draft":553},"\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":729,"title":730,"description":731,"published":732,"category":85,"image":733,"draft":553},"\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","\u002Fblog\u002Fdatabase-error-deleting-user\u002Fcard-800x500.png",{"path":735,"title":736,"description":737,"published":738,"category":599,"image":739,"draft":553},"\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":741,"title":742,"description":743,"published":744,"category":599,"image":745,"draft":553},"\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":747,"title":748,"description":749,"published":750,"category":599,"image":751,"draft":553},"\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":753,"title":754,"description":755,"published":756,"category":599,"image":757,"draft":553},"\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":759,"title":760,"description":761,"published":762,"category":599,"image":763,"draft":553},"\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":765,"title":766,"description":767,"published":768,"category":599,"image":769,"draft":553},"\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":771,"title":772,"description":773,"published":774,"category":599,"image":775,"draft":553},"\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":777,"title":778,"description":779,"published":780,"category":599,"image":781,"draft":553},"\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":783,"title":784,"description":785,"published":786,"category":599,"image":787,"draft":553},"\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":789,"title":790,"description":791,"published":792,"category":599,"image":793,"draft":553},"\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":795,"title":796,"description":797,"published":798,"category":599,"image":799,"draft":553},"\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":801,"title":802,"description":803,"published":804,"category":599,"image":805,"draft":553},"\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":807,"title":808,"description":809,"published":810,"category":599,"image":811,"draft":553},"\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":813,"title":814,"description":815,"published":816,"category":599,"image":817,"draft":553},"\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":819,"title":820,"description":821,"published":822,"category":599,"image":823,"draft":553},"\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":825,"title":826,"description":827,"published":828,"category":599,"image":829,"draft":553},"\u002Fblog\u002Fdatabase-error-saving-new-user","\"Database error saving new user\" in Supabase: how to fix it","\"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":831,"title":832,"description":833,"published":834,"category":599,"image":835,"draft":553},"\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":837,"title":838,"description":839,"published":840,"category":599,"image":841,"draft":553},"\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":843,"title":844,"description":845,"published":846,"category":599,"image":847,"draft":553},"\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":849,"title":850,"description":851,"published":852,"category":599,"image":853,"draft":553},"\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":855,"title":856,"description":857,"published":858,"category":599,"image":859,"draft":553},"\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":861,"title":862,"description":863,"published":864,"category":599,"image":865,"draft":553},"\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":867,"title":868,"description":869,"published":870,"category":599,"image":871,"draft":553},"\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":873,"title":874,"description":875,"published":876,"category":599,"image":877,"draft":553},"\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":879,"title":880,"description":881,"published":882,"category":599,"image":883,"draft":553},"\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":885,"title":886,"description":887,"published":888,"category":599,"image":889,"draft":553},"\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":891,"title":892,"description":893,"published":894,"category":599,"image":895,"draft":553},"\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":897,"title":898,"description":899,"published":900,"category":599,"image":901,"draft":553},"\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":903,"title":904,"description":905,"published":906,"category":599,"image":907,"draft":553},"\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":909,"title":910,"description":911,"published":912,"category":599,"image":913,"draft":553},"\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":915,"title":916,"description":917,"published":918,"category":599,"image":919,"draft":553},"\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":921,"title":922,"description":923,"published":924,"category":85,"image":925,"draft":553},"\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":927,"title":928,"description":929,"published":930,"category":85,"image":931,"draft":553},"\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":933,"title":934,"description":935,"published":936,"category":85,"image":937,"draft":553},"\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":939,"title":940,"description":941,"published":936,"category":599,"image":942,"draft":553},"\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":944,"title":945,"description":946,"published":947,"category":599,"image":948,"draft":553},"\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":950,"title":951,"description":952,"published":953,"category":599,"image":954,"draft":553},"\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":956,"title":957,"description":958,"published":959,"category":85,"image":960,"draft":553},"\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":962,"title":963,"description":964,"published":965,"category":599,"image":966,"draft":553},"\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":968,"title":969,"description":970,"published":971,"category":599,"image":972,"draft":553},"\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":974,"title":975,"description":976,"published":977,"category":599,"image":978,"draft":553},"\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":980,"title":981,"description":982,"published":983,"category":599,"image":984,"draft":553},"\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":986,"title":987,"description":988,"published":989,"category":599,"image":990,"draft":553},"\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":992,"title":993,"description":994,"published":995,"category":599,"image":996,"draft":553},"\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":998,"title":999,"description":1000,"published":1001,"category":599,"image":1002,"draft":553},"\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":1004,"title":1005,"description":1006,"published":1007,"category":599,"image":1008,"draft":553},"\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":65,"title":1010,"description":1011,"published":1012,"category":85,"image":1013,"draft":553},"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":1015,"title":1016,"description":1017,"published":1018,"category":85,"image":1019,"draft":553},"\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":1021,"title":1022,"description":1023,"published":1024,"category":85,"image":1025,"draft":553},"\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":1027,"title":1028,"description":1029,"published":1030,"category":599,"image":1031,"draft":553},"\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":1033,"title":1034,"description":1035,"published":1036,"category":599,"image":1037,"draft":553},"\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":1039,"title":1040,"description":1041,"published":1042,"category":599,"image":1043,"draft":553},"\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":1045,"title":1046,"description":1047,"published":1048,"category":599,"image":1049,"draft":553},"\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":1051,"title":1052,"description":1053,"published":1054,"category":599,"image":1055,"draft":553},"\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":1057,"title":1058,"description":1059,"published":1060,"category":599,"image":1061,"draft":553},"\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":1063,"title":1064,"description":1065,"published":1066,"category":599,"image":1067,"draft":553},"\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":1069,"title":1070,"description":1071,"published":1072,"category":599,"image":1073,"draft":553},"\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":1075,"title":1076,"description":1077,"published":1078,"category":599,"image":1079,"draft":553},"\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":1081,"title":1082,"description":1083,"published":1084,"category":599,"image":1085,"draft":553},"\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":1087,"title":1088,"description":1089,"published":1090,"category":85,"image":1091,"draft":553},"\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":1093,"title":1094,"description":1095,"published":1096,"category":599,"image":1097,"draft":553},"\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":1099,"title":1100,"description":1101,"published":1102,"category":85,"image":1103,"draft":553},"\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":1105,"title":1106,"description":1107,"published":1108,"category":599,"image":1109,"draft":553},"\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":1111,"title":1112,"description":1113,"published":1114,"category":599,"image":1115,"draft":553},"\u002Fblog\u002Fwhere-to-find-supabase-api-keys","Where to find your Supabase URL, publishable and secret keys","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":1117,"title":1118,"description":1119,"published":1120,"category":599,"image":1121,"draft":553},"\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":1123,"title":1124,"description":1125,"published":1126,"category":599,"image":1127,"draft":553},"\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":1129,"title":1130,"description":1131,"published":1132,"category":85,"image":1133,"draft":553},"\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":1135,"title":1136,"description":1137,"published":1138,"category":85,"image":1139,"draft":553},"\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":1141,"title":1142,"description":1143,"published":1144,"category":599,"image":1145,"draft":553},"\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":1147,"title":1148,"description":1149,"published":1150,"category":599,"image":1151,"draft":553},"\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":309,"title":1153,"description":1154,"published":1155,"category":85,"image":1156,"draft":553},"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":1158,"title":1159,"description":1160,"published":1161,"category":599,"image":1162,"draft":553},"\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":1164,"title":1165,"description":1166,"published":1161,"category":599,"image":1167,"draft":553},"\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":1169,"title":1170,"description":1171,"published":1172,"category":599,"image":1173,"draft":553},"\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":1175,"title":1176,"description":1177,"published":1178,"category":85,"image":1179,"draft":553},"\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":1181,"title":1182,"description":1183,"published":1184,"category":599,"image":1185,"draft":553},"\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":275,"title":1187,"description":1188,"published":1184,"category":85,"image":1189,"draft":553},"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":1191,"title":1192,"description":1193,"published":1194,"category":85,"image":1195,"draft":553},"\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":1197,"title":1198,"description":1199,"published":1194,"category":599,"image":1200,"draft":553},"\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",1795336308202]