Something you can put through a review
You are not evaluating software. You are evaluating a single supplier holding a principal’s entire data estate, and you have to write something defensible about it.
The answers are published, not promised
Which keys I hold and which the client holds, what an administrator can technically read, where the hardware physically is and what that does not give you — all of it in writing, before you ask.
Key-person risk, answered with a mechanism
Death, incapacity, insolvency and termination are treated separately, each with the arrangement that covers it — not a reassurance. The client can operate without me on any day of the contract.
Service levels with a consequence attached
What I owe you when something breaks, in hours rather than adjectives, how a one-person week actually runs, and what happens when I miss — including the exit.
No certification, and no pretending
There is no ISO 27001 and no SOC 2. If your committee requires an auditor’s letter, I am not your supplier and I will say so in the first reply rather than the fourth.
Company identification, VAT and REA numbers are here, so you can verify the entity before you speak to it.
Why replacing me is a handover, not a rescue
I run your infrastructure the way a family office runs a portfolio: on your behalf, with every account in your name, reporting to you. The machine it runs on is mine.
Nothing is in my name
The domain, the registrar account and the licences are yours, paid by you. I hold no account you cannot open yourself today, so there is nothing of yours to recover from me.
Written down, not remembered
Every service is documented: what it runs on, how it is configured, how it is restored. Your setup lives in a document you hold, not in my head, and it is standard software throughout — no private tooling only I understand.
Any competent administrator can take over
Because of the two above, replacing me is a handover rather than a rescue. If I am ill, away, or you simply want someone else, the next person starts from documentation and credentials you already hold.
What is committed, and what is not
Hardware I own, in my facility
Not a VPS reselling someone else’s cloud. One physical machine, just for you, encrypted at rest, in a facility I can walk up to — where it sits and who can reach it.
You would be among the first
I am taking on my first managed clients now. That means founding terms — your rate held for the length of the contract — and more of my attention than anyone who signs later will get. I would rather tell you that than imply a client list I do not have yet.
Who you would be contracting with
Eugene (Yevheniy) Hvozdikov
I run Arasaka alone, from Busto Arsizio. Behind it is a decade of production systems in regulated sectors — places where losing data is not an incident, it is a regulatory event. That is the standard your setup is built to.
Working alone is the point rather than a limitation. The person who designs your infrastructure is the person who answers you, so nothing is explained twice to a technician who has never seen it.
You can check me before we speak, and you should. The VAT and REA numbers are in the footer of every page, and they resolve to a real entry in the Italian Business Register — the details are here.
That decade was spent inside bank investments, insurance, HR services and gambling — as an employee and a contractor, on the systems those sectors are audited on. Not a client list: those were employers, and the work was theirs.
Questions
What happens when something breaks?
You hear from me, in writing, against the targets on the service levels page — how fast, and what happens after, are written there rather than decided in the moment.
What if you are ill, unreachable or dead?
Each case has its own arrangement, and the worst one needs no cooperation from me at all — the mechanism is here. The client can operate without me on any day of the contract.
Can we audit what you do?
You get read access to the administrative journal, the restore-test results in your report, and you may witness a restore. What you do not get is an auditor’s letter — said plainly here.
Can the principal’s own IT take over?
Yes, on any day. A second administrator of your choosing can hold the same documentation and be granted access by you, without asking me.
What happens if we leave?
30 days’ notice either way, no penalty. The handover document, a walk-through for the next administrator, and your data on drives you keep; the machine is yours to buy at its written-down value or have wiped.