The product

An org:admin registers the organization’s domains. Members with the org:admin or org:contributor role, and service accounts, create records under them: the record name is the name host joined to the domain, and the record type is A, CNAME, TXT or SRV.

Each record also carries a TTL, a routing policy (simple, failover, geo_location, split-view or weighted), an optional service owner label and an optional loose reference to a YellowPages service.

Every record and domain has a 9-bit mode, read like a unix file: view, edit and delete for the record owner, for members of the organization, and for everyone else, including anonymous callers.

Only the record owner or an org:admin may chmod. A mode can narrow what a role allows, never widen it across organizations.

New records are private (0o770). Publishing sets the other-view bit, which puts the record in the public directory, read-only, with only allowlisted fields. Organization-private data never reaches it.

Each publish or unpublish emits exactly one dns.record.published or dns.record.unpublished event.

The record linter is a deterministic rule set. It flags an A record whose content is not an IPv4 address, a CNAME that points at an IP, is malformed or sits at the apex, TXT content that is too long, a TTL out of range, a published record that exposes a private IP, and duplicate name and type pairs.

Lint findings are opt-in on the API (GET /list?lint=1) and appear in the dashboard’s Health column.

Record, domain and report changes become events. Each event is written in the same database transaction as the change itself, so a change and its delivery are never split.

Deliveries are signed with HMAC-SHA256 in the X-DNS-Signature header, sent only to public addresses, retried with backoff and dead-lettered after five failed attempts. Signing secrets are encrypted at rest.

Chorus stores and governs DNS records. It does not write them to a DNS provider and does not answer DNS queries; no provider client exists in the API or its packages.

The repo also contains a Tauri desktop app and an Expo mobile app with release workflows, but no build has been published, so this site offers no download. The web app is how you use Chorus today.