Why CoyoteDB
Why a database that stays up should be easy.
CoyoteDB is self-hosted software that runs real PostgreSQL on one or several of your own computers and keeps them in sync, so the database can keep running when one of them stops.
What problem does CoyoteDB solve?
Many apps keep their database on one computer. When that computer dies, the data and the app go with it. Making Postgres highly available usually means putting several separate tools together and having a specialist look after them.
Why does it exist?
So a small business or a solo builder can have a database that stays up without that expertise: install one small app on two or three computers and they look after each other.
Why real PostgreSQL instead of something new?
Because every Postgres tool, library and hosting habit already works with it, and your data sits in a format that has been trusted for decades. CoyoteDB adds the copying and the switch-over around it; it does not replace it.
Why on your own computers?
So the data stays with you, on machines you control, with no cloud database to rent. The computers can be in one room or linked over a private network such as Tailscale or a site-to-site VPN.
Why one program and an invite code?
So setting it up is minutes of work rather than a project: start the first computer, ask it for an invite code, and paste that code on the next one.
Why explain the safety rules in plain words?
Because you should know what happens when something fails: a save counts once two computers have it, the computers vote on which one is in charge, and a computer that is cut off steps aside so two never both act as the main one.
Why not just run one database?
One database is fine until its computer stops. Then everything that depends on it stops too, and anything saved since the last backup may be gone. A second full copy, and a third vote, mean one dead computer is an inconvenience, not an outage.
Can I take my data elsewhere later?
Yes. There is no lock-in: your data is plain PostgreSQL, so standard Postgres dump tools copy it out whenever you like, and any Postgres server can load it.
Why not do nothing?
Doing nothing works until the day the one computer fails. CoyoteDB is meant to make the safer setup cheap enough in time and effort that it is worth doing before that day.
Next: how automatic failover works, who it is built for, or answers to common questions.