From connect to restore
in under two minutes.
Backup247 sits next to your no-code stack and quietly captures every change. Here is exactly what happens — from the first OAuth handshake to a one-click restore.
The three steps
Set it up once. Forget it forever
Connect
Authorise Backup247 with OAuth — Airtable, Notion or Firebase. No API keys to manage, no webhooks to configure. We request the minimum scopes needed to read your data and write restores back when you ask us to.
Schedule
Pick a cadence per base or workspace — hourly, every 4 hours, daily, or anything in between. Set retention windows independently: keep 365 days for production, 30 days for reference data. The first snapshot starts immediately so you are protected from minute one.
Sleep
Backup247 takes it from here. Snapshots run on schedule, attachments are captured alongside records, and a unified calendar shows every backup across every tool. Need to restore? Pick a moment, diff it against today, and roll back in one click.
What you get
One dashboard. Every backup.
After connect + schedule, this is the view you live in — backup health, recent snapshots and connector status in a single screen.
Live health overview
Total backups, last run, storage used and failed jobs — across every connected tool.
Recent backups feed
Per resource: records captured, size, status and time — failures highlighted instantly.
Connectors at a glance
Every workspace you have linked, with last-tested status and one-click add-connector.
Behind the scenes
What actually happens during a backup
A snapshot is more than a database dump. Here is how Backup247 captures, stores and protects each one.
Full snapshots, not just diffs
Every backup is a complete, queryable copy of your data at that exact moment — schema, records, linked relations and attachments. You never have to replay a chain of incremental changes to get back to a usable state.
Encrypted at rest and in transit
All snapshots are written to a private object store with AES-256 at rest, TLS 1.3 in transit and signed-URL access only. Nothing is publicly reachable, even by accident.
Tenant-isolated storage
Each organisation gets its own logically isolated storage path, enforced at the infrastructure layer — not just behind an application check. On Scale plans you can bring your own S3 or R2 bucket.
Anomaly alerts
If a backup fails, a snapshot is unexpectedly small, or a sudden mass-delete is detected, we email and notify in-app immediately so a silent failure never costs you a weekend.
Connect everything
Link every workspace you rely on
From one screen you can add, monitor and manage every connector. Green means healthy, grey means it needs attention.
Multi-workspace grid
Connect every client base, team workspace or project tool. Each card shows the name, type and live status in one glance.
Tested & active status
Green dot means the connector is healthy and the last test passed. No guessing whether a backup source is still reachable.
One-click to backups
Jump straight to a workspace's backup history, schedule or restore flow from the connector card — no extra navigation.
Step 1 — Pick your tool
Start by choosing what to back up
The first thing you do in Backup247 is pick a source. Each connector knows how to back up structure, data and attachments — and how to restore them safely.
Choose a tool
Select which no-code tool you want to back up.
Need another tool? Request a connector
Continue with AirtableLifecycle of a snapshot
Six things happen, every single backup
Trigger
Scheduled cron fires, or you click Run now.
Capture
We page through the API, capturing schema, records and attachments in parallel.
Encrypt & store
Snapshot is compressed, encrypted, and written to your tenant-isolated bucket.
Index
Indexed for fast browse, search and diff against any prior snapshot.
Verify
Integrity check runs against the manifest; any drift triggers an alert.
Available
The snapshot appears on your calendar, ready to browse or restore.
Security
Your data, your boundaries
Backup247 is built so that a worst-case incident on our side cannot become a worst-case incident on yours. Every layer assumes the next one might fail.
- OAuth scopes limited to read + write-back on demand
- Row-level security on every Postgres query
- AES-256 encryption at rest, TLS 1.3 in transit
- Private buckets, signed-URL access only
- Bring your own S3 or R2 bucket on Scale plans
- Full audit log of every restore and member action
FAQ
Common questions
How long does the first backup take?
For most Airtable or Notion workspaces, the first full snapshot completes in 2–10 minutes. Subsequent snapshots are usually faster because we parallelise the capture across tables.
What happens if a scheduled backup fails?
We automatically retry with exponential backoff. If it still fails, you get an email and an in-app alert with the exact reason — expired OAuth, rate limit, schema change, etc.
Can I restore a single record instead of a whole table?
Yes. Restores work at any level — single field, single record, full table, or the entire workspace. You pick the scope before confirming.
Are attachments included?
Yes. Files, images and PDFs attached to records are captured in the same snapshot and restore correctly linked, not as orphans.
Do you store my data forever?
Only as long as your retention window says. After that, snapshots are permanently deleted. You set the window per resource.
Start backing up in 2 minutes
14-day free trial. No credit card. Cancel any time.