Solutions
Solutions
The same records serve three kinds of user. Here is what each gets from them.
For platform and infrastructure teams
Keep every record your organization owns in one place, with clear ownership.
- Domains registered once by an org:admin, records created under them
- A mode on every record, so ownership and access are explicit
- A linter that flags bad A records, CNAMEs at the apex and exposed private IPs
For application teams
Own your service’s records without an all-or-nothing admin panel.
- Create and edit records with the org:contributor role
- Narrow a record’s mode so only you and your organization can change it
- Publish a record to the public directory only when you mean to
For automation
Drive records from pipelines and follow every change.
- Service accounts with PATs, scoped to one organization and one role
- Signed webhooks for record, domain and report events
- An OpenAPI document at /openapi.json to generate clients from