David-Crty

databasement: Manage Self-Hosted Database Backups

Databasement is a self-hosted PHP web app for scheduling, storing, monitoring, and restoring backups across several database engines. It supports remote storage, SSH tunnels, team access, and Docker, Compose, and Kubernetes deployment.

Stars
2.6k
Forks
297
Stars, last 30 days
+81
Last commit
6 days ago
Contributors
13

Our take

Activeregular commits and releases

Health score

68/100

How it is scored
Activity
90
Community
42
Issues
59
Pull requests
79

+81 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • Merges more pull requests than 86% of the projects we track

Databasement is a feature-rich, actively maintained option for teams that want a single self-hosted control plane for database backups and restores.

Good fit if

  • You manage one or more of the supported database engines and want scheduling, retention, storage, and restore workflows in one web UI.
  • Self-hosting matters, and Docker, Compose, Helm, or native Ubuntu deployment fits your environment.
  • You want to automate backup management through its REST API or MCP server; the project is actively developed, handles issues, and has contributions from multiple people without heavy contributor concentration.

Look elsewhere if

  • You need Redis or Valkey restore support, which the README lists as unavailable.
  • You need a backup manager for a database engine not listed as supported.
  • You do not want to operate a PHP application and its supporting deployment setup.
All health signals
Last commit2026-11-04 (6 days ago)
Commits, last 90 days100+
Releases, last 12 months100+ (latest v1.10.10, 2026-11-04)
Contributors13 (top contributor: 75% of commits)
Issues closed, last 90 days11+ (typically closed in 5 days)
Pull requests merged, last 90 days79 (typically merged in 0 days)
Project age12 months

Checked on 2026-11-11 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

2,626

Forks

299

Change since Nov 14, 2026: 0 stars·0 forks

Overview

Databasement is a self-hosted PHP web application for managing backups of MySQL, PostgreSQL, MariaDB, Microsoft SQL Server, MongoDB, SQLite, Firebird, Redis, and Valkey. It brings scheduled backups, storage destinations, job monitoring, and restore workflows into one interface, helping teams avoid managing separate backup scripts and processes for each database.

It is aimed at people who want to control their backup infrastructure, including teams with databases behind firewalls, multiple environments, or shared operational responsibilities. The project supports Docker, Docker Compose, Kubernetes with Helm, and native Ubuntu installations. See the project documentation and live demo.

Key Features

  • Schedule daily or weekly backups and configure time-based or GFS retention.
  • Back up to local storage, S3-compatible storage, Azure Blob Storage, Samba/SMB, SFTP, or FTP.
  • Connect to private database networks through SSH tunnels, or use remote agents for isolated networks without inbound access.
  • Compress backups with gzip or zstd, or encrypt them with AES-256.
  • Restore snapshots to compatible servers, including across environments, and schedule recurring restores.
  • Track backup and restore progress with job logs, and send failure notifications through supported messaging services.
  • Manage workspaces and roles, use OAuth/SSO and optional two-factor authentication, or automate work through the REST API and MCP server.
  • Inspect supported MySQL, PostgreSQL, and SQLite servers with the built-in Adminer data browser.

Use Cases

  • A small operations team wants scheduled backups and retention policies for several database types without building a separate management interface.
  • A self-hosting administrator needs to send database backups to S3, a file share, or an SFTP server while keeping the management application under their control.
  • A team with databases on private or firewalled networks needs SSH tunnels or outbound-only remote agents to move backups to central storage.
  • Developers want to refresh staging from a recent production snapshot, manually or on a recurring schedule.
  • An organization needs multiple users to manage backups with separate workspaces, roles, and sign-in options.

What you need

Detected in the repository

  • Node.js (from package.json)
  • PHP (from composer.json)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • A Helm chart for Kubernetes
  • A test suite and automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Run the container with SQLite for the application's own data:

docker run -d \
  --name databasement \
  -p 2226:2226 \
  -e DB_CONNECTION=sqlite \
  -e DB_DATABASE=/data/database.sqlite \
  -e ENABLE_QUEUE_WORKER=true \
  -v ./databasement-data:/data \
  davidcrty/databasement:1

Open http://localhost:2226 to create an administrator account. See the Docker guide and configuration guide for production setup details.

Alternatives

  • borgbackupserver: Borg Backup Server manages scheduled file and machine backups, rather than database-engine-specific backups and restores.
ProjectLanguageLicenseStarsStatus
databasementPHPMIT2.6kActive
borgbackupserverPHPOther353Active

Considerations

  • The application requires PHP and Node.js according to its Composer and package manifests. Production use also means configuring the application database, queue worker, scheduler, and access to the database servers and storage you intend to use.
  • Restore capability varies by engine. Redis and Valkey backups are supported, but restore is not listed as available; consult the supported versions documentation for engine-specific details.
  • The project is actively maintained, with recent commits and releases and ongoing issue and pull-request activity. Its measured contributor base is not concentrated in one person, though operational teams should still evaluate the project against their own maintenance and recovery requirements.
  • The MIT license permits broad reuse, subject to its notice and license terms. Review the license file for obligations before distributing modified copies.

Found this useful?

Share it with someone who would like databasement.

Comparisons