# nanopack/yoke

Postgres high-availability cluster with auto-failover and automated cluster recovery.

Repository: https://github.com/nanopack/yoke
Canonical: https://ross.abutalabs.com/products/yoke
Language: Go
License: NOASSERTION
License Family: other
Topics: postgres, auto-failover, redundancy, golang, nanobox, availability-cluster, cluster, nanopack
Archived: true
Last push: 2016-01-07T00:37:05+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3954, "days_push": 3892, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, archived, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1341, forks 62 (observed 2026-08-28T04:04:26.132604+00:00)

## What it is
Yoke is a Postgres high-availability cluster manager written in Go that provides automatic failover and automated cluster recovery across a three-node primary/secondary/monitor setup. It manages Postgres as a child process, syncs data between nodes via rsync over SSH, and supports virtual IP and role-change hooks.

## Use cases
- run a highly available postgres cluster with automatic failover
- automatically recover a postgres cluster after node failure
- manage postgres primary/secondary replication with a monitor node
- assign a virtual IP that follows the postgres master
- run custom scripts when a node's postgres role changes
- introspect cluster node status from the command line

## When to choose
- you need a simple self-managed postgres HA cluster on bare servers with ssh and rsync
- you want automatic failover without an external orchestrator like Patroni
- you're already in the Nanobox/NanoPack ecosystem

## When to avoid
- you need actively maintained software - the last release was in 2016
- you want Kubernetes or cloud-native postgres HA (use Patroni, Stolon, or CloudNativePG)
- you need more than a 3-node primary/secondary/monitor topology
- you can't run postgres as a child process managed by yoke

## Facets
- artifact type: service
- maturity: abandoned
- function: database, deployment, monitoring, cli
- domain: databases, self-hosted, infrastructure-as-code
- platform: go, self-hosted, cli
- tags: postgres, high-availability, auto-failover, cluster-management, database-replication, nanobox, devops, linux

## Member repositories
- nanopack/yoke (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:26.132604+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:43:45.432512+00:00, confidence not recorded.
  - readme: https://github.com/nanopack/yoke (fetched 2026-08-28T04:04:26.132604+00:00, sha cd872fc64842)
- Data as of 2026-08-30T08:39:29.467469+00:00.