Docs
CoyoteDB docs
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.
At a glance
| What it is | 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. |
|---|---|
| Built on | PostgreSQL 18, running unchanged inside the app. |
| Platforms | Tested on macOS and Linux; Windows has not been tested yet. Data nodes in one cluster must be the same system type; the witness and the apps that connect can be anything. |
| Node counts | 1 computer: no second copy. 2 computers: a live copy, no automatic switch-over. 2 computers + a witness: automatic switch-over (recommended for most people). 3 computers: automatic switch-over, saves still on two computers with one down. |
| Networks | Tailscale, Twingate, a site-to-site VPN or a local network. One encrypted port between nodes. |
| How apps connect | A normal Postgres connection string. Connecting through any node, which passes you on to the current main node, is not available yet. |
| Switch-over time | A new main node about 10 seconds after a hard kill (6 to 11 seconds); writes flowing again in roughly 10 to 25 seconds (measured on one Mac, default settings). |
| Coding agents | Any agent can use it like any Postgres database, with a normal connection string. |
| Licence | To be decided. |
| Status | CoyoteDB is not available to download yet. So far it has run one machine at a time (macOS and Linux; automatic switch-over on macOS). Power-cut tests have run on Linux virtual machines on one host; Windows and separate physical machines are not tested yet. |
Questions people often ask are answered in Answers; the reasons behind the design are on Why CoyoteDB.
All docs
- Postgres cluster concepts in plain wordsThe handful of ideas you need to understand CoyoteDB, a multi-node PostgreSQL cluster: nodes, the main node, voting, the witness and invite codes.
- Node counts for a Postgres cluster, explainedWhat you get with 1 computer, 2, 2 plus a witness, or 3 or more in a CoyoteDB Postgres cluster, which setup we recommend, and good practice for any of them.
- CoyoteDB FAQ for high availability PostgresShort answers to common questions about CoyoteDB: real Postgres, how many computers you need, networks, the witness, coding agents and moving data in and out.
- High availability Postgres, in plain wordsWhat high availability means for a PostgreSQL database, why one computer is not enough, and how CoyoteDB turns your own computers into a Postgres cluster.
- How automatic failover works in CoyoteDBHow CoyoteDB's nodes vote on a main node, why two computers cannot decide alone, what a witness adds, and how a cut-off node steps aside to avoid split brain.
- Postgres sync replication, in plain wordsHow CoyoteDB uses synchronous Postgres replication so a save counts only once two computers have it, and what happens with one data node left.
- Running Postgres over Tailscale or a VPNHow CoyoteDB nodes talk over Tailscale, Twingate, a site-to-site VPN or a plain LAN using one encrypted port, and what kinds of links it is built for.
- Why you still need backups with a Postgres clusterCopies between nodes keep your database running when a computer dies, but not from mistakes. Here is why a Postgres cluster still needs backups.
- Glossary of Postgres cluster termsShort, plain definitions of the words used around CoyoteDB and Postgres high availability: node, main node, witness, majority, failover, split brain and more.