Pierre-Olivier Mercier
24eb85edc1
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
95 lines
4.7 KiB
Markdown
95 lines
4.7 KiB
Markdown
+++
|
|
title = "happyDomain for IT Managers"
|
|
description = "Get full visibility over your organization's domain names. happyDomain provides IT managers with centralized control, change tracking, and team oversight."
|
|
layout = "usage"
|
|
+++
|
|
|
|
{{< usage-lead >}}
|
|
Your organization's domains, <span class="text-hilight px-1">fully visible</span>, <span class="text-hilight px-1">under control</span> and <span class="text-hilight px-1">auditable</span>, whoever the providers are.
|
|
{{< /usage-lead >}}
|
|
|
|
{{< usage-points title="Does this sound familiar?" >}}
|
|
{{< usage-point icon="diagram-3" title="Scattered everywhere" >}}
|
|
Domains spread across registrars, cloud accounts and legacy hosts. Nobody has the full picture until something breaks.
|
|
{{< /usage-point >}}
|
|
{{< usage-point icon="person-lock" title="Locked behind one person" >}}
|
|
Every DNS change waits for the one engineer who holds the registrar credentials. A bottleneck, and a single point of failure.
|
|
{{< /usage-point >}}
|
|
{{< usage-point icon="eye-slash" title="Failures found by users" >}}
|
|
An expired domain, a broken delegation, a forgotten subdomain still pointing at a decommissioned server, all discovered in production.
|
|
{{< /usage-point >}}
|
|
{{< /usage-points >}}
|
|
|
|
{{< usage-feature
|
|
title="See your entire domain portfolio in one place."
|
|
image="/img/screenshots/domains-list.webp"
|
|
alt="List of domains from several providers, grouped by need"
|
|
url="app.happydomain.org/domains"
|
|
>}}
|
|
happy<span class="fw-bold">Domain</span> connects to more than 25 hosting providers worldwide: registrars, cloud DNS, CDNs and your on-premise servers.
|
|
|
|
Import a provider in one click and get a single, always up-to-date inventory of every domain your organization owns. No more spreadsheets, no more guessing which account holds what.
|
|
{{< /usage-feature >}}
|
|
|
|
{{< usage-feature
|
|
title="Catch incidents before your users do."
|
|
image="/img/screenshots/checks-dashboard.webp"
|
|
alt="Monitoring dashboard showing the status of every check on a domain"
|
|
url="app.happydomain.org/domains/example.com/checks"
|
|
flip="true"
|
|
bg="green"
|
|
>}}
|
|
happy<span class="fw-bold">Domain</span>'s checkers continuously watch over your whole portfolio: expirations, DNSSEC, delegation, certificates and service availability, with a clear status for each domain.
|
|
|
|
Your teams are notified the moment something changes state. Silent failures become actionable alerts, before they become outages.
|
|
{{< /usage-feature >}}
|
|
|
|
{{< usage-feature
|
|
title="Review every change before it reaches production."
|
|
image="/img/screenshots/zone-diff.webp"
|
|
alt="Review and confirm the changes that will be applied"
|
|
url="app.happydomain.org/domains/example.com/diff"
|
|
>}}
|
|
No change is applied blindly: happy<span class="fw-bold">Domain</span> shows the exact difference between the current zone and the new one, and asks for confirmation.
|
|
|
|
A typo in a record no longer takes a service down. Your team sees what will change, validates it, then deploys. It works like a code review, for your DNS.
|
|
{{< /usage-feature >}}
|
|
|
|
{{< usage-feature
|
|
title="A full audit trail, and a way back."
|
|
image="/img/screenshots/domain-logs.webp"
|
|
alt="Domain logs showing change history"
|
|
url="app.happydomain.org/domains/example.com/logs"
|
|
flip="true"
|
|
bg="plum"
|
|
>}}
|
|
Every modification is recorded: what changed, when, and who made it. When an auditor (or an incident) asks "who touched this zone?", the answer is one click away.
|
|
|
|
And because the entire history is kept, you can roll any zone back to a previous state at any time.
|
|
{{< /usage-feature >}}
|
|
|
|
{{< usage-feature
|
|
title="Delegate to your teams, without losing control."
|
|
image="/img/screenshots/domain-abstract.webp"
|
|
alt="Zone management shared between teams"
|
|
url="app.happydomain.org/domains/example.com"
|
|
coming_soon="true"
|
|
>}}
|
|
Let each team manage the records related to its own projects, internal or public, instead of queuing tickets to a central admin.
|
|
|
|
happy<span class="fw-bold">Domain</span>'s fine-grained access control lets you delegate all or part of a zone, down to a single record. Teams move fast; you keep the oversight.
|
|
{{< /usage-feature >}}
|
|
|
|
{{< usage-feature
|
|
title="No more forgotten subdomains."
|
|
image="/img/screenshots/domain-services.webp"
|
|
alt="Services attached to a domain, each with a clear purpose"
|
|
url="app.happydomain.org/domains/example.com/services"
|
|
flip="true"
|
|
bg="green"
|
|
coming_soon="true"
|
|
>}}
|
|
Document the purpose of every subdomain, and set an expiration date on temporary ones: a marketing event, a demo, a test environment.
|
|
|
|
When the date comes, happy<span class="fw-bold">Domain</span> cleans up automatically. Stale records pointing at decommissioned servers (the classic path to subdomain takeover) simply stop accumulating.
|
|
{{< /usage-feature >}}
|