Meet ivory.veegres.com: the website, the docs and a new logo for the open-source tool that deploys, watches and fixes your database clusters
For a long time, Ivory lived in exactly one place: a GitHub repository. If you wanted to learn about it, you opened the README, clicked through a folder of Markdown files and hoped you'd find the right one.
That worked while Ivory was a small Postgres and Patroni helper. It doesn't work anymore. Ivory now manages seven kinds of clusters, deploys them, watches the machines behind them and has an MCP server for AI agents. That deserves a proper home.
So here it is: ivory.veegres.com.
Ivory's UI: every cluster, the health of every node and the machine behind each one, in one screen
Deploy. Watch. Fix. Anywhere.
That's the tagline on top of the page, and it's the shortest description of Ivory I've ever managed to write:
- Deploy a cluster from a template over plain SSH.
- Watch its health: roles, replication lag, pending restarts and warnings for every node.
- Fix it: switchover, failover, restart, reinitialize, run a diagnostic query, read a log.
- Anywhere: from your browser, from your phone, or from your AI agent.
What you'll find on the site
Why Ivory, in three sentences
The landing page starts with the three reasons Ivory exists:
- Nothing to install. Ivory reaches your machines over plain SSH and talks to each database in its own protocol. No agent beside every node, no Kubernetes, no Ansible, no cloud account — one Docker container and you're done.
- One workflow, every engine. PostgreSQL, etcd, Redis, ClickHouse, MongoDB and ZooKeeper look and behave the same: the same health view, the same switchover button, the same console. Learn it once, use it everywhere.
- Fix it from anywhere. A UI that works on your phone for the 3 a.m. page, and a built-in MCP server so your AI agent can dig into a cluster with you — under exactly the permissions you have.
Every supported database, at a glance
PostgreSQL with Patroni and plain PostgreSQL replication are stable. etcd, Redis, ClickHouse, MongoDB and ZooKeeper are in beta. And there's one more card: "Yours next?" Every engine in Ivory is a self-contained plugin, and the repository even ships an AI agent that writes a new one for your database by the project's own checklist.
Real documentation, with search
This is the part I'm happiest about. The docs are finally easy to read and easy to search:
-
Getting started — from
docker runto your first cluster - Clusters, Overview and Node — everything the UI does, screen by screen
- Deployment — templates, variables and the shipped templates for every engine
- A page for every database — what Ivory reads, which operations it offers, how lag is measured and when it warns
- MCP server — connecting an agent, permissions and every tool it can call
- Comparison tables — operations, lag thresholds and console features for every engine, side by side
A small detail for fellow maintainers: the docs are still the same Markdown files in the repository's .doc folder. The site copies them in at build time, so there's one source of truth, and the docs keep rendering on GitHub exactly as before. The site itself is built with Rspress and served as static files from Cloudflare.
"Just ask your cluster"
The site has a whole section on Ivory being AI-ready, with the kind of questions you can now ask:
"Why is replica 2 lagging?"
"What is blocking my queries?"
"Switch the leader to node 3."
I'll write a separate article on how to make the most of it.
Up and running in a minute
docker run -p 80:80 --restart always veegres/ivory
Run the container, open the setup wizard at http://localhost, choose how people sign in, and add a cluster: type its node addresses, let Ivory detect the rest from one node, or deploy a brand-new one.
Coming soon: a Playground
There's a Playground link in the menu. It's not live yet, but it will be: a real Ivory with a real high-availability cluster behind it, right in your browser — no install at all. Watch the repository on GitHub to know when it opens.
And about that butterfly… 🦋
You may have noticed Ivory has a new logo.
Look closely 😉
It's a butterfly. But look at it again: the wings are a pair of big ears, and the tail curls down like a trunk. The elephant is still there.
Ivory started as a tool for Postgres — and Postgres is an elephant. In my very first article I wrote "When your elephant suddenly takes a nap, you rush to his side." That's still true. But Ivory isn't only about one elephant anymore. It looks after etcd, Redis, ClickHouse, MongoDB and ZooKeeper too, and it can reach them from a browser, a phone or an AI agent.
So the elephant didn't go anywhere. It just grew wings. 🐘➡️🦋
Get involved
Ivory is free, open source under GPL-3.0, and built in my spare time. If you'd like to help:
- ⭐ Star it on GitHub — one click that helps other people find it.
- 🧩 Add your database — every engine is a plugin, and there's an AI agent to help you write one.
- ❤️ Support the project — sponsorship funds new database plugins and features.
Treat your clusters with kindness, and they'll show you the way. 😉
Useful links:
Top comments (0)