Idea checked

a database backup service

This is a crowded space with many open-source tools, plus cloud vendors already sell database backup services, so a generic backup service is unlikely to be easy.

Confidence: high — There is a lot of real data here: multiple mature repos with thousands of stars, several HN discussions, and vendor pages showing established commercial offerings.

58 signals collected
11.8s to run
2026-08-01

hackernews 30
github 20
tavily 8

Who is already building this From data

There are several large open-source backup tools already, including databasus/databasus (7,825 stars), pgbackrest (4,281), wal-g (4,200), gobackup (2,771), pgbackweb (2,611), Portabase (1,568), and container-db-backup (1,524).
The space is not limited to one database: tools already cover PostgreSQL, MySQL, MariaDB, SQL Server, MongoDB, SQLite, Redis, and Docker volumes in different combinations.
Commercial and vendor-backed offerings already exist, including Oracle Database Backup Cloud Service, AWS Backup, Alibaba Cloud database disaster recovery, and Cohesity-style database backup products.
There are also app-specific and ecosystem-specific backup products like spatie/laravel-backup, dbatools for SQL Server automation, and Supabase CLI with Postgres backups.

What people actually say From data

HN posts repeatedly frame backup verification as a real pain point, for example 'Tool for programmatically verifying database backups' and 'How to test database backups.'
- hackernews Show HN: Uphold – Tool for programmatically verifying database backups 2016-03-31
- hackernews How to test database backups 2022-03-04
People ask basic operational questions like 'How do you do database backups?' and 'Do you use any online database backup service?', which suggests the problem is common and recurring.
- hackernews How do you do database backups? 2009-01-08
- tavily Do you use any online database backup service? : r/VPS
Some discussions focus on failure modes and fear, including corrupted backups after migrations, public backup leaks, and data loss stories.
There is interest in geo-redundancy, decentralized storage, and remote/local backup workflows, which points to demand for more than a simple dump-and-store tool.

Where the opening is Model estimate

The model's read of the signals below — not something anyone measured.

The clearest gap is not 'backup exists' but 'backup verification, restore testing, and operational confidence' for ordinary teams that do not want to manage pgBackRest/WAL-G-style tooling themselves.
Another possible gap is a truly user-friendly web product that supports many databases and storage targets without requiring CLI-heavy setup; Portabase and databasement move in this direction, but the market still looks fragmented.
A service aimed at small teams or agencies may have room if it combines scheduling, restore verification, encryption, and cloud delivery in one place, because users keep asking for simple automation.
There may be room for a cross-network / edge deployment model, since Portabase specifically mentions agents and multiple networks.
- hackernews Show HN: Portabase – open-source database backup/restore tool 2026-01-08
- hackernews Portabase 1.2.7: Large database backup support, UI/UX improvements 2026-02-18

How big the market might be Model estimate

The model's read of the signals below — not something anyone measured.

The installed base is clearly large: many backup-related repos have thousands of stars, with multiple projects above 1,500 stars and one above 7,800.
Commercial vendors explicitly market database backup as a standard infrastructure category for on-prem, cloud, and hybrid environments.
The scope includes many database types and deployment styles, which implies a broad market rather than a niche one-database workflow.
HN engagement is modest on individual posts, but the recurrence across many years suggests steady demand rather than a one-off trend.

What could go wrong Model estimate

The model's read of the signals below — not something anyone measured.

The space is crowded with mature open-source alternatives, so a new generic service will face strong comparison on price and features.
Backups are high-trust infrastructure; examples in the signals mention corruption, leaks, and catastrophic data loss, so any reliability miss would be very damaging.
Support burden could be high because users want many database engines, many storage backends, restore testing, encryption, and edge/network support.
Cloud platforms already bundle backup features, which can make a standalone service harder to sell unless it clearly beats built-in options.

What to do this week Model estimate

The model's read of the signals below — not something anyone measured.

Narrow the product to one painful wedge: automated restore verification for PostgreSQL/MySQL backups, since verification is repeatedly discussed and not just backup creation.
Make the product opinionated for a specific customer type such as agencies, small SaaS teams, or self-hosted app operators, because 'one service for every database' is already crowded.
Ship with a strong default workflow: connect database, schedule backups, encrypt, store to S3/SFTP/local, and run restore checks automatically.
Differentiate on evidence of recovery, not just backup storage: show last successful restore, backup age, and corruption checks in the UI.

Check another idea