Use cases
High availability Postgres, built for people without a database team.
Who CoyoteDB is for, who it is not for, and how you can use it. It is new, so these are the people it is built for, not customer stories.
Who it is for
Who it is for, and who it is not for.
CoyoteDB does one job: it keeps a Postgres database running on a few of your own computers when one of them stops. If that is not your problem, something else will suit you better.
A good fit if
- You want Postgres on computers you own. Your data stays on your machines, in one room or linked over a private network. There is no cloud database to rent.
- Nobody on your team is a database specialist. You want a database that stays up without first learning replication and failover tools. The nodes vote and switch over by themselves.
- You can keep two or three computers on. Two computers plus a small witness device, or three computers, give you automatic switch-over. One computer is fine to start with.
- Your app speaks Postgres, or soon will. Anything that connects to PostgreSQL connects to CoyoteDB with a normal connection string.
Not the right fit for
- Teams happy with a managed cloud database. If a hosted Postgres service already runs your database and you are happy with it, there is no need to move.
- One database across regions. It is built for a few computers on one private network, or a VPN between a few sites. It is not for spreading a database around the world.
- Writing on several computers at once. One node, the main node, takes the writes. The others keep live copies and take over if it stops.
- Data too big for one computer. Every data computer holds a full copy, so the whole database has to fit on each one. CoyoteDB does not split data across machines.
- Mixed operating systems for the data, today. Today the computers that hold data must all be the same system type, and CoyoteDB refuses a mixed join rather than risk your data. The witness and your apps can run on anything.
- A replacement for backups. A mistake such as a deleted table is copied to every node at once. Keep backups as well.
01 · Small business apps
The app in the back office keeps running.
- The problem
- Your orders, bookings, stock or till app runs on one PC in the back office, and if that PC dies, the business stops.
- What CoyoteDB does
- A second computer keeps a full, live copy of the database. With a witness, it takes over by itself if the first one dies, so the database carries on without it.
- Suggested setup
- 2 computers + a witness
02 · Indie builders and vibe coders
Real Postgres you own, on your own machines.
- The problem
- You are building an app, often with an AI coding agent, and you want a real Postgres database without renting one from a cloud.
- What CoyoteDB does
- CoyoteDB runs PostgreSQL 18 on your own computers, so it is hosted where you are and there is no cloud database to pay for each month. Any Postgres library connects to it, and your coding agent can use it like any Postgres database.
- Suggested setup
- Start with 1 computer, grow to 2 + a witness
03 · Homelabs and self-hosters
Postgres across your own boxes.
- The problem
- The services you run at home all depend on one Postgres, on one mini PC that will fail one day.
- What CoyoteDB does
- Spread Postgres across your own machines over Tailscale or your LAN. When a mini PC dies, the others hold full copies and carry on by themselves.
- Suggested setup
- 3 computers, or 2 + a witness on a Raspberry Pi
04 · Internal tools and side projects
Start small, add computers later.
- The problem
- You need a database today, but you do not want to plan the whole setup up front.
- What CoyoteDB does
- Start on one machine. When it matters more, add computers with an invite code. Your app connects the same way before and after.
- Suggested setup
- Start with 1, add computers with an invite code
05 · Agencies and freelancers
A dependable database at your client’s site.
- The problem
- You build software for clients who need it to keep running, but nobody there is a database specialist.
- What CoyoteDB does
- Put one app on the client’s computers and join them with invite codes. If one computer stops, the others take over by themselves (with 3 computers, or 2 plus a witness), without someone on call to fix it.
- Suggested setup
- 2 computers + a witness
06 · Offices and shops in more than one place
A copy in each location.
- The problem
- You have two sites, and you want the data to survive if one of them loses power or its internet line.
- What CoyoteDB does
- Link computers in each site with a site-to-site VPN, so each one holds a full copy, and put the witness in a third place or on a small cloud server. It is built for links like a VPN between a few sites, not for spreading a database across the world.
- Suggested setup
- 2 computers + a witness in a third place
Ways to use it
How people set it up.
The same small app in every case. What changes is how many computers you use and how they reach each other.
Start on one computer, add more later
Run one command and you have real Postgres. When it matters more, ask that computer for an invite code and paste it on the next one.
One computer, explainedcoyote upcoyote invitecoyote join <code>Two computers and a witness
The setup we suggest for most people. Two computers of the same system type hold full copies. A small always-on device, such as a Raspberry Pi, only votes, so switch-over happens by itself.
Two computers and a witnesscoyote witness <code>Three computers when the data really matters
Three full copies and no witness needed. Even with one computer down, a save still lands on two computers before it counts.
Three computersOver Tailscale, a VPN or your LAN
The computers only need to reach each other on a private network: Tailscale, Twingate, a site-to-site VPN or the same local network. They talk over one encrypted port.
Private networksAlongside your coding agent
Give your agent the connection string and the short note on the coding agents page. It uses CoyoteDB like any Postgres database.
Coding agentsBring a database you already have
It is real PostgreSQL, so pg_dump and pg_restore copy a database in from another Postgres server, and back out again. There is no lock-in.
What runs on it
If it speaks Postgres, it connects.
CoyoteDB runs real, unchanged PostgreSQL 18. To your app it is a normal Postgres server: it connects with a standard postgresql:// connection string, with no special driver.
- Web frameworks and ORMs
- Django, Ruby on Rails, Laravel and Spring support Postgres, and so do Node tools such as Prisma and Drizzle. Give them the connection string as you would for any Postgres database.
- Any programming language
- There are Postgres drivers for Python, JavaScript and TypeScript, Go, Ruby, PHP, Java, C# and more. They connect the same way they connect to any Postgres server.
- Self-hosted apps
- Many self-hosted apps ask for a Postgres database or connection URL during setup. Point them at CoyoteDB.
- Database tools
- psql, pgAdmin, DBeaver and other Postgres tools open it like any Postgres database. pg_dump and pg_restore copy data in and out.
- Your coding agent
- An AI coding agent that can use a Postgres library can work with it. coyote conninfo prints the connection details. How agents connect
We have not tested specific products with CoyoteDB. If an app supports PostgreSQL 18 and needs no extra Postgres extension, it should connect as it would to any Postgres server.
When the main computer stops, another node becomes the main node and writes flow again in roughly 10 to 25 seconds (measured on one Mac, default settings).
Connecting through any node, so your app always reaches the current main node, is not available yet.
Is it a fit?
A quick check, yes or no.
If most of these are a yes, CoyoteDB is built for you.
- You want your database on computers you own, not rented from a cloud.
- You can keep two or three computers switched on, or one to start.
- Those computers can reach each other on one private network: a LAN, Tailscale or a VPN.
- The computers that will hold data run the same operating system.
- Your app talks to Postgres, or it can.
- You will keep backups as well.
Straight answers
Is this for real?
What people ask first when they come across a new project.
Is it real PostgreSQL?
Yes. CoyoteDB downloads, checks and runs PostgreSQL 18, unchanged. It is not a fork and not a look-alike, so your data sits in ordinary PostgreSQL. CoyoteDB is not affiliated with or endorsed by the PostgreSQL project.
Where does my data live?
On your own computers. CoyoteDB is software you run yourself, not a cloud service. The nodes copy the data between each other, over one encrypted port on your network.
Can I use it today, and what does it cost?
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. There is nothing to buy: no price or licence has been set yet.
Who makes it?
CoyoteDB is made by the CoyoteDB team. Ask us anything at [email protected] or through the contact page, and follow along on X and GitHub.
More questions? Read answers to common questions, how automatic failover works, or get in touch.