Who You Are
A brief description of your organization, its size, and what you do.
Home · Contact
Contact
Initial contact is deliberate. The goal is to determine fit, not to rush into work.
How to get in touch
The preferred way to make initial contact is by email. A short message is sufficient. There is no need for a detailed proposal or formal brief at this stage.
If you’re unsure whether this is a fit, that is expected. Most clients contact me before something breaks. Or after the second time it does.
Useful to mention
Your Systems
High-level information about your infrastructure: number of servers, providers, and critical components.
The Situation
Whether this is about ongoing management, a specific project, or an urgent issue.
What happens next
If the request appears to be a reasonable fit, I will respond to clarify scope and expectations. In some cases, a short call may be suggested. In others, it may be clear early that the work is not a good match. Either outcome is intentional.
I usually reply within one business day.
About availability
I work with a limited number of clients and do not accept every request. Response time depends on current workload and the nature of the inquiry.
Silence does not imply urgency. Nor availability.
If your server is on fire
If you are dealing with an active outage or security issue and are not an existing client, please review the Emergency Support page before getting in touch.
Emergency work is handled separately and subject to availability. Contacting me does not guarantee availability or acceptance of emergency work.
Send a message
By submitting information through this form, you acknowledge that discussions may involve sensitive information and may be covered by a Mutual Non-Disclosure Agreement (NDA). All inquiries are reviewed personally.
FAQ
Do you offer 24/7 support?
No. I do not provide 24/7 coverage or on-call guarantees. Availability is discussed explicitly for each engagement and documented in writing.
Do you guarantee uptime or recovery times?
No. Infrastructure work involves uncertainty. My role is to reduce risk, improve observability, and design systems that fail predictably.
Do you work with very small setups or hobby projects?
The focus is generally on production systems where stability and documentation matter. Some smaller or non-profit projects may still be considered if they have a clear long-term purpose.
Can you take over an existing infrastructure?
Often yes, after an initial review. Existing systems vary widely in quality, and onboarding may require corrective work before steady-state management.
Do you work with cloud providers?
Yes. This includes cloud, on-premise, and hybrid environments. Provider choice is secondary to clarity, failure modes, and operational discipline.
What if we are not a good fit?
That outcome is acceptable and expected. It is better to identify misalignment early than to force a working relationship that creates stress or risk.