Calango LabIt runs. Nobody knows how.
A site or a system live in production, with no contact left to whoever built it. No documentation, dated technology, a password nobody can find and nobody who knows how to touch it.
How a rescue goes
Audit
Establish what is actually there: code, database, integrations and what has already broken.
Documentation
Write down what was found — including the rules that only ever lived in the code.
Action plan
Fix, migrate or rebuild, with the cost and the time each route takes.
Execution
Take the route you chose. Even when that means not hiring us for it.
This is work that asks for mileage, not enthusiasm — twelve years of it is the credential that counts here.
What people usually ask
I have access to nothing: no server, no code, no passwords.
That’s the most common starting point. Part of the audit is precisely recovering access — domain registration, hosting, database and repository — from whatever the company holds in its own name. It’s investigative work before it’s coding work.
Does the audit commit me to hiring the execution?
No. The action plan is delivered with the cost and time of each route, and it’s yours — including to take to another supplier. Holding a client hostage through lack of information is exactly the problem they came here to solve.
Is it worth fixing, or better to rebuild?
It depends on what the audit finds, and the honest answer is sometimes rebuild. What the audit hands you is the bill for both routes, what each one costs and what each one risks, so the decision is yours and made with the numbers in hand.