Safety net for AI-built apps
Back up your AI-built app.Know when it goes down.
Connect your Supabase project once. Qollam saves a copy of your database every night and checks your app every 30 minutes.
Free for one project. For apps built with Lovable, Bolt, Cursor, Replit, or v0 on Supabase.
Saved today at 03:00 UTC
Up. Checked 4 minutes ago.
Three ways a working app disappears.
The free plan has no backups.
Supabase's free plan does not include automatic database backups. If a table is dropped or a project is deleted, there is nothing to restore from.
Idle projects pause.
A free project pauses after a week without activity. Your app stops answering, and nothing tells you why.
Agents run commands.
AI coding tools can run SQL and delete projects. One wrong command is possible, and without a backup it cannot be undone.
Qollam keeps a copy, watches the app, and tells you in plain words what went wrong.
Set up once. Then it runs.
Connecting takes a couple of minutes. After that there is nothing to remember.
Connect your Supabase project.
Click Connect and approve access on Supabase's own page. Qollam never asks for your database password or a secret key.
Qollam backs up every night.
At 03:00 UTC, every table in your public schema is saved as one JSON file. Download the latest backup from the project card whenever you want it.
Qollam checks your app every 30 minutes.
Add your live app address. Qollam checks it 48 times a day and shows a green or red dot, with the status code it got back.
When something fails, it says what to do.
A failed check or backup shows its reason in plain English, like "your project is probably paused, restore it in the Supabase dashboard." The message stays on the card until the problem is fixed.
What you get.
A copy of your data you can read, and a clear view of whether your app is up.
{
"project": {
"ref": "abcd1234efgh5678",
"name": "my-saas-app"
},
"created_at":
"2026-10-04T03:00:12Z",
"schema": "public",
"tables": {
"profiles": [
{ "id": 1, "name": "Ada" },
{ "id": 2, "name": "Grace" }
],
"orders": [
{ "id": 41, "total": 29 }
]
}
}Every public table, every row.
Your app's data lives in the public schema. That is what each backup captures.
Readable and portable.
A backup is plain JSON. Open it in a browser, hand it to a developer, or load it anywhere.
Uptime you can see.
Every project has a dot: green when the last check passed, red when it failed, with the time of that check.
Errors in plain English.
Status 544 becomes "your project is probably paused." Status 404 becomes "the saved address may be wrong."
Any builder.
Qollam connects to Supabase, not to your editor. It works the same whether you built the app in Lovable, Bolt, Cursor, Replit, or v0.
How Qollam handles your access.
Qollam holds a key to your database, so here is exactly what it does with it.
- OAuth, not passwords.
- You approve the connection on Supabase's own screen. Qollam never sees your database password, and you never paste a secret key.
- Encrypted before it is stored.
- Access tokens are encrypted with AES-256-GCM. The encryption key is a separate server secret, not part of the code.
- Locked from the browser.
- The table that holds tokens cannot be read from a browser. Only server code can decrypt them.
- Schedules are private.
- Scheduled backups and checks run only with a private key, so nobody else can trigger them.
- Your data stays out of the explanations.
- Failure explanations are drafted by an AI model that only sees status codes, short error text, and check times. It never sees your table contents or your tokens.
What Qollam does not do yet.
Backups cover the tables in your public schema. They do not include auth users, Storage files, or Edge Functions.
Restore is a download for now, not a one-click button. Alert emails are not live yet, so today the status shows on your dashboard. Email alerts and restore are next.
Questions.
Do you need my database password?
No. You connect through Supabase's own approval screen and choose to allow access there.
What does a backup contain?
Every table in your project's public schema, row by row, saved as one JSON file. Auth users, Storage files, and Edge Functions are not included yet.
How often does it run?
Backups run once a day at 03:00 UTC, and uptime checks run every 30 minutes. You can also run a backup yourself from the project card with Back up now.
What if my Supabase project is paused?
Qollam cannot read a paused project. The card shows that the backup failed and that the project is probably paused. Restore it in the Supabase dashboard, then press Back up now.
Does it work if my app does not use Supabase?
Not yet. Backups connect to Supabase today.
What does it cost?
One project is free. Pro, for up to 5 projects, is $15 a month and is not open yet. You can join the waitlist on the pricing page.
Is my data sent to an AI model?
Only the explanation of a failure involves an AI model. It sees a status code, a short error message, and check times. It never receives table contents or tokens.
Who makes Qollam?
One person who builds apps with AI tools. When I connected my own old projects to test Qollam, several had paused and I had not noticed. That is why it exists.
Backups on. Uptime watched. The project stays alive.
Connect a Supabase project and run your first backup in minutes.
Connect a Supabase project