Start for free

About SiteGov

25 years.
Hundreds of client sites.
The same infrastructure problem - every time.

After hundreds of launches, migrations, and client handoffs, a pattern emerged that was hard to dismiss. Well-executed projects would run into the same operational wall, often at the worst possible moment: nobody had a clear picture of who actually controlled the infrastructure behind the site.

SiteGov was built as a direct response to that gap, not as a theory, but from having been in these situations too many times to count.

The pattern

The same situations. Different clients. Different years.

Working with clients long enough, you start to recognize these moments. Different projects, different industries, different years. The same underlying problem.

Project timeline

✓
Project
Approved
✓
Design
Complete
✓
Development
Complete
✓
QA
Complete
!
Launch
Day
DNS access missing  ·  Registrar login unknown  ·  Project blocked
OBS · 001 LAUNCH

DNS access missing on launch day

The site is ready. The client is ready. The DNS is controlled by someone who left eight months ago. Nobody documented that the nameservers were pointing to the old host. Everything was visible before the project started.

OBS · 002 RENEWAL

Domain renewal notices sent to abandoned inboxes

The domain was registered under the founder’s personal Gmail from 2014. The account still exists. Nobody checks it. The renewal is automatic, until the card expires.

OBS · 003 TURNOVER

Former employee still owns the registrar account

Someone leaves the company. Their email is still the primary contact on three registrar accounts. Everything is fine until someone needs to change DNS, renew a domain, or transfer a registrar.

OBS · 004 HANDOFF

Agencies inheriting undocumented infrastructure

A new agency takes over. The outgoing team shares a list of logins in a Google doc. Some are current. Some aren’t. The hosting is on a personal credit card. The DNS is “probably GoDaddy.”

OBS · 005 ACCESS

Hosting tied to a personal account

The hosting is under a developer’s personal account. They moved on two years ago. The billing still works. Access recovery does not. Resolving it means a support ticket and weeks of back-and-forth.

OBS · 006 VENDOR

Unknown vendor still controls the DNS

An old vendor relationship ended. The nameservers still point to their infrastructure. Nobody realized. It was fine, until the vendor’s system had an outage and the client’s email went down for a day.

How this started

Years of good work running into the same operational wall.

The projects that led to SiteGov weren’t failures. That’s what makes the pattern worth talking about. The work was solid. The code shipped. The design was approved. The client was happy.

And then, at the exact moment it mattered most (launch day, a migration, a handoff, an emergency), something outside the project would surface. Who controls the DNS? Where’s the registrar login? Whose personal account is hosting tied to? Is that vendor relationship still active?

These situations aren’t failures of craft. They’re failures of documentation. Preventable, but only if someone had thought to capture the information before it was needed.

One launch was delayed by more than a week because nobody knew how to access the client’s Cloudflare account. It wasn’t an unusual situation. It was one of many that pointed to the same gap: infrastructure ownership needed to be documented before it was needed.

That realization eventually became SiteGov.

Infrastructure ownership map

Documented
Old vendor
Former employee
Unknown

What we believe

Principles that drove every product decision.

Infrastructure knowledge should survive employee turnover.

When the person who managed the DNS leaves, their knowledge should stay behind. A system that only works while specific people are present is one departure away from an operational gap.

Access should be documented before it is needed.

Nobody finds out who controls a registrar account at a convenient moment. The right time to discover a missing login is during a routine review, not at 11pm on go-live day.

Client records belong to clients.

Infrastructure records are maintained by agencies, but they belong to the domain owner. Like medical records: the provider keeps them current, but the patient owns them. When the agency relationship ends, the record transfers, not disappears.

Control matters more than assumptions.

“We think the client has access” is not the same as knowing they do. “The domain auto-renews” is not the same as knowing who gets the renewal notice. SiteGov replaces assumptions with records.

Meet the founder

Built after looking for a tool that didn’t exist.

John Stuifbergen

John Stuifbergen

Founder, SiteGov

Founder, Jolly Good Sites

After 25 years of building websites through Jolly Good Sites, managing client launches, inheriting sites from other agencies, handling migrations, and supporting clients through transitions, a pattern emerged that was hard to dismiss.

The same challenge appeared across different clients, different team structures, and different project types. A launch delayed because DNS access was missing. A domain at risk because renewal notices were going to an abandoned inbox. A handoff complicated by infrastructure nobody had documented.

After enough repetitions, the natural response is to look for a tool that solves this. The tools that existed addressed credentials, uptime, and vulnerabilities. None of them addressed the underlying question: who controls each provider, is that access documented, and can the right person actually be reached when something goes wrong? SiteGov was built to answer that.

Experience behind the product

25+
Years building websites
100s
Of launches and migrations
1
Recurring pattern. Almost every time.

Where this is going

From scattered knowledge to infrastructure agencies can rely on.

Most agencies carry infrastructure knowledge in people’s heads, email threads, and spreadsheets nobody updates. SiteGov is the transition away from that.

Before SiteGov

Tribal knowledge
Email threads
Stale spreadsheets
Memory and assumptions
SiteGov

After SiteGov

Documented records
Transferable on handoff
Recoverable after turnover
Operationally resilient

Get started

The most important infrastructure information is usually discovered when something breaks.

SiteGov helps agencies document domains, DNS, hosting, SSL, email, and infrastructure ownership before those moments happen.

Run a free infrastructure scan What is SiteGov?

No credit card required. Your first scan in under five minutes.