FAQ
The things people usually do not ask out loud, though they should: access, the right to stop, and who owns the result.
What access do you need, and can it be less?
For the review, read-only access is usually enough. For the work itself I need write access — but only to what we agreed on, and through a separate account rather than your personal one. You can revoke it at any moment with a single command, and I will show you which one.
Can I stop the work halfway?
Yes, at any point. Every step is planned to be reversible and the rollback is prepared before anything changes, so stopping does not leave the system in a half-finished state. You pay for what was done before the stop.
What if you find nothing?
It happens, and it is a normal outcome. I will say so when we review the task and we go our separate ways. Inventing a problem in order to sell the fix is the fastest way to lose a reputation.
Who owns the result?
You do: access, configuration, scripts and the report all stay with you. I do not leave closed-off pieces that cannot be maintained without me. Locking a client to a contractor is a business model, not engineering.
How is pricing calculated?
After we review the task: first I understand the scope, then I state the price and the timeline in writing. There is no price list on the site on purpose — a number quoted before seeing your infrastructure would be a guess.
What about confidentiality?
Nothing from your infrastructure appears in public materials without separate permission. The case studies on this site are about my own servers. If your case ever appears, it will be with your consent and anonymised.
You work alone. What if you are unavailable?
That is exactly why everything I do is written up and left with you. Another engineer can continue without asking me anything. I do not offer round-the-clock duty and will not pretend otherwise.
Which time zone and which languages?
Remote, UTC+3. Russian and English.
Question not covered? Ask directly — I usually reply the same day.