Your developer left and nobody knows the passwords
The person who set everything up has gone. Nothing is broken yet — but nobody can log in to fix it when it is.
Does this sound familiar?
This is the most common way a business discovers it has an infrastructure problem: not through an outage, but through a resignation.
- Nobody is certain which provider the servers are actually on
- The domain renews to a personal email address of someone who has left
- There is one admin account and the password is in a message thread
- No one can say when the last backup was tested, or whether backups exist
What we do, in order
Roughly the first week. The sequence matters more than the speed.
We find out what exists
Before anything changes, we inventory it: which servers, which provider, which domains, which certificates, what renews when and on whose card. Most businesses in this position have never seen the full list.
We recover access
Registrar, hosting, DNS, database, mail. Where accounts are tied to a departed individual, we work through the provider recovery routes. This is the slow part, and it is the part that gets harder the longer you wait.
We move ownership to the business
Accounts move to company addresses, billing moves to a company card, and access is issued per person rather than shared. Losing one more employee stops being an event.
We take over the running
Patching, renewals, backups and monitoring become ours. Your team keeps day-to-day control of DNS and certificates through the console.
Why waiting makes it harder
Account recovery depends on evidence of ownership, and that evidence decays. A former employee’s mailbox gets closed, a card expires, a phone number is reassigned. The window where recovery is a support ticket rather than a legal exercise closes quietly.
Common questions
How do I regain access to a server when the developer has left?
Start with the provider, not the server. Hosting companies and registrars have account-recovery routes that rely on proving ownership — company registration, the billing card, or the original signup email. Recovering the account gets you the server; trying to break into the server rarely does.
What if the domain is registered in an ex-employee's name?
Registrars run a formal transfer-of-ownership process. It needs documentation showing the business owns the name, and it is far easier while the registration is current. Once a domain expires it enters redemption, where recovery costs considerably more and can fail entirely.
Can you take over without any handover from the person who left?
Usually yes. Most of what is needed can be established from the outside — where DNS points, who the registrar is, which certificates are live. Cooperation makes it faster, but it is not a precondition.
How long does recovering access take?
Anywhere from a day to a few weeks, depending entirely on how the accounts were registered. Provider recovery is the slow step, and it gets slower as evidence of ownership ages.