Features

Every safety net,
in one tool.

Per-resource schedules

You set the backup cadence individually for every base, database or workspace — not as a single account-wide setting. A production CRM base that changes every hour gets hourly backups. A reference table that barely moves gets a daily snapshot. Retention windows work the same way: keep 365 days of history for the bases that matter and 30 days for everything else.

One-click restore

Select a snapshot from the calendar, pick the scope — a single record, a full table, or the entire workspace — and click Restore. Backup247 writes the data back to its original location, preserving field types, linked records and attachments. Every restore is logged with a timestamp, a target, and a completion status so nothing happens silently.

Snapshot compare

Before you restore anything, you can diff any two snapshots side by side. Added records appear in green, modified cells in amber, deleted rows in red, at the field level. This matters because most incidents are not clean deletes — they are overwrites where the data is still there but wrong, and you need to see exactly what changed before you commit.

Browse snapshots

Every snapshot is a full, navigable copy of your data at that moment. Open any table, scroll through the records, use the search bar — exactly as you would in the live tool, but frozen in time. Useful for answering the question "what did this record say last Tuesday?" without triggering a restore.

Attachment backups

Files, images and PDFs are captured alongside their parent records in every snapshot. When you restore a record or table, its attachments restore with it — correctly linked, not orphaned in a separate folder. This is the gap most backup tools leave open.

Unified calendar

A single month, week or day view shows every completed backup and every scheduled backup across all your connected tools. A failed or skipped snapshot shows up as a red indicator on the calendar so nothing goes unnoticed.

Multiple connectors

Airtable and Notion are live today. Firebase is in active development. Slack, HubSpot and Jira are on the roadmap. All connectors share the same dashboard, the same diff interface and the same restore flow — you do not learn a new tool for each integration.

Restore history

Every restore your team has ever triggered is logged in a searchable table: when it happened, which snapshot was used, which table or base was targeted, which user triggered it, and whether it succeeded or failed. Useful for incident postmortems and for auditing who changed what.

Isolated storage

Backups land in a private bucket with signed-URL access only. Nothing is publicly reachable, and each organisation's storage is isolated at the infrastructure level — not just behind an application-layer permission check. On Scale plans you can bring your own S3 or R2 bucket instead.

Multi-tenant orgs

Invite teammates, assign roles and manage members from the organisation settings. Every organisation's data is fully isolated — a member of one organisation cannot query or restore data belonging to another, even if they share the same plan.

Row-level security

Every database query Backup247 makes is scoped to your organisation via Postgres row-level security. There is no shared table that could accidentally leak one tenant's snapshot metadata to another.

OAuth or API key

Connect a new tool in under a minute via OAuth — no API keys to copy, no webhooks to configure. For sources that require an API key rather than OAuth, you can paste the key directly in the connector settings.

Inside the app

Every feature, one dashboard

Schedules, snapshots, restores and connectors — all surfaced in one place so you never wonder whether a backup actually ran.

app.backup247.app/dashboard
Backup247 dashboard showing total backups, last backup, storage used, failed jobs, recent backups list and connector status

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.

Deep dive

Three features people switch tools for

Per-resource schedules

One cadence does not fit every base

A production CRM that takes 200 writes per hour needs a different schedule than a static reference table. With Backup247 you set cadence and retention independently per base, workspace or database — keep 365 days for the data that matters, 30 days for the rest, and stop paying to store snapshots you will never restore.

  • Hourly to daily cadence per resource
  • Independent retention windows
  • Pause individual schedules without disconnecting
Snapshot compare

See exactly what changed before you restore

Most data incidents are not clean deletes — they are silent overwrites where the records are still there but wrong. Backup247 diffs any two snapshots field-by-field: added in green, modified in amber, deleted in red. You confirm the change before it is rolled back.

  • Field-level diff across any two moments
  • Filter by table, user or change type
  • Preview the restore impact before committing
One-click restore

Roll back without rebuilding

Pick a snapshot, choose the scope — single record, table or full workspace — and click Restore. Backup247 writes the data back to its original location with field types, linked records and attachments intact. Every restore is logged with who, what and when.

  • Restore at field, record, table or workspace level
  • Linked records and attachments stay linked
  • Full audit log of every restore action

Backup247 vs DIY

What you would otherwise build yourself

A scheduled export script gets you 20% of the way. Diffs, attachments, retention and alerts are the other 80%.

Capability
Backup247
DIY script
Per-resource backup cadence
Field-level snapshot diffs
Attachment backup & restore
One-click restore to original location
365 days retention out of the box
Anomaly alerts on missing or shrinking backups
Multi-tenant org isolation
Engineering time required
Zero
Ongoing

Integrations

One dashboard for your whole no-code stack

Same diff interface, same restore flow, same calendar — no matter which tool the data lives in.

Airtable
Live
Notion
Live
Firebase
Beta
Slack
Soon
HubSpot
Soon
Jira
Soon

Connect everything

All your workspaces, one grid

Link every Airtable base and Notion workspace your team depends on. Each connector card shows live health, last test and a direct route to its backups.

app.backup247.app/connectors
Backup247 connectors grid showing multiple linked Airtable workspaces with active status and manage backups buttons

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.

Supported tools

Choose a tool to back up

Every connector backs up the structure, the data and the attachments — and restores them into a new or existing workspace.

Choose a tool

Select which no-code tool you want to back up.

Who it is for

Built for the people responsible when data goes missing

Ops teams

Protect the CRM, project tracker or pipeline that the whole company runs on. Recover from a bad bulk-edit in minutes, not hours of manual fix-ups.

No-code builders

Ship faster knowing every base your client app reads from is versioned. Roll back a schema change without explaining downtime to your customer.

Agencies & consultants

Manage backups for every client workspace from one dashboard. Hand over restore access without giving up control of the schedule or retention.

Start backing up in 2 minutes

14-day free trial. No credit card. Cancel any time.