#Supported databases

Every database Ivory supports is a plugin with two halves:

• The cluster side — how Ivory finds the members of a cluster, tells the leader from the replicas, measures replication lag and runs operations like a switchover or failover. In Ivory's terms this is the cluster's Keeper: an HA tool such as Patroni, or the engine's own built-in replication. It is reached on the node's Keeper port.
• The database side — the query console, saved queries and dashboards, reached on the node's Database port. For engines that manage their own replication, both ports are usually the same.

Because of that split, every cluster looks the same in Ivory — one overview, one set of operation buttons, one console — and each page below describes what that engine fills in.

STABLE is what Ivory has run against for a long time; BETA works end to end but has had less time in the field; new plugins start at ALPHA.

#Operations

An operation a cluster cannot perform is simply not offered in the UI. ⏱ marks one that can also be scheduled for a later time.

#Health and replication lag

Ivory warns about a replica whose lag passes its threshold. The threshold is Ivory's own default for that engine, not a setting of the engine itself.

#Query console

Every engine ships a set of saved queries for monitoring and diagnostics; see Node → Database.

#Adding your database

Every engine is a self-contained plugin, so supporting a new one needs no change to Ivory's core. The repository ships an AI agent for exactly this — ask Claude Code to use keeper-database-plugin for your engine and it writes both halves, their tests and the UI wiring by the project's checklist. Then open a pull request; see Contributing.