What Happens if Your Web Developer Disappears?

Websites outlast the people who build them. The developer who set up your WordPress install in 2017 may be running a bakery in 2026, or working interstate, or simply not interested in replying to a one-off question about a nine-year-old project. For businesses that only speak to their developer when something is broken, the day they cannot speak to them at all is a quietly stressful one.

The uncomfortable truth is that the website only belongs to the business if the business can reach the accounts that run it. The visible site is produced by three or four systems working together, and each of them lives behind a login. If any of those logins are tied solely to the developer, the business is a tenant, not an owner.

Three Flavours Of Disappearance

The first is the amicable handover gone cold. The developer finished the site, invoiced, and quietly stopped responding to emails as other work filled their calendar. Nothing hostile. Just a slow fade.

The second is the business that closed. A one-person studio or a two-person agency wound down. The company name is still on your old invoices, but the website, the support inbox and sometimes the ABN have been retired.

The third, and the one most people prefer not to think about, is the serious illness or death of a sole developer. It is more common than the industry admits, especially for the generation of independent developers who built out the first wave of Australian small-business websites.

In each of these cases the business response is the same: find out which systems hold the site together, confirm who has access to each one, and move anything the developer solely controlled into business-owned accounts.

The Four Parts To Document

The domain. Which registrar is the domain with, which email receives the renewal notices, and does anyone at the business have the login to that registrar account. The registrar is the control point. Whoever can sign into the registrar can point the domain anywhere, and no amount of money paid to the developer changes that.

The DNS. Sometimes the registrar is also the DNS provider. Sometimes the DNS is on a separate account, often Cloudflare, often created on the developer's personal email address. If the DNS is somewhere else, that account is the second control point and needs to be documented separately.

The hosting. Where does the website actually run. Is it on a shared hosting plan at an Australian provider, a managed WordPress host like WP Engine or Kinsta, a VPS at DigitalOcean or Vultr, or a cloud account at AWS or Google Cloud. Who pays the invoice, and whose credit card is on file.

The site itself. The admin login to WordPress, Shopify or whichever platform runs the site. Do multiple admin accounts exist, and is at least one of them under the business's control.

The fifth part, which is not strictly needed to run the site but is needed to rebuild it, is the backup. Is one being taken, where is it stored, and can the business request a copy without going through the developer.

The Registrar Problem

An alarming number of small-business .com.au domains are registered through a reseller account controlled by the developer. The reseller arrangement is legitimate, it is common, and it works fine until the developer stops responding. At that point the domain can be inside a dashboard the business has never seen, with renewal notices going to an inbox the business never reads.

The fix is to transfer the domain into a registrar account owned by the business, with the registrant email set to a current, business-owned mailbox. This is a half-hour task when the developer is cooperative and a long one when they are not.

The DNS Problem

DNS is the layer that decides where your domain points. If the nameservers are set to a developer's Cloudflare account, that account is where email, website and any subdomains are decided. Losing that account can mean the domain still exists at the registrar, but the business cannot change where it points without the developer's cooperation.

The resolution is either to add a business-controlled email as an administrator of the DNS account, or to move the DNS back to the registrar's own nameservers. Either way, the end state is that nobody outside the business holds unilateral control.

The Hosting Problem

Hosting accounts that are paid for by the developer and then rebilled to the business are convenient. They are also fragile. When the developer disappears, so does the credit card paying the hosting invoice, and the site goes down on the next billing cycle.

The resolution is to put the hosting account in a business name, with a business-owned email, and a business credit card. Developers who need access can be added as collaborators, which most reputable hosts support.

The Site Problem

Even where the business has all of the above, if the only administrator account on WordPress is the developer's, a locked-out business can struggle to update content. The simple fix is to create an administrator account for an internal person, confirm it works, and keep the credentials under control. One business account, one developer account, each with its own login, is the healthy minimum.

The Backup Question

A business with no backup is one failed update away from an expensive rebuild. Ask the developer where the backup lives, how often it is taken, and whether a copy can be sent to the business. Store the most recent copy on a business-owned file store. Yes, it feels paranoid. It is also what the business needs to be able to say 'yes' to the first question an incoming developer will ask.

A backup you have never restored is an assumption, not a control. Test a restore while the developer is still available, even into a staging environment. The test teaches the business which credentials are needed and how long the process takes.

Agency Acquisitions And Mergers

Agencies merge and get acquired more than their clients realise. The partner you signed with in 2019 may have been quietly bought by a larger agency in 2022, and the staff who built your site may have moved on. The service might still be fine. The relationship might not survive the next ownership change. Treat an agency acquisition announcement as a prompt to confirm who holds what, not as an administrative detail that does not affect you.

A Short Scenario From Inner Sydney

A boutique bookshop in inner Sydney commissioned a bespoke site in 2015. The developer, a solo operator, moved to Spain in 2020, continued answering emails occasionally, and then stopped altogether in 2024 after what the family later said was a serious illness. The domain was in his personal reseller account at an auDA accredited registrar. The hosting was on his personal AWS account. The DNS was on his personal Cloudflare account. The site itself still worked. Nobody at the bookshop could change the opening hours banner.

The resolution took the better part of two months and involved auDA's dispute process, a sworn statement, and a complete rebuild of the hosting environment on a new account. None of the technical work was difficult. The waiting, the paperwork and the loss of the Christmas trading window were the real cost. Had the registrar, DNS and hosting all been in the bookshop's name from the start, with the developer invited as a collaborator, the only task would have been to engage a new developer.

The Continuity Conversation

The time to have this conversation is at the start of the engagement, not after a problem. Ask the developer directly which accounts they will create in your name and which they will not. Ask them to document the stack in writing. Ask them what happens if, hypothetically, they were unavailable for six months. A good developer will have thought about this and will be ready to put you in the right accounts. A developer who gets defensive about the question is the one you most need to ask.

Put commercial terms around access. Contracts can require that the registrar, hosting and repository ownership sit with the client, and that a handover pack is delivered before final payment. Continuity is a feature you can purchase deliberately, and it is a reasonable thing to ask for.

How Business Vault Fits

Business Vault records the registrar, the DNS provider, the hosting account, the site admin and the backup location as separate assets, each with its own owner and recovery contact. When any of them is held only by an external party, that is visible as a risk. The register does not replace the conversation with your developer. It makes sure the answers to the conversation do not live only in the developer's head.

A website is a business decision long before it is a technical one. The developer builds the site. The business owns it, or does not, depending on which accounts the business can reach when the developer cannot be reached at all.