Databases

Four database families today. Built to support many more.

MySQL and MariaDB, MongoDB, PostgreSQL and Microsoft SQL Server — each covered in the terms that engine actually uses rather than flattened into a lowest common denominator. The platform is built so that adding another engine is a matter of coverage, not architecture.

Explore Monitoring See Backup & Recovery

Engines

Pick an engine

MySQL / MariaDB

Deep operational coverage across the MySQL family, including Galera and InnoDB Cluster.

MongoDB

Replica set and sharded cluster operations, with policy-driven backup.

PostgreSQL

Full operational coverage for PostgreSQL across monitoring, backup and recovery.

Microsoft SQL Server

Enterprise SQL Server operations under the same platform and policies.

Coverage

Capability matrix

Capability coverage by engine family, today. Each cell links to the detail on that engine’s page — and the matrix is generated from the content collection, so an added engine becomes a column without a template change.
Capability	MySQL / MariaDB	MongoDB	PostgreSQL	Microsoft SQL Server
Supported versions	MySQL 8.0 · MySQL 8.4 LTS · MariaDB 10.11 · MariaDB 11.4	MongoDB 6.0 · MongoDB 7.0 · MongoDB 8.0	PostgreSQL 14 · 15 · 16 · 17 · 18	SQL Server 2019 · 2022 · 2025
Monitoring	Database + system metrics	Database + system metrics	Database + system metrics	Database + system metrics
Query Analytics	Slow queries · timeline · index reports	Slow queries · timeline · index reports	Slow queries · timeline · index reports	Slow queries · timeline · index reports
Backup	Percona XtraBackup — supported MySQL and PXC versions · mariabackup — MariaDB · mysqldump — logical and fallback backup	mongodump / mongorestore · Continuous oplog capture and replay for point-in-time recovery	pg_basebackup · pgBackRest · pg_dump	Native full backup · Differential backup · Transaction-log backup
Point-in-time recovery	Base or full backup plus archived binary-log segments	Base backup plus continuous oplog capture and retention	Base backup plus continuous WAL archiving	Full backup plus a continuous transaction-log backup chain, optionally using differential backups
HA / topology awareness	Standalone · Replication Cluster · Galera Cluster · InnoDB Cluster	Standalone · Replica Set · Sharded Cluster	Standalone · Streaming Replication · Logical Replication	Standalone · Always On Availability Groups · Failover Cluster Instances
Recommendations	6 categories	6 categories	6 categories	5 categories
AI context	Full operational context	Full operational context	Full operational context	Full operational context
Provisioning & automation	Terraform + Ansible	Terraform + Ansible	Terraform + Ansible	Terraform + Ansible
Integrations	Jira · PagerDuty · Slack · Teams · Webhook · Email	Jira · PagerDuty · Slack · Teams · Webhook · Email	Jira · PagerDuty · Slack · Teams · Webhook · Email	Jira · PagerDuty · Slack · Teams · Webhook · Email

Detail per engine sits on that engine’s page, including versions, topologies and the specific mechanisms behind each capability.

Coming from somewhere else

Need another database engine?

SchemaPulse is not architecturally limited to these four. The agent, the metric model, the backup policy language and the incident pipeline are engine-agnostic — what an engine needs is its own collection adapter, its own backup mechanism and its own topology model, which is an addition rather than a rewrite.

Which engines come next is decided by what customers actually run. We would rather add the one you need than announce a roadmap we have not committed to.

Tell us what you run. If your estate includes something not listed here, it is worth a conversation — that is how the order gets decided.

Tell us what you run